Execution safety
The guarded execution pipeline: kill switches, exact-bound short-lived authorizations, and reconciliation. Every intent is fail-closed unless a matching short-lived authorization is presented and consumed.
Kill switch
loading…
Reconciliation
loading…
Guarded execution demo
Step 1: an authorization is minted for the exact intent parameters (60s TTL, single use). Step 2: submitting runs the full guard pipeline — kill switch, idempotency, policy engine, authorization binding, limits, liquidity, simulation, fee/slippage bounds, and chain-specific transaction validation — before a signed receipt is produced. In paper mode the receipt is a mock-signed artifact; in live mode the same pipeline broadcasts a real transaction.
Security properties (implemented and tested): replay and duplicate submissions fail closed; altered parameters (intent-hash-mismatch), wrong chain, expired/revoked/missing authorizations, excessive spend over per-user and per-strategy caps, position and daily-loss caps, insufficient liquidity, fee/slippage/price-impact bounds, simulation uncertainty, and kill switches all reject with typed codes. The frontend holds no keys, secrets, or signing logic and cannot bypass a guard.