OmniSwap
OmniSwap is Nami's multichain meta-aggregator.
It compares aggregators, solvers, and bridges to find the best available execution for any operation.
It is powered by Nami's proprietary Batcher Engine, which bundles multiple calls into a single transaction across providers and chains.
Samechain swaps, cross-chain transfers, multi-token operations, destination-chain gas top-ups, and direct interactions with Nami products can all be combined within a single flow.
The user chooses what to convert and what to receive.
OmniSwap manages the entire execution.
Transparent Routing
For each operation, OmniSwap queries leading aggregators, solvers, and cross-chain providers in parallel — including 0x, 1inch, OKX, KyberSwap, CoW Swap, Fly, De¹, Velora, Relay, Squid, Jumper (LI.FI), Bungee (Socket), bebop, and Rubic Exchange.
Each quote is simulated and verified in real time, then ranked by net output.
The comparison also accounts for gas costs, so the selected route reflects the estimated amount that reaches the user.
The best verified route is selected automatically. Alternative routes remain available for manual selection.
Fee Structure
Quotes returned by OmniSwap include no protocol fees or additional markups charged by Nami.
The costs borne by the user include network gas and any native fees charged by the providers included in the selected route.
Some providers share a portion of their own revenue with Nami at no additional cost to the user. All revenue received through these agreements is directed to the Recursive Buyback Engine.
The Batcher Engine
The Batcher Engine is Nami's proprietary execution architecture, designed to transform a complex operation into a programmable sequence of coordinated calls.
The first time a user interacts with OmniSwap, their personal execution account is automatically deployed as part of the same transaction. No separate setup or confirmation is required.
The batcher account has the same predictable address across all supported chains.
The account can interact exclusively with aggregators, solvers, bridges, and protocol contracts included in a whitelist administered by the Nami team.
Each call can use a different provider, and the output of one operation can become the input of the next. Calls executed on the same chain can be bundled into a single transaction.
Approval Isolation
Each user operates through a personal Batcher Account created by the Batcher Factory.
The account is tied exclusively to the user's wallet and isolated from every other user.
In a standard flow, users grant token approvals directly to third-party routers, bridges, and aggregators. These approvals may remain active, leaving the wallet exposed if a provider is later compromised.
One Approval Across All Providers
With OmniSwap, each token only needs to be approved once to the Batcher Factory.
OmniSwap can then route that token through any integrated router, bridge, or aggregator without requiring another wallet approval when the selected provider changes.
The Factory can use that approval solely to transfer tokens from the wallet into the corresponding personal Batcher Account. It cannot redirect them to another account or destination, and only the user's wallet can authorize operations from the account.
Third-party providers never receive an allowance over the assets held in the user's wallet.
For each call, the Batcher Engine grants the selected executor an allowance limited to the amount required for that operation.
The resulting tokens are returned directly to the wallet, leaving the personal Batcher Account empty between flows.
This creates an isolated execution layer between the wallet and external contracts.
A stale approval or compromised provider cannot directly access funds held in the wallet, and its exposure is limited to the assets present in the personal Batcher Account during execution.
Standard Swap
Possible access to wallet funds through old approvals not revoked
Exposure limited to the active execution amount.
MultiSwap
MultiSwap applies the Batcher Engine to multi-asset operations.
Users can consolidate multiple tokens into a single asset and distribute one token across several assets.
Each leg is quoted, simulated, and routed independently, allowing the same MultiSwap to use the most efficient provider for each operation.
Before execution, the simulation displays the expected balance of each token before and after the MultiSwap, together with the minimum output defined for each leg.
Users choose between two execution policies.
Complete what you can: executes the legs that meet minimum output and skips any leg where price has moved beyond the defined limit.
All or Nothing: executes only when all legs satisfy the defined conditions.
For cross-chain legs, the policy determines whether the operation is valid and can be initiated.
Completion on the destination chain is governed by the conditions of the selected provider.
Cross-Chain Execution and Destination Gas
For cross-chain operations, OmniSwap coordinates the swap on the source chain, the bridge, and any required conversion on the destination chain within the same flow.
When the user does not have gas on the destination chain, OmniSwap can include the required native token as part of the execution.
The received assets can be used immediately, without a separate operation to obtain gas.
Privacy Swap
Privacy Swap is an optional same-chain and cross-chain routing mode powered by Houdini Swap.
When enabled, OmniSwap requests a Houdini Private Swap route and displays the expected output and total execution cost before confirmation.
The transaction is routed through separate exchange partners, temporarily using an intermediary asset.
Once the deposit is detected, the route proceeds automatically until the requested asset is delivered to the selected destination address.
Privacy Swap execution is provided through third-party infrastructure and services.
Availability, completion times, costs, supported assets, and execution conditions depend on the providers involved in the route.
By using Privacy Swap, users are also subject to the applicable Houdini Swap Terms of Service.
One Engine, Multiple Products
The same execution engine powers OmniDeposit and OmniShift.
OmniDeposit converts, transfers, and balances the assets required to create a liquidity position.
Users can start with a single supported token on any connected chain and directly receive the LP position required by the selected pool and strategy.
OmniShift uses the same infrastructure to remove, transfer, rebalance, and rebuild deposited liquidity across different chains or opportunities.
Supported Chains
OmniSwap currently supports 15 chains: