At this level
network.attested · 3- network.attested.proof record not from the namespace authority A remote attestation proof: a standalone record in the attestor's repository that binds, via a canonical attestation CID, to a subject record living elsewhere. Referenced from the subject's `signatures` array via com.atproto.repo.strongRef. The `cid` is computed from the subject record (signatures stripped) with this record's metadata (cid/signature/signatures stripped, `repository` = subject's repo DID added) inserted as $sig, DAG-CBOR + SHA-256 + CIDv1. Verifiers recompute that CID and require
- network.attested.signature object not from the namespace authority An inline attestation: an ECDSA signature over a canonical attestation CID, embedded directly in a record's `signatures` array. The CID is computed from the record (signatures stripped), this entry's metadata (cid/signature stripped, `repository` = authoring repo DID added) inserted as $sig, DAG-CBOR + SHA-256 + CIDv1 (dag-cbor codec). Signatures are low-S normalized; supported curves are P-256 and K-256 (did:key). This is the shared network.attested.* vocabulary any speaker can verify.
- network.attested.verify query not from the namespace authority Verify the attestations on a record. Resolves the record at `uri`, recomputes the canonical attestation CID, and checks each entry in its signatures array: inline network.attested.signature entries are verified by ECDSA against `key`; remote strongRefs are resolved to network.attested.proof records whose `cid` must match the subject's canonical CID. Any network.attested.* speaker can call this to verify without re-deriving the CID machinery.
- network.attested.payment.initiate procedure Begin a payment flow. Called by the payer's client against the selected payment servicer using inter-service authentication. Returns an opaque token for status polling and a URL to direct the payer through the payment process in a browser.
- network.attested.payment.lookup query Look up verified payment records between a payer and a recipient. Returns only records whose attestations have been cryptographically verified. Results may include any combination of oneTime, recurring, and scheduled payment records.
- network.attested.payment.oneTime record A one-time payment from a supporter to a creator. Represents a single, non-recurring financial transaction attested by one or more parties.
- network.attested.payment.proof record A remote attestation record stored in the attestor's repository (creator or broker). Referenced via com.atproto.repo.strongRef in the payment record's signatures array. The attestation CID is computed per the badge.blue spec from the payment record, attestation metadata, and the repository DID — meaning a record copied to a different repository automatically invalidates all its attestations.
- network.attested.payment.recurring record A recurring payment commitment. Immutable once created — supporters cancel and create new subscriptions to change terms. Bills on anniversary dates with automatic retry on failure.
- network.attested.payment.scheduled record A fixed series of payments. Unlike recurring payments that continue indefinitely, scheduled payments specify a total count and terminate automatically upon completion.
- network.attested.payment.status query Check the status of a payment initiated via network.attested.payment.initiate. Returns the current status and, when completed, a com.atproto.repo.strongRef pointing to the attested payment record in the payer's repository.