Skip to main content

Module at9p_alias

Module at9p_alias 

Source
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:

legcarriersignature strength
at9p → classicalthe GATE-verified capsule body’s alsoKnownAsHybrid (EdDSA + ML-DSA-65, pinned)
classical → at9pthe classical DID document’s alsoKnownAsClassical (the doc’s best)

The ratified semantics (#905 §2/§6) are:

  1. Bidirectional to be believed. Both documents must name each other. A one-way claim is not trusted → Err.
  2. 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 PqHybrid assurance — the assurance of the capsule leg actually walked.
  3. 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 lands PqHybrid. This rule is only ever evaluated with a VerifiedCapsule in hand (the capsule leg was walked), so its result is PqHybrid.

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§

AuthoritativeIdentity
The authoritative identity resolved through the at9p aliasing bridge.

Functions§

classical_aliases
The classical aliases a verified did:at9p capsule attests to — the method-allowlist bridge (#905 §6).
resolve_authoritative_alias
Resolve the authoritative identity for classical_did via mutual alsoKnownAs attestation with a GATE-verified did:at9p capsule.