org.eu.net.pool.gpgkey
establishes a bidirectional many-to-many link between a DID and an associated GPG key. the rkey of this record must be the fingerprint of the GPG key, encoded in lowercase hexadecimal with no prefix, suffix, or delimiter.
Details · record, key any
| Kind | record |
|---|---|
| Record key | any |
| Authority | pool.net.eu.org |
| Indexed |
Record
record · key anyProperties
base64-encoded detached signature of the canonical at:// uri of this record, to prove the DID's ability to use the key.
base64-encoded GPG key as produced by `gpg --export $rkey | base64 -w0`. the export must consist of exactly one key.
at uri of this record with the owning DID replaced by handle.invalid. used to search keys by fingerprint.
Similar lexicons
semantic matchLexicons 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.
-
org.zerosum.deviceKey
recordA per-device public key bound to an account DID.
-
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.
-
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.