Sushi: swap routes, product-specific fees, liquidity positions and legacy withdrawals

Sushi’s router can combine liquidity from its own pools and external exchanges. A Sushi trade therefore need not be executed entirely against Sushi liquidity. The September 2025 Route Processor 9 announcement describes additional external-pool support and distinguishes future Sushi v4 work from integrations already announced. A familiar interface name does not identify every contract used by the selected route.[3]

An acceptable target price does not guarantee that sufficient liquidity will fill the instruction. The guide lists a 0.25% fee; a universal minimum size and partial-fill rule were not established. Its expiry options describe resting instructions, not the maximum time that an ordinary blockchain transaction may remain pending.[4]

DCA divides an allocation into scheduled purchases or sales. The FAQ says an active schedule can be cancelled before remaining trades execute, but cannot be modified; replacing a schedule is different from changing an existing one. Its later wording about adjusting an order is less precise. The July 2025 launch notice names Katana, Arbitrum, Base and Ethereum for the automated-order services.[5][6]

The separate perpetual interface exposes trading activation, vault deposit/withdrawal controls and position, funding and transfer histories. That establishes an additional interface, not a complete verified specification of its collateral, liquidation thresholds or builder surcharge. Those product terms were not established from the accessible screen. Spot pool fees should therefore not be reused as a perpetual tariff.[23]

Blade is described as a managed-liquidity design using external prices and dynamic rebalancing, rather than a conventional constant-product pool. Its announcement markets removal of impermanent loss and presents a model-based performance comparison. That description is not a guarantee of principal, future returns or freedom from oracle, strategy and contract failure. The actual vault’s controls and exit conditions still matter.[22]

These figures describe different products and fee layers. The basic-screen 0.35% observation is dated 20 October 2026; the 29 October extraction exposed the fee label without a numerical rate. Published automated-order and cross-chain charges have their own scope. A quote can already include deductions, so adding them again would double-count costs.[2][7]

Four illustrative DCA trades of 250 units create 1,000 units of turnover. At 0.25%, the UI charges total 2.5 units, excluding pool and network costs; each execution can receive a different token amount.[5]

Slippage tolerance and price impact are separate from a platform fee. Impact reflects the proposed trade relative to available liquidity; tolerance constrains acceptable movement before execution. If a fee-adjusted quote is 100 output tokens and tolerance is 0.5%, an illustrative minimum is 99.5. Raising tolerance permits worse execution and does not create missing liquidity.[9]

The Katana pool-creation screen also distinguishes manual ranges from automated vault strategies. A pool’s selected tier is not a promised annual return. Its estimate labels APR as an in-range figure excluding impermanent loss, and the interface says a position outside its range earns no fees. A displayed strategy choice therefore needs its own cost and risk assessment.[8]

Fiat purchases are offered through an Onramper integration that compares third-party providers. The selected provider verifies and processes the purchase, then delivers crypto to the specified wallet. This is not a Sushi bank balance. Confirm the network, receiving address, total purchase cost and provider before payment; the guide’s historical country and currency counts are not a current permission matrix.[10]

SushiXSwap’s current FAQ describes LiFi routing across bridge providers and a choice between faster execution and a better estimated return. A bridge route has more stages than a same-chain swap. Inspect the source asset, destination representation, bridge and expected receipt; successful source submission alone does not demonstrate final delivery or destination-side execution. Keep enough native gas for any separately required transactions.[12]

To reduce a concentrated-liquidity position, the walkthrough directs users to the correct network and wallet, then My Positions and Decrease Liquidity. The returned assets reflect the position’s current composition. A pool can move toward one asset as its price changes; an exit does not guarantee the original quantities or the same dollar value as the deposit.[13]

Trident’s main-interface withdrawal deadline was 15 March 2024, according to the deprecation notice. The notice directs later users toward contract interaction and support. This was a specific product transition, not closure of the whole exchange. Do not send new funds to a legacy route simply because an old tutorial still describes it as current.[14]

The remaining deprecated application lists legacy Farm, Trident and BentoBox withdrawals as well as V2/V3 positions, and warns of limited updates. It can help locate old holdings, but its existence does not prove automatic migration, active incentives or continuing strategy maintenance. Identify the original network and position contract before choosing an exit path.[26]

The SushiBar screen provides SUSHI staking and xSUSHI unstaking controls on Ethereum. This is a token-contract position rather than a conventional deposit account or native blockchain-validator stake. A separate fee-sharing description does not establish a fixed yield, a universal cash reward or protection against movements in the underlying token.[15]

Wallet connection, token allowance and transaction signing are distinct permissions. The revocation guide links an allowance-review tool and explains revoking old approvals, including historical RouteProcessor2 approval guidance. Closing the site or disconnecting the wallet is not evidence that a contract allowance has been removed. Inspect the spender address and network when reviewing an approval.[17]

Sushi’s April 2023 RouteProcessor2 post-mortem documents an exploit involving that router and affected approvals. It also records a historical claims process. That event should not be described as a current vulnerability in every later router, nor should the historical portal be treated as a standing promise to reimburse every future loss.[18]

The June 2024 routing explainer says Cantina audited RP4. The later RP9 announcement concerns a different iteration, so the earlier statement does not establish audit coverage for every current component. Contract version, deployment and review scope matter more than a generic statement that the brand has been audited. No user-beneficiary insurance limit was verified.[19]

The May 2025 token-scanner announcement describes De.Fi and GoPlus indicators for buy/sell taxes, transfer restrictions, ownership powers and honeypot behaviour. These are screening signals. A clean display is not proof that a token is safe, liquid or sellable under all conditions, and a token creator’s powers can differ from the router’s permissions.[20]

