Sushi swap is a multichain exchange powered by Route Processor 9

Sushi swap is a wallet-based token exchange that searches many liquidity pools - shared reserves used for trading - before it submits an onchain transaction. Route Processor 9 can combine Sushi pools with supported external venues while the wallet retains control until the owner signs. The quoted output reflects the selected route, pool charges and network execution.

That design makes Sushi both an automated market maker and an aggregator. The useful question isn’t simply whether a pair exists; it’s whether the route, chain and total execution cost fit the intended trade.

A 0.30% V2 pool fee is only one line in the trade’s final execution cost.

Sushi and Uniswap make different routing bets

Sushi and Uniswap both automate token swaps, but their interfaces search different universes of liquidity. Uniswap’s Auto Router evaluates Uniswap v2, v3 and v4 pools, then considers UniswapX when that option is eligible. Sushi’s Route Processor emphasizes aggregation across its own pools and supported external venues on many networks.

Route Processor 9 launched with aggregator coverage across more than 40 chains and liquidity sources, including PancakeSwap Infinity pools and hooks. That breadth matters where reserves are fragmented among Sushi V2, Sushi V3, Curve, Camelot, QuickSwap and Trader Joe. Neither route family wins every comparison. The decisive figure is the output remaining after pool fees, price impact and gas.

Fees, gas and the quoted output

A Sushi swap quote combines pool fees, network gas and price impact into one practical decision. These charges arise from different mechanisms and shouldn’t be treated as one percentage.

Pool fees

In the simplest case, Sushi V2 charges a fixed 0.30% pool fee on each swap. Standard Sushi V3 pools use four fee tiers: 0.01%, 0.05%, 0.30% and 1%, while Katana adds 2% and 4%. A route that crosses several pools applies the relevant fee at each leg. The quote engine incorporates those deductions when it calculates expected output.

Gas and price impact

Network gas pays the chain that executes the transaction, rather than the liquidity pool. Ethereum, Arbitrum One, Base and Optimism charge gas in ETH; BNB Smart Chain uses BNB and Avalanche uses AVAX. Price impact comes from changing pool reserves. It rises when the order is large relative to active liquidity, even if the stated fee tier remains low.

A worked cost example

In this hypothetical worked example, every changing input is hypothetical: the trade size is 1,000 USDC, price impact is 0.20% and gas is worth 1 USDC. A Sushi V2 fee removes 3 USDC, price impact represents another 2 USDC and gas adds 1 USDC. The combined economic cost is 6 USDC, leaving value equivalent to 994 USDC. A live quote embeds the fee and impact in its output, so they shouldn’t be subtracted twice.

What do you need before the first Sushi swap?

A first Sushi swap needs a compatible wallet, the correct network and enough native currency for gas.

MetaMask, Rabby and Coinbase Wallet connect through supported browser flows, while WalletConnect links compatible mobile wallets. On EVM networks, a token contract address occupies 20 bytes and appears as 40 hexadecimal characters after the 0x prefix. The network must match as well: Ethereum uses chain ID 1, Base uses 8453 and Arbitrum One uses 42161. Those identifiers prevent a wallet from signing the transaction for a different chain.

An ERC-20 token normally requires an approval before its first swap through a particular spending contract. That approval and the swap may therefore require two signatures and two onchain transactions. Native currency follows a different path because the router handles its wrapped representation during execution.

Same-chain trades and cross-chain transfers

Underneath that, Sushi supports same-chain swaps through Route Processor 9 and cross-chain transfers through SushiXSwap.

Trading within one network

A same-chain route keeps every pool and token movement on one blockchain. Common uses include moving between an EVM network’s native currency and an ERC-20 token, exchanging stablecoins or rebalancing a wallet without depositing into a centralized account. Route Processor 9 searches eligible direct, multihop and split paths before preparing one executable transaction.

Moving value between networks

In day-to-day use, SushiXSwap adds bridge and messaging infrastructure to the route. Its documented configuration covers 25 networks and applies a standardized 0.25% interface fee. LiFi aggregates providers that include Across, Stargate, Squid and Circle CCTP, then ranks routes by expected return or speed. Cross-chain execution adds source-chain gas, bridge settlement and destination delivery, so its timing and cost structure differ from a same-chain swap.

Liquidity positions change the job

Liquidity provision turns a one-time trade into an open position that earns fees while bearing market risk.

Sushi V2 positions

