tech.lenooby09.kvcs.signingKey

A bidirectional binding between this repo's atproto DID and a kvcs local signing key. Verifiers MUST check that `jws` is a valid compact JWS produced by `localDid` over the canonical JSON `{atprotoDid, localDid, jwk}`; records without a verifying inner JWS are ignored.

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

Record

record · key any

Properties

createdAt

requiredstring · datetime

ISO-8601 timestamp at which the endorsement was issued.

jwk

requiredunknown

The localDid's verification method as a JWK (`kty`, `crv`, `x`, optionally `y` / `kid`). Public-only; never includes the private `d` coordinate.

jws

requiredstring

Detached compact JWS by `localDid` over the canonical JSON `{atprotoDid, localDid, jwk}`, where `atprotoDid` is the repo this record lives under. 8192 chars covers Ed25519 / ES256 / ES256K compact-JWS sizes with a comfortable margin.

  • maxLength: 8192

localDid

requiredstring

The local kvcs signing DID being endorsed (did:key:... or did:jwk:...). Capped at 2048 chars to accommodate did:jwk values whose method-specific id embeds a base64url-encoded JWK.

  • maxLength: 2048

Similar lexicons

semantic match

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

  • 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 signed kvcs tag, addressable on the tagger's atproto PDS. The rkey is the canonical-JSON digest of the tag payload (lower-case hex BLAKE3 multihash).

  • Common type definitions for cryptographic signatures attached to records, per the ATProtocol Attestation Specification. Each signature's `$type` says what it attests.

  • A cryptographic signature attesting to a claim

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