Expand description
The DID document that backs an agent account.
A document says where an account is and who signs for it. atproto reads
the id, the alsoKnownAs handle, the #atproto signing key and the
#atproto_pds service entry. Beside those, every hosted account names
its operator: the human who answers for it, one read away from any
depth of the tree. How a process logs in as the account is not in the
document at all; that is the account’s bot.did.credential records.
Structs§
- Claim
- One claim an ID token must carry to be this account.
- DidDocument
- A DID document, reduced to the fields this crate consumes.
- Oidc
Identity - The OpenID Connect identity an account is.
- Service
- One service endpoint in a DID document.
- Verification
Method - One public key in a DID document.
Constants§
- ATPROTO_
KEY_ FRAGMENT - Fragment identifying the atproto signing key within a DID document.
- ATPROTO_
PDS_ FRAGMENT - Fragment identifying the account’s PDS within a DID document.
- DEFAULT_
CONTEXT - JSON-LD contexts a spec-compliant atproto DID document declares.
- MULTIKEY_
TYPE - The
typeatproto requires on the signing key’s verification method. - OPERATOR_
PROPERTY - The property naming the human who answers for a hosted account. Not a DID Core property: a didbot deployment writes it, and a reader that does not know it ignores it, which is what every atproto resolver does.
- PDS_
SERVICE_ TYPE - The
typeatproto requires on the PDS service entry.
Functions§
- owns_
fragment 🔒 - Whether
idissubject’s ownfragmententry; seeDidDocument::owns_fragment.