You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
The text was updated successfully, but these errors were encountered: