The bmannconsulting.com website
1--- 2tags: 3 - DID 4 - ATProtocol 5 - specification 6 - W3C 7 - article 8link: https://w3c-ccg.github.io/did-method-web/ 9published: 2024-07-31 10--- 11Unofficial Draft 31 July 2024 12## Abstract 13 14DIDs that target a distributed ledger face significant practical challenges in bootstrapping enough meaningful trusted data around identities to incentivize mass adoption. We propose a new DID method using a web domain's existing reputation. 15 16## ATProto 17 18Supported by [[ATProtocol]], with some constraints: 19 20> `did:web`, which is a W3C standard based on HTTPS (and DNS). The identifier section is a hostname. This method is supported in atproto to provide an independent alternative to `did:plc` [[DID PLC]]. The method is inherently tied to the domain name used, and does not provide a mechanism for migration or recovering from loss of control of the domain name. In the context of atproto, only hostname-level `did:web` DIDs are supported: path-based DIDs are not supported. The same restrictions on top-level domains that apply to handles (eg, no `.arpa`) also apply to `did:web` domains. The special `localhost` hostname is allowed, but only in testing and development environments. Port numbers (with separating colon hex-encoded) are only allowed for `localhost`, and only in testing and development. 21> [atproto.com/specs/did](https://atproto.com/specs/did)