Sushi

Sushi (originally launched as SushiSwap in 2020) is a decentralized exchange and automated market maker protocol that operates across multiple EVM-compatible and other supported blockchain networks, providing a unified interface for token swaps, liquidity provisioning, and DeFi trading. The protocol is accessible at sushi.com/swap and uses the constant product market maker model for its core AMM pools, allowing liquidity providers to deposit token pairs into pools and enabling traders to swap tokens against pooled liquidity at prices determined by the pool's invariant. The SUSHI token serves as the protocol's governance token, participating in the Sushi ecosystem governance process across supported networks

The Sushi protocol's core swap and liquidity pool contracts are published under the GPL-3.0 open-source license on GitHub at github.com/sushiswap/sushiswap-interface, making the implementation available for independent review and integration development. Protocol documentation for users and developers is maintained at docs.sushi.com, covering the swap interface, liquidity pool mechanics, and integration references for building on the Sushi protocol. Sushi Academy at sushi.com/academy provides educational content on DeFi concepts and the Sushi exchange, and the Help and FAQ section at sushi.com/faq addresses common platform questions for users accessing the exchange interface

The primary user interaction with Sushi begins at sushi.com/swap, where traders connect an EVM-compatible wallet, select input and output tokens, and execute a swap routed through available pool liquidity on the selected network. Sushi routes the trade through one or more pool hops when doing so improves the execution price relative to routing through a single pool, splitting liquidity sourcing across available pools for the selected token pair. The interface displays the estimated output amount, price impact, and minimum received for the swap before the user confirms the on-chain transaction, allowing review of execution parameters before authorizing

Liquidity providers interact with Sushi by selecting a trading pair, depositing balanced value amounts of both tokens into the corresponding Sushi pool, and receiving LP tokens representing their proportional share of the pool's total liquidity and accrued swap fees. When liquidity is removed, LP holders redeem their tokens for their proportional share of the pool's current token balances, which reflect the AMM's rebalancing from swap activity since the liquidity was deposited. Swap fees accrued during the LP's holding period are reflected in the redemption value of the LP tokens at exit

Sushi's core AMM pools implement the constant product market maker invariant (x * y = k), where x and y represent the pool's balances of the two pooled tokens and k is a constant maintained by the pricing mechanism. When a trader swaps token A for token B, the pool's balance of A increases and the pool's balance of B decreases in a ratio that preserves k, with the resulting trade price reflecting the marginal rate implied by the pool's post-swap token ratio. Swap fees charged on each trade are added to the pool's token balances, incrementally increasing k and distributing fee revenue to liquidity providers in proportion to their LP token holdings

Multi-chain routing on Sushi allows the exchange interface to find execution paths across the pool liquidity available on a selected blockchain network, using multi-hop routing when a direct token pair pool is unavailable or when a multi-hop route offers better price execution than a direct path. The swap routing logic aggregates available liquidity sources on the target network to determine the optimal route for the requested swap size, with routing mechanics and supported network configurations documented at docs.sushi.com alongside contract deployment addresses for the pool factory and router contracts on each supported chain

The SUSHI token is used within the Sushi ecosystem as the protocol's governance token across supported networks, with token holders participating in governance decisions over protocol parameters and development priorities. SUSHI is an ERC-20 token on Ethereum with representations on other supported networks, and details on token utility, governance participation, and applicable mechanics are described in the official protocol documentation at docs.sushi.com. SUSHI token holders should consult the current documentation for up-to-date information on governance features available through the Sushi platform

Sushi Academy at sushi.com/academy is the protocol's educational resource for users learning about DeFi trading, liquidity provisioning, and the Sushi exchange ecosystem. The Academy provides content covering foundational DeFi concepts — including how constant product AMM pools price swaps, how fee accrual works for liquidity providers, and how to evaluate trade execution quality — making the protocol more accessible to users who are new to decentralized exchange mechanics. The Discord community at discord.gg/9dZAebw6yT and the Help and FAQ section at sushi.com/faq provide additional resources for users with questions about swap execution, wallet connectivity, and platform usage

Sushi supports a range of trading and liquidity use cases across its supported blockchain networks: traders swap ERC-20 and other supported tokens through the sushi.com/swap interface, with multi-hop routing finding execution paths through available pool liquidity on the selected chain; liquidity providers deposit token pairs into Sushi AMM pools to earn swap fees from trading activity routed through their liquidity position; developers build integrations using the GPL-3.0 open-source contracts and documentation at docs.sushi.com to interact with Sushi pool and router contracts programmatically; SUSHI token holders participate in protocol governance across the Sushi ecosystem; and DeFi users access educational content on swap mechanics, liquidity provisioning, and AMM design through Sushi Academy at sushi.com/academy and the Discord community at discord.gg/9dZAebw6yT

Developer integration with Sushi is supported through the documentation at docs.sushi.com and the open-source contract repositories on GitHub at github.com/sushiswap/sushiswap-interface, published under the GPL-3.0 license. The Sushi protocol exposes pool and router contract interfaces for on-chain integrations — including swap execution, liquidity deposit and withdrawal, and pool state queries — allowing developers to build applications that interact with Sushi pools directly through the deployed contract ABIs and documented interfaces. Deployment addresses for pool factory and router contracts across supported networks are referenced in the documentation at docs.sushi.com, providing the starting point for developers building trading integrations, liquidity management tools, or analytics applications on top of the Sushi protocol

Sushi's core protocol contracts are published under the GPL-3.0 open-source license on GitHub at github.com/sushiswap/sushiswap-interface, enabling independent review of the pool and router contract implementations for each supported network. As a non-custodial AMM protocol, Sushi does not hold user funds in a centralized account — token swaps and liquidity operations are executed through on-chain smart contracts, with all state changes verifiable on the respective blockchain by any external observer. Users evaluating Sushi should review the open-source contract code on GitHub, apply standard Web3 wallet security practices before connecting to sushi.com/swap and authorizing on-chain transactions, and consult the FAQ at sushi.com/faq or the Discord community at discord.gg/9dZAebw6yT for platform questions

Sushi provides a multi-chain decentralized exchange and AMM protocol accessible at sushi.com/swap, with constant product pool liquidity, multi-hop swap routing across supported blockchain networks, and GPL-3.0 open-source contracts published on GitHub at github.com/sushiswap/sushiswap-interface. Documentation at docs.sushi.com, Sushi Academy educational resources at sushi.com/academy, the SUSHI governance token, and the Discord community at discord.gg/9dZAebw6yT give developers, traders, and liquidity providers structured access to the protocol's swap infrastructure and educational resources. Teams and users evaluating Sushi should review the documentation at docs.sushi.com, the contract source code on GitHub, and the FAQ at sushi.com/faq to understand the AMM pool mechanics, multi-chain routing, and wallet interaction requirements before trading or providing liquidity through the Sushi protocol