app.certified.signature.proof

Remote attestation proof containing the CID of the content being attested.

Repository @certified.app did:plc:apun3uo5jqm34pxzqq6on754 namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authoritysignature.certified.app
Indexed

Record

record · key tid

Properties

cid

requiredstring · cid

CID of the attested content, computed per the ATProtocol Attestation Specification: encode the attested record with its `signatures` field removed and a temporary `$sig` object inserted as canonical DAG-CBOR, then SHA-256 hash to produce a 36-byte CIDv1. `$sig` is this proof record without its `cid` field (so `$type`, plus `note` and `createdAt` when set), plus `repository`: the DID of the repository that holds the attested record.

createdAt

string · datetime

Client-declared timestamp when this proof was created.

note

string

Optional note explaining the attestation purpose or context.

  • maxLength: 500

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • 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

  • 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.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.

  • A cryptographic proof record that validates an endorsement by containing the CID of the endorsement content.

  • A service attestation proving a FreeMix record existed with specific content at a specific time. Created by the FreeMix attestor service in its own repo as an independent witness.