Intent-based execution
Intent-based execution is a design pattern in which a user states what they want, such as a trade with a minimum amount received and an expiry, and the system works out how to carry it out across networks. On SODAX, a permissioned solver within the SODAX system performs the fill.
What it refers to
Intent-based execution is a design approach where the user specifies what they want to happen, not how it should happen.
Instead of building a sequence of transactions across networks, the user submits an intent: a structured request that states what they want (such as "trade 100 USDC on Base for ETH on Arbitrum") along with limits (minimum amount received, expiry time, acceptable slippage).
The system then works out the execution path, weighing liquidity, gas costs, routes between networks and network conditions to find a reliable way to fulfil the intent. On SODAX, SODAX routes, quotes and settles, and a permissioned solver within the SODAX system performs the fill.
This pattern is distinct from transaction-based execution, where the user or application must specify every step.
Why this concept exists
Cross-network financial actions are complex. A single trade across two networks may involve moving value between networks, local trades, liquidity sourcing, gas management and settlement.
In transaction-based models, applications must embed all of this logic. They must know which routes to use, where liquidity exists, how to handle failures partway through and how to manage timing across asynchronous networks.
Intent-based execution (often searched as intent based trading or crypto intents) moves this work from the application to the infrastructure. The application states what the user wants. The infrastructure handles how.
This matters most when activity spans many networks, where:
- Execution paths change with conditions
- Liquidity is fragmented across venues
- Choosing a route needs information the application may not have
- Failure handling must be coordinated across networks
What this changes for system design
Intent-based execution requires systems to:
- Separate stating the request from planning its execution
- Evaluate and select execution paths as conditions change
- Verify fulfilment, settling an intent only when its limits are met
- Support intent expiry and a clear path back when an intent cannot be filled within its limits
- Design settlement to work asynchronously across networks
The pattern trades user-side complexity for system-side work. It does not remove the timing differences between networks; it makes actions across them easier to request and clearer to follow.
Related terms
- Intents: the structured request
- Solver: who performs the fill on SODAX
- Execution: the full process from request to settlement
- Cross-network execution: actions that span networks
- Chain abstraction: a related design approach
- Cross-chain swap: a common intent