Solver
The Solver is the part of SODAX responsible for deciding, initiating, and coordinating how a cross-network action is carried out, selecting the most reliable execution path across networks.
What it is
The Solver is SODAX’s execution planning and coordination engine for cross-network actions. When an application submits an intent, such as swapping assets or adjusting a position across networks, the Solver determines how that action can be completed under current conditions. Its responsibility is to turn intent into a concrete execution plan that downstream systems can carry out.
What it does inside SODAX
Within the SODAX system, the Solver evaluates possible execution paths across networks and liquidity sources. It considers factors such as liquidity availability, fees, gas costs, and execution constraints. Based on this, it selects an execution plan and initiates the process that delivers the user’s destination asset as quickly and reliably as possible. At the same time, the Solver accounts for how liquidity should be redistributed across networks so the system remains balanced after execution.
Why it exists
Cross-network actions are difficult to coordinate because liquidity is fragmented and execution steps often span multiple networks with different costs and timing characteristics. Without a Solver, applications would need to embed complex routing and execution logic themselves.
The Solver exists to centralize these decisions so cross-network actions can be planned coherently instead of treated as a series of disconnected steps.
In broader DeFi terminology, this role is part of an emerging solver network (sometimes called decentralized solvers in crypto contexts): specialized systems that compete or collaborate to find optimal execution paths on behalf of users.
What this means for users and partners
With the Solver in place, users benefit from faster and more predictable cross-network actions, while builders interact with a simpler and more consistent execution surface. The system focuses on completing the intended outcome first, while managing liquidity movements in the background. This does not imply guaranteed execution, but it does reduce unnecessary complexity and failure modes for applications built on SODAX.
