com.publicdomainrelay.temp.market.badgeBlueKey

Publishes the public half of a badge.blue attestation key that this repo signs market.* records with. The record key is the key's did:key, so a verifier can look up a key by did:key directly in the author's PDS repo — a PDS-native key registry complementing DID-document key binding.

Details · record, key any
Kindrecord
Record keyany
Authoritymarket.temp.publicdomainrelay.com
Indexed

Record

record · key any

Properties

createdAt

requiredstring · datetime

issuer

string · did

DID (e.g. a did:web) that controls/advertises this key when it is bound to a service identity.

key

requiredstring · did

The did:key of the public key (the same value as this record's key).

Similar lexicons

semantic match

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

  • Associates a device key with a DID, enabling key→DID lookup for vouch graph traversal and service authorization.

  • Reusable types for an at://2048 authority to provide public did:keys and signatures for verification

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

  • A per-device public key bound to an account DID.

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