Skip to main content
Set the delivery limits controlled by a DID operator. A policy rule may narrow these values but cannot increase them. This mutation uses an authorized DID proof and the current Policy V2 policy_nonce. See Authorize a Directory update.

Request

string
required
The URL-encoded DID. It must equal the signed body did.
object
required
Requested delivery limits. Active values must be positive and at or below their network maxima.
integer
required
Operator-requested Cache retention in clock-time seconds, stored as a positive u32. The chain preserves this request but derives an effective maximum of 172800 seconds.
integer
required
Maximum raw HTTP request envelope. Maximum 26214400.
integer
required
Maximum decoded encrypted message sent without chunking. Maximum 16777216.
integer
required
Maximum decoded bytes in one chunk. Maximum 2097152.
integer
Deprecated Policy V2 wire-compatibility field. Omit it. The Directory encodes the unbounded compatibility sentinel 4294967295.
integer
Deprecated Policy V2 wire-compatibility field. Omit it. The Directory encodes the unbounded compatibility sentinel 65535.
integer
required
Maximum Cache replicas. Maximum 4.
Omit effective_ttl_seconds; it is chain-derived and read-only. The active byte limits must satisfy the consistency rules described in Delivery policies.

Response

202 Response
202 Accepted confirms submission for processing, not final settlement. Read the constraints from finalized state before relying on them.

Straight to the point

  • Proof: authorized DID key
  • Action: set_did_delivery_constraints
  • Nonce: Policy V2 policy_nonce
  • Above-network active byte or replica values: 400 invalid_delivery_constraints
  • TTL above 48 hours: accepted as requested, effective value clamped to 48 hours
  • Accepted submission: 202