tech.lenooby09.didgit.signatureProof

A cryptographic proof that a did-git object was signed by a specific DID. This provides key-rotation-independent verification by anchoring the proof to a PDS or signing event.

Details · record, key any
Kindrecord
Record keyany
Authoritydidgit.lenooby09.tech
Indexed

Record

record · key any

Properties

objectId

requiredstring

The hex SHA-256 object ID being proven.

  • maxLength: 64

objectType

requiredstring

The type of object.

  • maxLength: 16
  • knownValues: blob | tree | commit | tag

The PDS endpoint that issued this proof (for service auth proofs).

  • maxLength: 256

signature

requiredstring

The base64url-encoded signature or JWT token.

  • maxLength: 2048

signatureType

requiredstring

The signature algorithm or token type (e.g., 'atproto-service-auth', 'jws', 'raw-ed25519', 'raw-ecdsa-secp256k1').

  • maxLength: 64

signedAt

requiredinteger

Unix timestamp (seconds) when the proof was created.

signer

requiredstring

The DID of the signer.

  • maxLength: 128

Similar lexicons

semantic match

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

  • A cryptographic signature attesting to a claim

  • 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 did-git object stored in an AT Protocol repository. Each record represents a single content-addressable object (blob, tree, commit, or tag), keyed by its hex SHA-256 object ID.

  • 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 ATProtocol Attestation Specification.

  • An atproto identity (did:plc / did:web) endorses a local kvcs patch-signing key (did:key / did:jwk) by hosting this record on its PDS. Existence of the record over an OAuth-authenticated write proves the atproto DID consented to the binding; the inner JWS proves the local key consented in turn.