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

Revocation Reason Codes #20

Open
kimdhamilton opened this issue Jul 15, 2017 · 1 comment
Open

Revocation Reason Codes #20

kimdhamilton opened this issue Jul 15, 2017 · 1 comment
Assignees
Labels

Comments

@kimdhamilton
Copy link
Contributor

From @ChristopherA on June 30, 2017 7:2

The easiest way to revoke a DID is to just spend the previously unspent funds on the tip.

This technique was inspired by my revoke-ssl approach suggested in https://github.com/ChristopherA/revocable-self-signed-tls-certificates-hack and presented at https://www.meetup.com/SF-Bitcoin-Devs/events/222712738/

In that proposal it was suggested that optionally the op_return could encode the reason for the revocation. For instance: key compromise, change of affiliation, superseded, cease of operation, or unspecified, hold

Copied from original issue: WebOfTrustInfo/btcr-hackathon-2017#5

@kimdhamilton
Copy link
Contributor Author

TODO: Ryan Grant is an assignee too

@xrgrant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants