Sushiswap exchange

Sushiswap exchange is a Multichain DEX Aggregator for Routed Token Swaps

Sushiswap exchange is a wallet-connected market that combines decentralized trading pools and calculates a route before an on-chain token swap. A user selects a network, input token, amount, and output token; the interface then presents an executable quote for wallet authorization. Sushi remains non-custodial during this process: smart contracts execute against available liquidity, and the output settles to the specified wallet address.

In short: A V2 pool charges 0.3%, while V3 pools define four fee tiers from 0.01% to 1%.

Network mismatch and contract identity stop otherwise valid quotes

One wrong network or contract address makes a valid Sushi quote irrelevant, because token identity includes both the asset contract and the blockchain carrying it. Ethereum mainnet uses chain ID 1, Arbitrum One 42161, Base 8453, Polygon PoS 137, and BNB Smart Chain 56.

An EVM token contract uses a 20-byte address, written as 40 hexadecimal digits after the 0x prefix. Decimals then scale the integer recorded on-chain: Circle-issued USDC uses 6 decimals, DAI uses 18, and WBTC uses 8 on Ethereum. One USDC therefore represents 1,000,000 base units, while one DAI represents 1,000,000,000,000,000,000. The same symbol can represent a native issuance, a bridged representation, or a distinct token contract, and the router treats each contract as separate liquidity. Read the chain, contract, symbol, and decimals together before accepting a token selected by address.

A Base quote spends Base assets; it does not reach an Ethereum balance carrying the same symbol. Network selection therefore precedes every price decision.

Pool fees, interface fees, and gas form separate costs

Three cost layers determine a Sushi swap’s final value: the pool fee inside each liquidity hop, any interface charge displayed in the quote, and the network gas paid by the wallet.

Sushi V2 charges 0.3% per trade, allocating 0.25% to liquidity providers and 0.05% to SUSHI holders, while V3 defines four pool tiers: 0.01%, 0.05%, 0.3%, and 1%. A two-hop route crosses two pools, and each pool applies its own fee to the amount entering that hop. The interface quote incorporates those route deductions, while the wallet pays gas separately in ETH, POL, BNB, or another chain’s transaction currency. A separate page looks at this About Exchange.

An interface fee appears as its own quote line when applied; it remains distinct from the V2 or V3 pool fee encoded in each hop. A route without an interface charge still pays pool fees and gas, so compare all three cost layers before authorizing.

Gas rises with network demand and route complexity, whereas a pool tier remains fixed for that pool. Compare expected output after all displayed charges and the gas estimate.

Minimum received is the decisive quote field

Two quote fields govern execution: estimated output describes the present route, while minimum received encodes the lowest amount the transaction accepts under the selected tolerance.

A worked example uses three hypothetical changing inputs: an estimated output of 0.5000 ETH, a 0.50% slippage tolerance, and a network fee of 0.0020 ETH. Multiplying 0.5000 ETH by 99.50% sets minimum received at 0.4975 ETH. Because gas leaves the same ETH balance separately, subtracting 0.0020 ETH produces a concrete minimum-output wallet change of 0.4955 ETH for these inputs. Pool and interface charges already reflected in the quote should not be deducted again.

Price impact measures how the trade itself moves through available reserves. A larger order relative to pool depth lowers output, and a refreshed route can select different pools. The encoded minimum controls settlement.

Four actions take a same-chain swap from wallet to settlement

Four actions define the Sushiswap exchange entry path: connect a wallet, select the active network, specify the token pair and amount, then review and sign the quoted transaction.

MetaMask and Coinbase Wallet connect directly, while WalletConnect links many mobile and hardware-wallet interfaces. WalletConnect carries the session, but the connected wallet still creates the signature and broadcasts the transaction through its selected network provider. The wallet should display the chain and requested action before any signature. Selling a native asset such as ETH requires no ERC-20 allowance. Selling an ERC-20 token without sufficient allowance adds an approval step, so a first interaction may produce two on-chain transactions: one approval and one swap. Later trades can reuse a remaining allowance for the same token and spender.

Keep enough native currency outside the input amount to cover approval and swap gas. The final signature submits the encoded route, recipient, and minimum output.

Token conversion, stable routes, and staking wrappers cover the main uses

Three recurring uses define Sushi’s swap product for wallet users: same-chain token conversion, stable-asset routing, and supported wrapper or staking conversions assembled inside an executable route.

A USDC-to-DAI trade searches suitable liquidity rather than requiring a direct Sushi pool. An ETH-to-WETH conversion uses the wrapper’s fixed 1:1 deposit relationship, though gas and any displayed interface charge still affect wallet value. Routes involving SUSHI, xSUSHI, stETH, or wstETH require closer attention because the quoted unit relationship reflects each wrapper or staking mechanism. The route view shows whether execution passes through Sushi pools, Curve, Uniswap, or another integrated venue.

Aggregation expands execution beyond pools branded Sushi, which helps when the deepest pair sits elsewhere. It also means the route contract can touch several venue contracts within one atomic same-chain transaction; if any required condition fails, the whole swap reverts.

Cross-chain conversion belongs to SushiXSwap. It adds a destination network and bridge layer through providers such as Across, Stargate V2, or Circle CCTP, so time, fees, and settlement checks differ from a same-chain route.

