Delegated execution limits
Execution gas caps, schema 21 cumulative limits, and what those limits do and do not cover.
Use test assets only in the current preview. Before relying on cumulative limits, confirm that both API and worker support schema 21 and verify that the returned grant scope retains every requested cap. Installing SDK 1.0.1 alone does not upgrade enforcement.
Per-execution gas cap
Standing EVM grants require rules.evm.maxExecutionGasCostWei, an explicit decimal-string limit. Finite grants may opt in. SDK 1.0.1 exposes the field as optional, so a successful TypeScript check does not prove that a standing grant is valid.
Cumulative encoded components
The optional cumulativeEvmComponents profile uses:
- mode
encoded_native_components_v1; - chain ID
1or11155111— use Ethereum Sepolia in staging; - separate
maxValueWeiandmaxExecutionGasCostWeicaps.
It requires explicitly signed sponsorshipRequested: false, matching Ethereum/Sepolia network and chain, empty calldata 0x, explicit value, and supported type 0/1/2 gas fields. It caps gross encoded native value and maximum execution gas cost.
It does not cap USD value, total wallet loss, token transfers, approvals, L2 fees, sponsor costs, blob transactions, authorization lists or recipient fallback effects. Allowlisted recipients remain trusted.
Reservations and queued work
Reservations are never automatically refunded, including failed signing or ambiguous broadcasts. A null usage value means unavailable or inconsistent data, not zero usage.
Before signing queued work, the worker rechecks current environment policy and delegated authority. Denials do not refund reserved capacity. Already-issued signatures cannot be recalled, and the check is not an atomic guarantee against a concurrent policy change.
See agent session grants, environment policies, and the live developer reference for integration context.