...
did:webs and did:webvh are web-based DID methods where the DID is bound to the location of a specific web server. While some degree of portability is still possible by using the DID document alsoKnownAs property to establish synonyms with other DIDs, this design does not support the requirement for the DID alone be able to serve as a permanent immutable account identifier (for more about this requirement, see Appendix B).
did:jlinc is now being adapted for use with a federated network of servers to increase portability. However it is not currently designed for peer-to-peer usage.
did:plc uses SCIDs but in its current implementation uses a centralized directory service operated by Bluesky.
did:scid can address all of these limitations without requiring new formats for SCIDs or SCID verification metadata. It can reuse the formats listed above. While in theory did:scid could choose to support only one of these formats, picking one would discriminate against the others. Since all three these formats have their adherents—and existing code bases that support them—did:scid is designed to support all threeany of them, and be extensible to support other SCID-based formats if necessary. This enables adopters to choose the SCID format that works best for them, and for these formats to evolve over time.
...