Lexicon Garden

com.fedproxy.temp.xrpc.registration

A subscriber's signed registration. Proves custody of the did:key by carrying badge.blue attestations (network.attested.signature) over the nonce returned from com.fedproxy.temp.xrpc.getRegistrationNonce. Presented as the parameter to com.fedproxy.temp.xrpc.subscribe to open a relay channel bound to this key.

Repository @johnandersen777.bsky.social did:plc:5svqtrhheairglgiiyvutzik namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authorityxrpc.temp.fedproxy.com
Indexed
Compare Edit in builder → Fork →

Record

record · key tid

Properties

key

requiredstring

did:key public-key reference that signed the nonce; must match the key passed to getRegistrationNonce.

nonce

requiredbytes

The 64-byte nonce issued by com.fedproxy.temp.xrpc.getRegistrationNonce that this registration signs over.

signatures

requiredref

badge.blue attestations (network.attested.signature) over the issued nonce, proving liveness and custody of the did:key.

Reference

Similar lexicons

semantic match

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

  • com.fedproxy.temp.xrpc.getRegistrationNonce

    procedure

    Request a one-time registration nonce from the relay before subscribing. The caller presents its did:key and badge.blue attestations (network.attested.signature) over its own key material; the relay replies with a crypto-secure random nonce and its own attestations over that nonce. The subscriber then signs the returned nonce and presents the resulting com.fedproxy.temp.xrpc.registration record as the parameter to com.fedproxy.temp.xrpc.subscribe, proving liveness and key custody and binding the

  • com.fedproxy.temp.xrpc.subscribe

    subscription

    Open a relay channel. The subscriber presents a com.fedproxy.temp.xrpc.registration: a record signed (network.attested.signature) over the nonce previously issued by com.fedproxy.temp.xrpc.getRegistrationNonce. The relay verifies the registration's signatures against the issued nonce and the did:key, then binds the WebSocket to that key. On connect the relay sends a #registered frame with the assigned serviceId/proxyRef; subsequent #request frames carry inbound XRPC calls the subscriber answers

  • com.publicdomainrelay.temp.market.badgeBlueKey

    record

    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.

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

  • com.atprotofans.brokerProof

    record

    Broker attestation proof for a supporter relationship. When inline, cid and signature are required. When remote, only cid is required.