Expand description
#896 (at9p D4) — did:web / did:key → did:at9p aliasing resolver:
resolves a classical DID to its authoritative did:at9p identity via mutual
alsoKnownAs attestation + the GATE pipeline. Sibling to at9p_resolver.
did:web / did:key → did:at9p aliasing resolver (#896 / D4; design
#879 Q4, #905 §2/§6).
This is the I/O half of the D4 aliasing bridge. It composes the
untrusted [CapsuleSource] + GATE pipeline (D1 / #893) with the pure
authoritative-direction rule (hyprstream_pds::at9p_alias) to resolve a
classical DID to its authoritative did:at9p identity when — and only when
— the two are mutually alsoKnownAs-attested. Sibling to
crate::at9p_resolver::At9pResolver: where that turns a did:at9p into
dialable reach, this turns a classical DID + its at9p claim into the
authoritative at9p identity (and its assurance).
§Fail-closed posture
An authoritative identity is emitted only when:
- the capsule named by the classical leg fetches and passes the full GATE pipeline (canon → hash → sig), and
- both legs name each other (mutual attestation).
Any GATE failure, a classical leg pointing at a different capsule, or a
capsule that does not reciprocate the classical DID returns Err — never a
partial or one-way trust upgrade. See hyprstream_pds::at9p_alias for the
authoritative-direction rule and the two-leg strength table.
Structs§
- At9p
Alias Resolver did:web/did:key→did:at9paliasing resolver.