Intents

An intent is the structured request an app submits to SODAX for a cross-network action: what the user wants, such as trading one asset for another across networks, and the limits it must meet, such as a minimum amount received and an expiry.

cross-networkexecutionintentsconstraintssolversystem

What it is

An intent is the formal request submitted to SODAX when a user wants to carry out a cross-network action.

It states what the user wants, such as trading one asset for another across networks, and includes the limits within which the action is acceptable. These limits typically include a minimum amount received, an expiry, and source and destination information.

An intent does not contain routing logic or liquidity strategy. It specifies what is wanted and the limits. The system determines how to carry it out.

What it does inside SODAX

Within the SODAX system, the intent is the starting point for execution coordination.

When an app calls the SODAX API and submits an intent, a permissioned solver within the SODAX system evaluates whether it can be filled under current liquidity and network conditions. If it can, the permissioned solver plans the steps and starts coordination across networks.

The intent sets the boundaries of execution. The permissioned solver determines the plan. The Coordinator structures and monitors the steps. The Hub records settlement.

The intent stays fixed throughout this process. It does not change as routing decisions evolve.

Why it exists

Cross-network actions are asynchronous and depend on fragmented liquidity. When execution is modeled as a loose sequence of transactions rather than one defined request, failures often occur mid-process.

The intent separates what the user asked for from the execution strategy.

By defining the request apart from the execution path, SODAX can:

  • Adapt routing under changing conditions
  • Source liquidity across networks
  • Enforce price and timing limits
  • Surface failures instead of leaving them silent or partial

An intent does not promise a fill. It makes sure a fill only happens within the defined limits. This design pattern is what defines a cross-network intent protocol (often searched as cross chain intent protocol): users state what they want, and the system takes responsibility for planning, routing and settling the path.

What this means for users and partners

For users, intents let a cross-network action be expressed once, with clear limits. A trade fills only if those limits are met: it completes as requested or reverts and returns the original assets, rather than filling under worse terms.

For builders, intents provide a consistent request format. Apps calling the SODAX API state what the user wants and the limits, while SODAX routes, quotes and settles.

Component boundaries remain clear:

  • The intent defines what should happen.
  • The permissioned solver decides how it is filled.
  • The Coordinator structures the execution steps.
  • The Hub records settlement.

The intent is the request layer of the system. It is not the execution engine.

Related terms

Last updated: 11/11/2026