- did:oyd seems to generate non-permanent identifiers. These identifiers change each time a corresponding DID document is updated. In my opinion that negates the primary reason to use DID in the first place.
- did:keri is quite complicated and I can’t figure out how it works. For some reason, authors chose to skip the most important part of the resolution algo: The method for discovering the Key Event Log is outside the scope of this specification. Possible implementations include the use of a Distributed Hash Table (DHT), anchoring a KEL in a ledger or the use of a gossip protocol involving a witness network.
- did:plc is a joke. Everything is stored on a single server controlled by BS.
3 Likes