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.

Sign up for GitHub

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

Jump to bottom

Revocation Reason Codes #5

Closed
ChristopherA opened this issue Jun 30, 2017 · 2 comments
Closed

Revocation Reason Codes #5

ChristopherA opened this issue Jun 30, 2017 · 2 comments
Assignees
@ChristopherA

Comments

@ChristopherA
Copy link
Member

ChristopherA commented Jun 30, 2017 •
edited by kimdhamilton
Loading

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
This was referenced Jun 30, 2017
Closed
Closed
@kimdhamilton
Copy link
Collaborator

kimdhamilton commented Jul 14, 2017 •
edited
Loading

TODO: Ryan Grant is an assignee too

@xrgrant

@kimdhamilton kimdhamilton mentioned this issue Jul 15, 2017
Open
@kimdhamilton
Copy link
Collaborator

This issue was moved to WebOfTrustInfo/rwot5-boston#20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ChristopherA ChristopherA

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ChristopherA @kimdhamilton