Pre-Draft Feedback on WoT Enrolment Transaction BIP
kimdhamilton opened this issue · comments
From @veleslavs on July 9, 2017 12:29
Myself and @jonasschnelli have been brainstorming and working in private about a proposed Identity Enrolment Transaction for Bitcoin (and other comparable blockchains).
We would certainly welcome more pre-draft feedback on this work-in-progress BIP.
cc: @muneeb-ali @shea256 @jcnelson @ChristopherA
Copied from original issue: WebOfTrustInfo/btcr-hackathon-2017#24
From @ChristopherA on July 9, 2017 19:36
Thank you for sharing this — I appreciate the proposal! It is quite possible we should implement an approach in this directly instead of our own.
One hope that we had with DID:BTCR was that we would not only be able to revoke, but alternatively rotate the old public key to a new one, rather than the only choice being to revoke. Is there some way to adapt your proposal to do that?
Our second hope is that would be some way way to discover solely from blockchain data a place to store an optional DID Descriptor Object (DDO) associated with that DID. That way we can store additional information, like PGP keys, alternative keys, etc. about the identity. Maybe one of the hashes can be used to look up a IPNS object? Not sure. ( @jbenet any chance you have an idea here? )
BTW, one value of working with us is that we are proposing this through the W3C Credentials community as an international standard (I am co-chair and several of people in the hackathon are deeply involved in W3C and the web payments standards). Simply changing your format to did:tx1:rk63-uvxf-9pqc-sy (i.e tx1 is your method, and add did to the front) and creating the BIP to also serve as a W3C DID method spec, your proposal would not only be a BIP, but also be on standards track to be an international standard.
If we can find a way to rotate keys and be able to get a value so that we can discover a DDO (and confirm that the DDO is signed by the current rotated key), I'd be glad to drop calling it BTCR method and use your TX1 method and help get it standardized.
If we can also address @sipa's thoughts about using a sign-to-contract signature as well (as per discussion is #2) the combo could be a huge win!
Move to RWoT. Create TX1 method