dev.keytrace.signature
A cryptographic signature attesting to a claim
Details · object
| Kind | object |
|---|---|
| Authority | keytrace.dev |
| Indexed |
Object
objectProperties
The cryptographic signature (base64-encoded).
comment
stringOptional comment or description.
maxGraphemes: 512
Key identifier (e.g., date in YYYY-MM-DD format).
retractedAt
string · datetimeDatetime when this signature was retracted. Present only if the signature has been retracted (ISO 8601).
Datetime when the signature was created (ISO 8601).
Ordered list of field names included in the signed payload (e.g., ['did', 'subject', 'type', 'verifiedAt'])
AT URI reference to the signing key record published by the verification service (e.g., at://did:plc:serviceaccount/dev.keytrace.serverPublicKey/2024-01-15).
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
dev.keytrace.statement
recordA public statement signed by one of the user's own published public keys (dev.keytrace.userPublicKey).
-
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.
-
dev.keytrace.claim
recordAn identity claim linking this DID to an external account
-
Common type definitions for cryptographic signatures attached to records, per the ATProtocol Attestation Specification. Each signature's `$type` says what it attests.
-
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.