Skip to main content

Transactions and authorization

The utility contracts compose the app's transaction flow. RouterContract batches calls. FeeForwarderContract collects a token fee and invokes a target. SessionPolicyContract restricts smart-account authorization contexts.

ReferenceWhat it defines
Market routerThe four router entry points, Call, strict and isolated execution, and result encoding.
Fee forwarderforward, forward_dynamic, signed arguments, the fee allowance, errors, and events.
Session policyFixed contract permissions, token destinations, the pinned fee recipient, and policy errors.
Wallet factorySmart-account creation, constructor inputs, and deterministic addresses.

The market enforces order authorization and execution gates. The router has no persistent state, funds, owner, or special market authority. Each target enforces its own authorization. The forwarder authenticates its fee payer before it invokes the target.

For the user-facing signing flow, read What you sign. Current contract addresses appear in Deployments.