Massive scale for DIDs
#ssi #sidetree #did #web3 Decentralized ids https://www.w3.org/TR/did-core/ is a core of web3 identity. It allows you to distribute your identity and public keys without a central server. Currently, you could find hundreds of did methods — a quite good list of methods can be found here https://w3c.github.io/did-spec-registries/#did-methods. Some methods are on-chain, and it is quite interesting from a security and trust perspective. A major on-chain challenge is the cost of single did creation. Quite often 1 did is the cost of a single transaction on a blockchain. It is no go if we need to produce large amount of did. One of the ways of solving scalability issue and massive did anchor is L2 protocols on top of blockchain. The most mature one currently is #sidetree protocol. https://identity.foundation/sidetree/spec/ protocol defines how you interact with ledger and operation storage, but keep all tech decision open for the development team. Side tree operate with CRDT types for did document operations (create, update , recover, deactivate). Did document state could be changed by (add-public-keys ,remove-public-keys ,add-services, remove-services ,ietf-json-patch). As result, we have granular control over a did document and flexibility of adding keys and services — it is not true for big amount of on-chain methods that I have seen so far. On Affinidi SDK, we use a did element https://element-did.com/#:~:text=Welcome%20to%20Element,identity%20provider%2C%20or%20certificate%20authority. On top of Ethereum and IPFS. Popular side tree did methods —
