Expand description
Authoritative direction for did:web / did:key ↔ did:at9p aliasing
(#896 / D4; design #879 Q4, ratified #905 §2/§6).
This is the pure, I/O-free core of the D4 aliasing bridge — the rule
that decides, given a classical DID’s alsoKnownAs claim and a
GATE-verified VerifiedCapsule, whether the two identities are mutually
attested and — when they are — which one is authoritative. The I/O half
(fetch the capsule bytes from an untrusted locator, run GATE) composes this
rule and lives in hyprstream-discovery::at9p_alias, sibling to the D1
capsule resolver.
§The authoritative-direction rule
A did:web / did:key identity can declare (via alsoKnownAs) that it is
also a did:at9p. The reverse vouch lives inside the at9p capsule body
(the [CapsuleBody::also_known_as] field, #896 schema). Two legs therefore
exist, of different strength:
| leg | carrier | signature strength |
|---|---|---|
| at9p → classical | the GATE-verified capsule body’s alsoKnownAs | Hybrid (EdDSA + ML-DSA-65, pinned) |
| classical → at9p | the classical DID document’s alsoKnownAs | Classical (the doc’s best) |
The ratified semantics (#905 §2/§6) are:
- Bidirectional to be believed. Both documents must name each other. A
one-way claim is not trusted →
Err. - at9p is authoritative. The content-verified capsule (BLAKE3-512
self-certifying, hybrid-signed) is the stronger identity. When the
attestation is mutual, the at9p identity is authoritative at
PqHybridassurance — the assurance of the capsule leg actually walked. - Assurance = the leg walked, never the max. A verifier reaching the
identity through the classical leg lands
Classical; reaching it through the GATE-verified capsule landsPqHybrid. This rule is only ever evaluated with aVerifiedCapsulein hand (the capsule leg was walked), so its result isPqHybrid.
at9p is the PQ upgrade path, additive to — not a replacement for — a
principal’s classical atproto identity (the method-allowlist bridge: public
atproto infra accepts only did:plc/did:web as repo authorities, so
public records publish under the classical DID with alsoKnownAs to the
at9p identity; our own PDS accepts did:at9p natively, #908/G3).
Structs§
- Authoritative
Identity - The authoritative identity resolved through the at9p aliasing bridge.
Functions§
- classical_
aliases - The classical aliases a verified
did:at9pcapsule attests to — the method-allowlist bridge (#905 §6). - resolve_
authoritative_ alias - Resolve the authoritative identity for
classical_didvia mutualalsoKnownAsattestation with a GATE-verifieddid:at9pcapsule.