Transactions

Direct wallet actions

Non-price-sensitive actions such as account creation, collateral approval, deposit, withdrawal, session creation, revocation, and conditional creation can call their contracts directly after simulation.

Reported price actions

Open, reduce, close, strategy execution, conditional execution, and liquidation require fresh reports. The server route:

1. validates request fields
2. fetches a fresh report for each market
3. ABI-encodes the protocol call
4. wraps it in oracle-router execution
5. simulates against the configured RPC
6. returns transaction data to the wallet

The wallet remains the sender for direct user actions.

Delegated actions

Delegated intents use EIP-712 signatures rather than a pre-signed raw transaction. The message commits to the session, owner, action, market, position, side, size, collateral, leverage, nonce, and expiry. The keeper submits the final transaction only after checking the signature and current on-chain session.

Slippage

Wallet-reviewed requests include an expected price and maximum slippage in basis points. The contract compares that bound against the report-selected bid or ask. A validly signed report cannot override the user's slippage limit.

Simulation

Simulation is required before submission by the production transaction builders and keeper. It catches stale reports, closed markets, insufficient collateral, session limits, trigger state, slippage, leverage, open-interest, and other contract reverts before gas is spent where possible.

Receipts

The UI reports wallet submission state immediately. The indexer later assigns confirmation-aware canonical history. Automation workers wait for configured receipt confirmations and persist transaction hashes and failures for deduplication and monitoring.