V2 and V3 pools create different liquidity positions

Two pool generations sit behind many Sushi routes: V2 holds two reserves across the full price curve, while V3 concentrates liquidity inside a provider-selected price range.

V2 follows the constant-product relationship x × y = k and charges its fixed 0.3% trading fee. Providers deposit equal values of two assets and receive fungible liquidity tokens representing their share. V3 records a concentrated position through a non-fungible ERC-721 position token and offers four fee tiers. Concentration commits capital near a chosen market range, increasing its use there without supplying the entire curve.

Swappers do not open either liquidity position. The route engine compares available V2 and V3 paths, and the quote exposes the chosen sequence before wallet authorization.

A V3 position outside its selected range earns 0 swap fees until the market price re-enters. Both models expose providers to inventory changes as traders rebalance the pool, making liquidity provision a separate decision from swapping.

Approvals separate spending permission from swap execution

Two distinct wallet transactions may precede settlement for an ERC-20 input: an approval writes the spender’s allowance, and the swap later uses that permission to move the specified tokens.

An exact approval limits allowance to the entered amount. A maximum approval can reach 2^256 − 1 base units because the ERC-20 allowance field uses an unsigned 256-bit integer. That permission remains recorded until another transaction changes it or the relevant token and spender differ. Before signing, inspect the token contract, spender, allowance amount, input amount, recipient, and active chain as separate fields.

Disconnecting a wallet ends the interface session but leaves recorded allowances unchanged. Changing an allowance requires another on-chain transaction and its network gas.

RouteProcessor 6 introduced a two-contract routing layer

Two contracts defined RouteProcessor 6 when Sushi released it on 25 February 2025: RouteProcessor6 executed route instructions, and RedSnwapper served as the façade for user and integrator calls.

RP6 expanded route construction with Curve metapools and supported integrated staking or unstaking paths for SUSHI/xSUSHI and ETH/stETH/wstETH on Ethereum. Its separated façade let integrators keep a stable entry layer while Sushi changed the executor behind it. Sushi subsequently released RouteProcessor 7 on 8 May 2025 with Maverick V2, Fluid, and fee-on-transfer routing work, then RouteProcessor 9 on 23 September 2025 with PancakeSwap Infinity support.

RouteProcessor 6 therefore marks an important architecture stage, not a permanent version label. Integrators need the deployed contract expected by their quote response; interface users judge the transaction currently presented to the wallet.

Does aggregation guarantee the best final output?

Two routing engines can inspect overlapping liquidity and still return different final outputs because their source sets, split algorithms, gas estimates, and quote times differ.

Sushi aggregation has integrated liquidity from Sushi, Uniswap, Curve, Algebra, QuickSwap, PancakeSwap, Camelot, Trader Joe, Maverick V2, and Fluid. The router evaluates direct paths, intermediate-token hops, and split liquidity, then produces one transaction plan. Extra hops sometimes improve the token output yet consume more gas, so the strongest route depends on the final amount after its full execution cost.

Split routing draws from several reserve sets to reduce price impact on a large order. Each extra pool also adds calldata and computation, which can erase a nominal token-output gain on an expensive network.

A quote ranks routes available at a moment rather than proving a universal optimum. Compare executable minimum output on the same chain and refresh immediately before signing.

Uniswap, Curve, PancakeSwap, and 1inch divide the alternatives

Four established alternatives frame the choice around Sushi: Uniswap emphasizes its own pool ecosystem and UniswapX, Curve specializes in correlated assets, PancakeSwap spans its AMM stack, and 1inch focuses on aggregation (more in Sushiswap exchange walkthrough ).

Uniswap provides direct access to V2, V3, and V4 pool designs, while UniswapX adds a filler-based auction model. Curve concentrates liquidity around stablecoins and similarly priced assets through specialized pools and metapools. PancakeSwap combines broad BNB Smart Chain roots with multichain deployments and Infinity’s hook-enabled pool architecture. The 1inch router searches external liquidity sources and splits trades across venues, placing it closest to Sushi’s aggregator role.

Custody stays wallet-based across these decentralized routes, but venue coverage and contract architecture differ. Matching the same chain, input amount, recipient, and timing makes quote comparisons meaningful.

Sushi differentiates itself by combining its own V2 and V3 liquidity with external routes in one multichain interface. Compare the quoted recipient amount, gas, minimum received, route visibility, and desired chain rather than assuming one venue wins every pair.

The transaction record defines the final check

One 32-byte transaction hash identifies the submitted swap, appearing as 64 hexadecimal digits after its 0x prefix and linking the wallet request to the chain’s final record.

After inclusion, inspect status, sender, destination contract, gas used, and token Transfer events. An EVM receipt status of 1 indicates success, while 0 indicates reversion. An aggregated route can emit several intermediate transfers because assets pass through multiple pools, yet the final output transfer should name the intended recipient and token contract. Compare that amount with the transaction’s minimum-output condition and the wallet’s balance change. If the token does not appear in the wallet interface, importing its selected contract address reveals the already-recorded balance.

This record closes the swap with durable evidence of execution, route transfers, cost, and recipient settlement.

Helpful answers about Sushiswap exchange