Skip to main content

Module repo_authority

Module repo_authority 

Source
Expand description

Which DID methods our PDS accepts as a repo authority — the account DID that owns a repository and signs its commits (#908, design #905 §6).

Public atproto infrastructure allowlists only did:plc and did:web as repo authorities. hyprstream additionally accepts did:at9p (the self-certifying hybrid-PQC capsule identity, #879/#880) on our own side: a did:at9p account can own and sign a repo hosted by our PDS. Public publication of such a repo goes through the #896 alsoKnownAs bridge, which republishes under a classical did:web/did:plc authority that public infra will accept — so accepting did:at9p here never implies public infra must.

Public authorities are validated as complete repository identifiers, not DID URLs. Host-form web authorities use the hosted-account DNS rules plus atproto’s top-level-domain restrictions, with an explicit self-hosted OAuth extension for canonical encoded ports (including .test hosts). This extension does not imply interoperability with public AT Protocol services. PLC authorities require their full base32 identifier. Native at9p capsule validation remains the native resolver’s responsibility. This is not a signature or ownership check (see crate::commit::Commit::verify).

Enums§

RepoAuthority
A DID method our PDS accepts as a repo authority.

Functions§

accept_repo_authority
Classify did as an accepted repo authority for our PDS, or reject it.
is_path_form_did_web
Whether did is a path-form did:web identifier.