Did peer - https://identity.foundation/peer-did-method-spec/ It is a hidden gem of did methods - it full function off-chain method did:peer is generation algorithm for diddocs + protocol In a wide range of systems, we recommend having a did per transaction or did per transaction parties. It could cost a lot with a classical on-chain solution, and if we have quite frequent transactions even with l2 protocols, it could not be feasible. With a did: peer, we get

• zero cost did
• zero propagation time
• storage is on a peer side
• did is upgradable we could go from simple method 0 key did to method 1 full scale updatable did docs
• arbitrary cryptography and even mixed cryptography for keys
• the possibility of building a complex did document
• quite complex authorization mechanism that allows mimicking complex topology