Skip to main content

Module claim

Module claim 

Source
Expand description

Single-use claims for connections belonging to a supervised spawn.

These standalone bodies use channel 0, the connection’s control lane. Merely defining them does not advertise daemon support for either operation. Success uses a RESPONSE; refusals use crate::ErrorBody and the codes in crate::error_codes. Claims grant nothing until the daemon consumes them.

Structs§

Claim
An opaque bearer claim. Debug output is always redacted, including when a containing request or reply is formatted. Never log the serialized body or exposed value, or put the claim in argv or an environment variable.
ClaimMintReply
One single-use 128-bit base64url claim, redeemable for 30 seconds on the daemon’s monotonic clock. The wall-clock expiry is informational only; readers must not use it to decide that a claim is still valid.
ClaimMintRequest
Mint only over the spawn’s live primary registration channel. Claim-bound connections cannot mint. Refusals never permit falling back to direct.
ClaimPresentReply
Acceptance of a single-use claim. Refusals use an ERROR frame, never this ACK.
ClaimPresentRequest
The first frame after a new connection’s handshake. Acceptance consumes the claim and binds the connection atomically while rechecking the live spawn. Any refused presentation closes the connection, including a retryable refusal; it never continues as direct.
ClaimRateLimitedDetail
Backoff carried in crate::ErrorBody::detail for claim_rate_limited.

Enums§

ClaimPurpose
The authority requested for one additional connection. Only a prefix claim carries a module id. The daemon checks its grammar and that the minting module owns the longest matching reserved prefix, excluding exact reserved or gated ids and prefixes without an owner.