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

Key Revocation #6

Open
OR13 opened this issue Aug 6, 2019 · 2 comments
Open

Key Revocation #6

OR13 opened this issue Aug 6, 2019 · 2 comments

Comments

@OR13
Copy link

OR13 commented Aug 6, 2019

I've compromised myself 🥇

I added a leaked private key to my brand new BTCR DID :(

Its for testing purposes for decentralized-identity/.well-known#2

Since I'm new to BTCR, I understand that I can just commit to: https://github.com/OR13/self/blob/master/ddo.jsonld

And remove the public key, should I be aware of anything else?

The private key used to create the DID has not (to my knowledge) been stolen.

@ChristopherA
Copy link
Member

Ideally, should rotate your DID to a new transaction, and use all new keys there. However, right now I don't know any BTCR implementations following to the tip.

-- Christopher Allen

@danpape
Copy link
Collaborator

danpape commented Aug 7, 2019

Not that this is super-helpful yet, but Ryan and I have a utility that does follow to the tip (via call outs to chain.so) but then stops. I'm trying to make it at least print an implicit DID for now.

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

3 participants