Liquidity
Liquidity is the SODAX system component that enables cross-network actions to complete by treating assets as a unified, globally accessible inventory rather than isolated pools.
What it is
Liquidity in SODAX is a system-level inventory that enables cross-network actions to be executed reliably. Rather than existing as isolated pools on individual networks, liquidity is treated as a unified, accounted resource that can be accessed and coordinated across networks to fulfill user intents.
What it does inside SODAX
Inside the SODAX system, liquidity serves as the source of value used to complete cross-network actions. It is accessed by the solver when planning execution and consumed during execution to deliver the user’s intended outcome. After execution, liquidity is redistributed to maintain system balance. By separating the accounting of assets from their physical location, SODAX can coordinate execution without requiring large idle balances on every connected network.
Why it exists
In cross-network systems, execution often fails not because assets cannot be moved, but because usable liquidity is fragmented or temporarily unavailable where it is needed. Liquidity in SODAX exists to close this execution gap. Treating liquidity as a unified inventory allows the system to reason about availability, risk, and balance globally rather than per network, reducing failed executions caused by timing, volatility, or local shortages.
What this means for users and partners
For users, this means cross-network actions are more likely to complete successfully and with predictable outcomes. Liquidity can be sourced and coordinated across networks instead of being constrained to a single location. For builders and partners, this removes the need to manage liquidity fragmentation themselves. They can rely on SODAX to coordinate liquidity behind the scenes while focusing on user-facing functionality.
By coordinating depth across networks, the system can achieve low slippage on cross-network swaps (often searched as low slippage cross chain swap), since execution is not constrained to the depth of a single local pool.