You can absolutely convert a did:key to a did:btrc, or a did:ion or did:elem for that matter... in fact, you could start with a did:key and end with a did:v1, did:peer, did:ion and did:elem.... and if we can ever agree on the concept of https://www.w3.org/TR/did-core/#equivalence we could link them all :) I'd love to collaborate on did:torv3 please link a repo if possible. OS On Fri, Jun 12, 2020 at 12:00 PM Christopher Allen < ChristopherA@lifewithalacrity.com> wrote: > > > On Fri, Jun 12, 2020 at 9:35 AM Daniel Hardman <daniel.hardman@evernym.com> > wrote: > >> I'm just noting that did:peer was recently updated to provide an upgrade >> path from did:key that may be helpful in some cases. You can create a >> did:key and then begin using it as a did:peer when you need endpoints or >> additional key complexity (e.g., rotation, multiple key values, different >> key types). This allows you to preserve the "no blockchain or network >> required" characteristic longer than would be possible otherwise. >> > > I’m investigating if you can use the secp256k1 version of did:key for a > time then bootstrap into one of the Bitcoin network DIDs like did:btcr. > > I’m also interested in investigating soon a possible did:torv3 Métis which > is like did:web: but uses the distributed 25519 keys that Tor V3 uses. > > — Christopher Allen [via iPhone] > >> -- *ORIE STEELE* Chief Technical Officer www.transmute.industries <https://www.transmute.industries>
Received on Friday, 12 June 2020 17:04:09 UTC