A Sushi V2 provider deposits two assets in the ratio required by the pool. When market prices and pool prices align, that commonly represents a 50/50 split by value. The provider receives an ERC-20 Sushi Liquidity Provider token, or SLP, representing a proportional claim on both reserves. Withdrawal burns that pool share and returns the corresponding assets plus accrued pool fees.

Sushi V3 positions

From a cost perspective, Sushi V3 concentrates liquidity between two chosen price boundaries. Its position uses an ERC-721 token because each combination of pair, fee tier and range is distinct. Capital earns swap fees only while the market trades inside the selected range. Once the price leaves it, the position becomes increasingly one-sided and stops collecting fees until the range is active again or the provider changes the position.

Liquidity rewards, trading volume and active-liquidity share move over time. V2 favors a passive full-range structure, while V3 exchanges that simplicity for control over capital placement. The range decision turns V3 into a continuing management commitment.

SUSHI, xSUSHI and pool ownership

In the simplest case, SUSHI, xSUSHI and liquidity-position tokens record different rights inside the wider Sushi ecosystem.

Underneath that, Sushi began in late August 2020 as an automated market maker and later expanded into aggregation and multichain execution. SUSHI is the ecosystem’s ERC-20 governance token, but it isn’t required for ordinary swaps. Depositing SUSHI into the Sushi Bar produces xSUSHI as a staking receipt. SLP tokens represent V2 pool shares, while Sushi V3 uses non-fungible ERC-721 positions. Holding one of these assets doesn’t automatically confer the rights attached to another.

Where the main trade-offs sit

In day-to-day use, Sushi’s principal trade-offs are route complexity, contract exposure, approvals and pool-driven price movement.

An aggregated route may touch several pools and an execution contract within one atomic transaction. Each additional hop changes gas usage and introduces another pool’s fee and liquidity conditions. ERC-20 allowances are separate on each chain and for each approved spending contract. An allowance may remain active after a swap until the wallet owner reduces it, sets it to zero or replaces it with a new limit.

Price impact remains the central trading risk when liquidity is thin. Slippage tolerance sets the lowest acceptable output; it doesn’t improve the pool price. Two assets may share a ticker while using different contract addresses or chains, and cross-chain routes add bridge finality to the settlement path. Reading those fields before signing protects the intended received amount.

How does Route Processor 9 build a trade?

Route Processor 9 searches supported liquidity, scores viable paths and encodes the chosen route for onchain execution.

The router models tokens as route points and pools as possible connections between them. It evaluates direct swaps, paths through intermediate assets and splits across more than one source. Each candidate produces an estimated output after its pool mathematics and fees. Gas estimates then penalize needless complexity, because a slightly better pool price may lose its advantage when execution requires extra calls. The selected path is converted into calldata that the wallet reviews and signs.

From a cost perspective, Sushi V2 pools use the constant-product rule x × y = k, preserving the reserves’ product across fee-adjusted trades. V3 pools use concentrated liquidity instead, while Curve-style pools and PancakeSwap Infinity hooks contribute different pricing behavior. RP9 lets one quote engine compare these mechanisms before the chosen contracts settle the trade.

Reading the quote before signing

The Sushi quote reveals expected output, minimum received, route, price impact and network cost before wallet confirmation, which is detailed in Sushi swap walkthrough.

Expected output is the route’s estimate at quotation time. Minimum received applies the chosen slippage tolerance and becomes an onchain execution condition. Price impact describes the route’s movement through available liquidity, while gas estimates what the network charges for computation. The route display identifies intermediate tokens and liquidity venues. Token contract, chain and recipient complete the transaction context.

A longer route remains rational when its extra output exceeds added fees and gas. Comparing the final received amount gives the wallet owner a clearer decision than focusing on one fee line.

Uniswap, 1inch, CoW Swap and PancakeSwap as alternatives

Uniswap, 1inch, CoW Swap and PancakeSwap each emphasize a different execution model or liquidity network.

Uniswap routes across its v2, v3 and v4 pools and uses UniswapX for eligible orders. The 1inch Aggregation Protocol searches multiple exchanges and its Pathfinder system can split a trade across sources. CoW Swap submits trading intents to competing solvers and clears compatible orders through batch auctions. PancakeSwap supplies deep native liquidity across its own pool generations, including Infinity pools that RP9 can access on supported networks.

Chain coverage, token support and route economics decide which interface fits a transaction. Comparing executable quotes on the same network exposes those differences through the actual output, gas estimate and route.