From 9a9910179ed862d2f018e4fa5f2d18085a354632 Mon Sep 17 00:00:00 2001 From: Boris Mann Date: Sat, 2 Aug 2025 17:31:00 -0700 Subject: [PATCH] did web --- _notes/did web.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 _notes/did web.md diff --git a/_notes/did web.md b/_notes/did web.md new file mode 100644 index 0000000..ce5ffef --- /dev/null +++ b/_notes/did web.md @@ -0,0 +1,21 @@ +--- +tags: + - DID + - ATProtocol + - specification + - W3C + - article +link: https://w3c-ccg.github.io/did-method-web/ +published: 2024-07-31 +--- +Unofficial Draft 31 July 2024 +## Abstract + +DIDs 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. + +## ATProto + +Supported by [[ATProtocol]], with some constraints: + +> `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. +> [atproto.com/specs/did](https://atproto.com/specs/did) \ No newline at end of file -- 2.51.2