Intents
An Intent is the structured user request that defines the desired cross-network outcome and the constraints under which it may be executed.
What it is
An Intent is the formal request submitted to SODAX when a user wants to perform a cross-network action.
It defines what outcome the user is aiming for, such as swapping one asset for another across networks, and includes the limits under which that outcome is acceptable. These limits typically include pricing thresholds, expiration timing, and source and destination information.
An Intent does not contain routing logic or liquidity strategy. It specifies the outcome and the constraints. The system determines how to fulfill it.
What it does inside SODAX
Within the SODAX system, the Intent acts as the starting point for execution coordination.
When an application submits an Intent, the Solver evaluates whether it can be fulfilled under current liquidity and network conditions. If viable, the Solver selects an execution strategy and initiates coordination across networks.
The Intent defines the boundaries of execution. The Solver determines the plan. The Coordinator structures and monitors the execution process. Liquidity is consumed to complete the action.
The Intent remains fixed throughout this process. It does not change as routing decisions evolve.
Why it exists
Cross-network actions are inherently asynchronous and dependent on fragmented liquidity. When execution is modeled as a sequence of transactions rather than a defined outcome, failures often occur mid-process.
The Intent layer exists to separate outcome definition from execution strategy.
By defining the desired result independently from the execution path, SODAX can:
- Adapt routing under changing conditions
- Source liquidity across networks
- Enforce pricing and timing constraints
- Avoid silent or partial failures
The Intent does not guarantee fulfillment. It ensures that fulfillment only occurs within the defined constraints. This design pattern is what defines a cross-network intent protocol (often searched as cross chain intent protocol): users declare outcomes, and the system takes responsibility for planning, routing, and executing the path to fulfillment.
What this means for users and partners
For users, Intents allow cross-network actions to be expressed once, with clear limits. Execution occurs only if those limits are satisfied. If not, the action expires rather than executing under unfavorable conditions.
For builders, Intents provide a consistent integration surface. Applications define outcomes and constraints, while SODAX handles routing, coordination, and liquidity sourcing behind the scenes.
Component boundaries remain clear:
- The Intent defines what should happen.
- The Solver decides how it should happen.
- The Coordinator structures the execution process.
- Liquidity settles the action.
The Intent is the request layer of the system. It is not the execution engine.