Managed Blade liquidity introduces dependence on its external pricing and rebalancing architecture. A marketing claim about eliminating one form of divergence loss does not remove general asset-price exposure or demonstrate that every withdrawal is immediately available. Modelled historical returns should not be substituted for a live vault’s observed net performance.[22]

The perpetual-vault page displays a jurisdiction-restriction notice. The linked application terms could not be substantively retrieved during this review, so a complete current country list, minimum-age rule and exact contracting entity were not verified. The ability to load a public page does not establish permission to use every product.[23][30]

Fiat providers can require identity verification, billing checks and transaction-specific information. The Onramper FAQ explains that another purchase may trigger another verification request. Eligibility for a connected-wallet swap therefore does not guarantee acceptance by a card issuer, bank or fiat provider. The chosen provider’s rules and transaction status govern that purchase.[11]

The Sushi help index provides product articles and a chat entry. No guaranteed staffed hours, dealing-by-telephone facility or complaint-resolution deadline was established. Begin with the relevant product category: a pool withdrawal, bridge transfer and third-party card purchase can require different evidence and assistance.[25]

For an apparently missing wrapped/native-token receipt, Sushi’s support article recommends examining the transaction hash and explorer balance changes. Wallet interfaces may omit internal movements. Preserve the chain, public address, token contract and hash, and check balances before repeating a transaction. A missing display and a failed execution are different possibilities.[24]

Fiat-purchase support follows the provider selected in the Onramper flow. Its FAQ distinguishes a bank preauthorisation from a completed charge and directs users to transaction-status information. A pending card entry is not proof that crypto has been delivered, while cancellation and refund conditions depend on the provider’s transaction terms.[11]

The official scam guidance warns that staff do not require recovery phrases or private keys and do not initiate unsolicited support messages. Use links reached through the official site. An account displaying Sushi branding is not authenticated by that name, and a promise to release funds in exchange for another payment is not a documented recovery procedure.[16]

The route-processor design selects among several liquidity sources. Those external pools can have their own token controls and administrative arrangements; aggregation does not make all participating contracts share one governance model. The public routing explanation is not a complete register of current upgrade keys, pause powers or timelocks across every route.[19]

The June 2024 Sushi Labs announcement describes a development structure alongside DAO governance. That organisational account does not establish an exact legal counterparty for every current product or prove that governance voters can reverse a completed trade. No incorporation jurisdiction, current signer quorum or regulator permission number is inferred from the brand name.[21]

The revocation workflow concerns a user’s contract allowance, not a regulator licence. Removing that authority limits future use of the allowance; it does not unwind a completed swap or automatically cancel a separate scheduled-order contract. Those actions must be checked in their own product workflows.[17]

Sushi and SushiSwap are treated as aliases of the same exchange family. The brand’s published material includes pool protocols, aggregation and developer products; these should not be counted as independent exchanges merely because their screens use different product names. An exact current contracting-company map was not established.[1]

DefiLlama’s combined Sushi page, retrieved on 20 October 2026, reported approximately US$237.55 million of DEX volume over its rolling 30-day window and US$8.47 million over 24 hours. Its aggregator series was separate. These are captured observations across included components, not a fixed daily close, a user count or evidence of a particular worldwide exchange rank.[31]

The same data producer separately classifies Sushi Perps as a Hyperliquid builder interface. Its methodology measures leveraged trade notional and builder-code revenue. That scope differs from spot-pool turnover and must not be added to it as if both represented comparable cash purchases. It also does not establish the number of distinct people using the service.[32]

Operator

Sushi Labs and protocol contributors; exact contracting entity not established

Exchange model

Decentralised

Service scope

Spot swaps and aggregation, liquidity positions, scheduled orders, cross-chain routing, SushiBar and a separate perpetual interface.

Client types

Retail clients

Pricing publication

Public pricing

Other names

SushiSwap; Sushiswap

Funding scope

Wallet tokens and native gas; third-party fiat purchases and bridge routes have separate requirements.

Custody and asset handling

Connected-wallet approvals, pool positions and additional provider dependencies for automated, bridged or managed products.

Client eligibility

Product-specific restrictions; an exact current application-wide country matrix was not verified.

Support

Official help centre and chat entry; fiat-provider issues follow the selected provider.

Authorisation and registration scope

No exact contracting entity and matching exchange permission independently established.

Exchange metadata checked 20 Oct 2026Source 1Source 2Source 7Source 8Source 10Source 11Source 12Source 17Source 19Source 21Source 23Source 25Source 30

The Sushi API reference exposes chain-specific quote and swap routes, token and price data, and liquidity-source endpoints. These support integrations rather than constituting a complete personal account statement. A returned quote or transaction payload is not proof of settlement, and an API response does not itself confer permission to spend a wallet’s assets.[28]

The Blade reference separately lists pool data, quote generation, quote signing and deposits. In this context, a server-signed quote is different from possession of the user’s private key. The endpoint list alone does not establish per-user allowance limits, live risk settings or the complete fee and withdrawal conditions of a managed pool.[29]

Order histories and public chain records can help reconstruct transactions, but a complete tax export was not established. Incoming transfers, acquisition costs, rewards and activity on other venues may still need reconciliation. The missing-balance guide’s explorer checks are useful evidence for a particular transaction, not a replacement for a complete portfolio record.[24]

Developer SDK/API resources and the documentation assistant help integrations read or construct transaction information. They do not themselves grant wallet-signing authority. Wallet recovery follows the connected wallet’s recovery arrangement.[27]

Cancel remaining DCA instructions in the product and verify their status. Closing a browser is not the published cancellation workflow; scheduled fills may execute at different prices.[5]