com.fedproxy.temp.xrpc.getRegistrationNonce

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 WebSocket session to the key.

Details · procedure
Kindprocedure
Authorityxrpc.temp.fedproxy.com
Indexed

Procedure

procedure · POST

Input

application/json

key

requiredstring

did:key public-key reference the caller will use to sign the returned nonce.

signatures

requiredref

badge.blue attestations (network.attested.signature) presented by the caller over its key material.

Output

application/json

nonce

requiredbytes

Crypto-secure random nonce, 64 bytes, that the caller must sign to complete registration.

signatures

requiredref

badge.blue attestations (network.attested.signature) from the relay over the issued nonce.

Errors

InvalidRequest

Malformed body, missing fields, or unverifiable caller signatures.

Similar lexicons

semantic match

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

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

  • 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