network.attested.signature

johnandersen777.bsky.social View official

Documentation

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.

main object

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 string cid Required

The computed canonical attestation CID (base32 CIDv1) this entry signs.

issuedAt string datetime Optional

An RFC 3339 formatted timestamp.

issuer string did Optional

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.

key string Required

did:key public-key reference used to verify the signature.

role string Optional

Optional role this signature attests in a multi-party workflow (e.g. 'proof-of-settlement', 'broker'), letting verifiers require specific attestation completeness.

signature bytes Required

Low-S normalized ECDSA signature over the CID bytes.

View raw schema 
{
  "type": "object",
  "required": [
    "key",
    "cid",
    "signature"
  ],
  "properties": {
    "cid": {
      "type": "string",
      "format": "cid",
      "description": "The computed canonical attestation CID (base32 CIDv1) this entry signs."
    },
    "key": {
      "type": "string",
      "description": "did:key public-key reference used to verify the signature."
    },
    "role": {
      "type": "string",
      "description": "Optional role this signature attests in a multi-party workflow (e.g. 'proof-of-settlement', 'broker'), letting verifiers require specific attestation completeness."
    },
    "issuer": {
      "type": "string",
      "format": "did",
      "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."
    },
    "issuedAt": {
      "type": "string",
      "format": "datetime"
    },
    "signature": {
      "type": "bytes",
      "description": "Low-S normalized ECDSA signature over the CID bytes."
    }
  },
  "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."
}
signatures array

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.

View raw schema 
{
  "type": "array",
  "items": {
    "refs": [
      "network.attested.signature",
      "com.atproto.repo.strongRef"
    ],
    "type": "union"
  },
  "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."
}

Lexicon Garden

@