network.attested.signature

johnandersen777.bsky.social View official

{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "description": "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.",
      "properties": {
        "cid": {
          "description": "The computed canonical attestation CID (base32 CIDv1) this entry signs.",
          "format": "cid",
          "type": "string"
        },
        "issuedAt": {
          "format": "datetime",
          "type": "string"
        },
        "issuer": {
          "description": "DID of the signing party (e.g. the did:web of the service holding the key). Verifiers may bind `key` to this DID's document when the authoring account's DID document does not list it.",
          "format": "did",
          "type": "string"
        },
        "key": {
          "description": "did:key public-key reference used to verify the signature.",
          "type": "string"
        },
        "role": {
          "description": "Optional role this signature attests in a multi-party workflow (e.g. 'proof-of-settlement', 'broker'), letting verifiers require specific attestation completeness.",
          "type": "string"
        },
        "signature": {
          "description": "Low-S normalized ECDSA signature over the CID bytes.",
          "type": "bytes"
        }
      },
      "required": [
        "key",
        "cid",
        "signature"
      ],
      "type": "object"
    },
    "signatures": {
      "description": "An attestation signatures array: inline network.attested.signature entries and/or strongRefs to remote network.attested.proof records. Always stripped from the record before attestation-CID computation, so attaching attestations never changes the signing payload.",
      "items": {
        "refs": [
          "network.attested.signature",
          "com.atproto.repo.strongRef"
        ],
        "type": "union"
      },
      "type": "array"
    }
  },
  "id": "network.attested.signature",
  "lexicon": 1
}

Validate Record

Validate a record against network.attested.signature

Validation Options
Treat any remaining unresolved references as valid

Metadata

DID
did:plc:5svqtrhheairglgiiyvutzik
CID
bafyreiadzaqv2rfql3uf4xnv2dzgfgxsbr665sqg3n5s34d3vylbsx6rii
Indexed At
2026-07-26 20:05 UTC
AT-URI
at://did:plc:5svqtrhheairglgiiyvutzik/com.atproto.lexicon.schema/network.attested.signature

Similar Lexicons

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

  • Common type definitions for cryptographic signatures attached to records, per the ATProtocol Attestation Specification.

  • network.attested.proof recordnot 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.at…

  • A remote attestation proof record holding the CID of attested content. Lives in the attestor's repository and is referenced from the attested record's `signatures` array via `com.atproto.repo.strongRef`. Conforms to the…

  • A cryptographic signature attesting to a claim

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

Lexicon Garden

@