Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Concerns about BTCR method #41

Open
kimdhamilton opened this issue Aug 12, 2017 · 0 comments
Open

Concerns about BTCR method #41

kimdhamilton opened this issue Aug 12, 2017 · 0 comments

Comments

@kimdhamilton
Copy link
Contributor

From discussion with @msporny @ChristopherA and @kimdhamilton

Spec should be declarative: as long as you end up with X, doesn't matter how you construct it

The BTCR examples are doing 2 things, which Manu recommends separating.

  1. proof of control
  2. verifiable claims

For BTCR, why fragments?

  • DDOs have almost nothing to do with VC, but can shove VCs into a DDO
  • BTCR can build up a datastructure over time, but mechanism is different btw ledgers
  • what is the best way to mark "go look for next object"
  • we don't have a way to rotate or revoke claim issuer -- see doc for REVOKED
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant