search

WebOfTrustInfo / btcr-hackathon-2019

BTCR Hackathon 2019
https://weboftrustinfo.github.io/btcr-hackathon-2019/
MIT License
2 stars 0 forks source link

Key Revocation #6

Open OR13 opened 5 years ago

OR13 commented 5 years ago

I've compromised myself 🥇

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

Its for testing purposes for https://github.com/decentralized-identity/well-known/pull/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 commented 5 years ago

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 commented 5 years ago

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.