Replying to Avatar elsat

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 why does mstr insist on using “the blockchain” for DID?

Is there no other practical way to add key rotation?

https://github.com/MicroStrategy/did-btc-spec/issues/7#issuecomment-2245601679

Key rotation for a ‘name’, not an identifier. I’ve been looking at this problem for a long while and have concluded that this problem needs to be solved at a higher level. I think a trusted nip05 provider that keeps a history of keys (npubs), is a better approach. I think key rotation at the did:method level is not the way to go.

Reply to this note

Please Login to reply.

Discussion

No replies yet.