SushiSwap has three practical paths: swap tokens on one network, swap across networks, or provide liquidity through V2, V3, or managed pools. If you hold tokens on a supported EVM network and want to trade them or supply a pool, SushiSwap lets you do that.
The options depend on what you want to do
The first choice is between receiving a different token and earning a share of trading fees. A swap ends with tokens in your wallet; providing liquidity leaves your tokens in a pool until you withdraw them. The pool choices then differ in how much control and upkeep they require.
- Same-network swap — Best for exchanging tokens already on the same blockchain. It does not move assets from, say, Ethereum to Polygon, even if both networks have tokens with the same ticker.
- Cross-network swap — Best when the token you want must arrive on another blockchain. SushiXSwap can route a trade through cross-chain providers; it does not fit a trade where a simple same-network swap gives the intended result with less cost and delay.
- V2 pool — Best for a straightforward, full-range position that stays available as the price moves. It does not fit someone seeking to concentrate their capital around a chosen price; every unit is spread across the pool’s full price curve.
- V3 pool — Best when you can choose a fee tier and price range, then monitor that range. It does not fit a position you intend to ignore: outside your range, your liquidity stops earning swap fees.
- Smart Pool — Best when you want a managed strategy to adjust concentrated liquidity. It does not fit someone who wants direct control of every adjustment, and its strategy adds its own costs and risks.
I would start with a same-network swap if the goal is simply to own another token. For liquidity, I would inspect an established V2 pool before choosing a V3 range: the quoted fee rate means little without trading volume, active liquidity, and a plan for price moves.
A swap changes pool reserves and the price you receive
An automated market maker quotes against tokens held in a pool, rather than matching your order with another trader’s order. In a basic V2 pool, the reserve product x × y = k determines how much the other reserve must fall when your input arrives. Fees and the changing reserve ratio make the execution price differ from the price shown before the trade.
For example, suppose a pool holds 100 ETH and 300,000 USDC, implying 3,000 USDC per ETH. Before a 3,000 USDC swap, that amount appears to buy 1 ETH at the starting price. After a 0.3% pool fee and the reserve shift, it buys about 0.987 ETH; the average price is roughly 3,039 USDC per ETH. A deeper pool would move less for the same trade.
That difference is price impact, plus the trading fee. Slippage tolerance is different: it sets how far the executed output may fall below the quoted minimum while your transaction waits. For a liquid pair, a tolerance around 0.1%–0.5% may be enough; a thin or volatile pair may need more, but increasing it also permits a worse fill. Check the quoted output, minimum received, and token contract before signing.
Pool design determines when fees outweigh the work
SushiSwap V2 liquidity usually starts with equal values of two tokens. You contribute, say, 1 ETH and 3,000 USDC when ETH is worth 3,000 USDC, and receive a claim on your share of the pool. Trades change the quantities behind that claim. The fees you earn depend on trading volume and your share of liquidity, so a high fee rate alone does not establish a high return.
The trade-off is visible if ETH doubles to 6,000 USDC. Ignoring fees, holding the original tokens would be worth 9,000 USDC; the pool position would hold about 0.707 ETH and 4,243 USDC, worth about 8,485 USDC. That roughly 5.7% shortfall against holding is impermanent loss. Fees can offset it, but they are not guaranteed to do so.
V3 concentrates a position between lower and upper prices. A narrow range can earn more fees per dollar while the market trades inside it, but a move beyond either boundary leaves the position in one token and earning no swap fees until price returns or you reposition it. A wider range stays active longer while spreading capital more thinly. Managed pools automate some of that repositioning, with strategy and contract risk added to the underlying token risk.
Getting it done starts with the network and the outcome
For a swap, first check which network actually holds your input token and which network must hold the output. Connect a wallet with enough of that network’s native token for gas, verify the token contract, and compare the final amount received with the fee and price impact. An ERC-20 approval may require a separate transaction before the swap; setting an approval cap limits what that permission covers.
sushiswap.co is where you can exchange tokens on a supported network or put a token pair into a liquidity pool. If you are providing liquidity, compare pools for the same pair on that network before depositing: their version, fee tier, available liquidity, and trading volume determine the position you are taking. Changing the network in your wallet alone does not transfer tokens between blockchains.
Common practical questions
How can I provide liquidity?
Hold the pair on the same supported network, plus its native token for gas. Choose an existing pool, check its version and fee tier, and deposit the required token amounts after any needed approvals. For V3, also choose a price range and plan when to adjust or withdraw it. A single-token deposit, where available, swaps part of your input first; check that conversion’s cost and price impact.
How much are SushiSwap trading fees?
Published pool rates are typically 0.3% for V2 and 0.01%, 0.05%, 0.3%, or 1% for V3, depending on the pool. A 1,000 USDC trade through a 0.3% pool incurs about 3 USDC in pool fees, before price impact and network gas. Cross-network routes can add provider and interface charges, so compare the final output rather than the pool percentage alone.
How long does a transaction take?
A same-network swap completes when its blockchain includes the transaction, often in seconds to a few minutes, depending on congestion and the gas price offered. The Ethereum Foundation describes Ethereum blocks as arriving in roughly 12-second slots, but inclusion and finality are different events. Approvals add another transaction. Cross-network swaps also wait for source-chain settlement and a destination-chain route, so they can take minutes or longer.
Can I use it on different blockchain networks?
Yes, but pools and balances belong to particular networks. Ethereum, Polygon, and Avalanche each have their own gas token, liquidity, and transaction history; a pool on one does not draw reserves from another. Check that the exact pair and pool type exist where your assets are. If the destination is another network, compare a cross-network route with moving assets first, then make a small trade to verify the result you expect.