Dodo swap liquidity, fees, and execution limits

Liquidity and token behavior shape the available exchange

An executable quote requires liquidity for the selected tokens and an execution path compatible with their contracts. DODO X searches beyond DODO’s own pools and can incorporate other exchanges and aggregators. This broadens the available routing choices, although it cannot create liquidity for an unsupported trade. The input amount also matters: a route suitable for a smaller exchange may deliver a worse rate when it must absorb a larger sale.

Token identity and token behavior are separate concerns. A matching symbol does not establish that two selections represent the same contract. Transfer restrictions or unusual token logic can also prevent an otherwise plausible exchange. A displayed asset name therefore needs the context of its network and contract, especially when several search results share the same ticker.

Wallet readiness determines whether the quote is usable

Before approving spending or submitting a swap, check the wallet network, available input balance, and funds for gas.

The network holding the input

A same-network swap operates on balances held on that network. Selecting a different network in a wallet changes the account view; it does not move assets between chains. DODO distinguishes its same-network routing service from its cross-chain service. That distinction determines whether the intended output requires only a swap or also a bridge operation.

Funds for transaction execution

The sell-token balance alone may be insufficient to execute the exchange. Ordinary wallet transactions also require the network’s gas asset, and a separate approval can consume gas before the swap begins. If the input itself pays gas, spending its entire balance can leave inadequate transaction funding. The wallet’s estimate relates to the proposed transaction, so it deserves another look after a route or amount changes.

Approval changes spending permission

An ERC-20 approval grants a specified contract permission to spend a token up to an allowance. It does not exchange that token. An existing allowance can cover another trade from the same wallet account when the token, spender, and network match and the remaining allowance covers the input amount. Connecting a wallet establishes access to the account interface; approval changes an on-chain permission.

DODO’s V2 architecture separates token authorization through DODOApprove from several operation-specific proxy contracts. Consequently, an approval recipient need not be the same contract used for the eventual swap call. The relevant check is the intended spender and its allowance for the selected operation. A larger allowance reduces repeated approval transactions but grants more spending capacity than a narrowly sized one.

PMM pricing responds to pool inventory

DODO’s Proactive Market Maker algorithm adjusts quoted prices as pool inventory changes. Its price curve uses a reference price and a parameter controlling sensitivity to inventory imbalance. Concentrating liquidity around a price can support favorable execution near that region, while larger inventory changes alter the rate. Not every aggregated trade uses a PMM pool. The routing service can select liquidity with other pricing mechanisms, so the final quote reflects the pools the route actually uses.

Route structure changes the balance between output and gas

SmartTrade can route the input along one path or divide it among several liquidity sources.

A single path through available pools

Linear routing sends the trade along one sequence of pools. That sequence can include an intermediary token when a direct pool offers weaker execution or no usable connection. A single path therefore does not necessarily mean a single pool. Its contract interactions determine part of the execution cost.

Input divided among liquidity sources

Split-order routing allocates portions of the input across pools. This can reduce the pressure placed on one pool and improve the quoted output, while additional interactions can increase gas consumption. The useful comparison is between executable quotes for the same input and destination, including their transaction costs. More routing complexity alone does not establish a better exchange.

Pool charges and network costs have different causes

The cost of a swap includes charges associated with its liquidity and routing, plus network execution costs.

Charges associated with the trade

DODO distinguishes a routing fee from liquidity-provider fees. Pool fees vary, so one percentage cannot describe every available route. The quote’s fee breakdown matters more than assuming all pools follow one schedule. When comparing outputs, establish whether the displayed amount already includes trading charges; subtracting an included charge again would distort the comparison.

Charges associated with execution

Gas pays for computation on the network. It depends on transaction work and the applicable network fee conditions, rather than simply following the amount sold. This means a modest exchange can carry a substantial proportional execution cost. A separate approval adds another transaction, while a swap that reverts after execution begins can still consume gas.

What does slippage tolerance actually limit?

Slippage tolerance limits the deterioration in execution you accept relative to the quote used to construct the trade. For a fixed-input swap, that protection commonly takes the form of a minimum output amount. DODO AMM V3’s exact-input swap requires the output amount to meet or exceed its specified minimum. This is an execution condition, rather than a promise that the displayed quote will remain available.

Price impact describes how the proposed trade affects pool pricing; slippage concerns execution moving away from the quote. Raising tolerance does not add liquidity or improve the pool’s price curve. It permits a less favorable result before the protection stops execution. A trade can therefore succeed within its configured limit while delivering less than the earlier estimate.

A transaction deadline limits stale execution

A configured transaction deadline prevents the swap from executing after its permitted time window. This differs from slippage protection: the deadline limits when execution can occur, while the minimum output limits an acceptable result. Expiry does not itself remove a pending transaction from the network. A submitted transaction and a successful transaction remain different states, so elapsed time alone cannot establish completion.

---

Conditions for proceeding with a quoted swap

Consider a same-network exchange where the input is already in the wallet and a later action needs the output. Before granting permission or submitting the swap, establish whether this quoted trade can satisfy that need:

• The wallet holds the intended input asset on the quoted network, with the correct contract address if it is a token.
• The selected output matches the asset needed for the later action, including its contract address if it is a token.
• The input balance and gas balance cover their separate obligations.
• If token approval is required, the spender matches the intended operation and the allowance covers the input amount.
• The minimum output remains acceptable after accounting for the quoted charges.

View full-size image

With those conditions met, any required approval precedes submission of the swap. Completion requires a successful swap receipt and the corresponding output balance at the intended address. The transaction hash provides a way to inspect the actual operation, rather than relying on a success message alone. If the swap receipt instead records a revert, the expected output has not arrived through that transaction. Stop the dependent action and reassess the failed condition before requesting another quote; repeating the trade without resolving its cause can consume more gas.

Cross-chain completion requires destination evidence

A cross-chain exchange adds a bridge operation between the starting network and the destination network. DODO’s cross-chain service returns routes for selected assets and provides order-status information. A successful source transaction establishes only that part of the operation; it does not, by itself, establish receipt of the destination asset. Check the destination transaction and confirm receipt of the intended asset at the recipient address on that network. Its supported assets and available channels also govern compatibility, so same-network swap availability cannot establish cross-chain availability.

The required output determines whether to swap now

An immediate swap fits a task when an available route delivers an acceptable output under the proposed limits. Comparing it with a direct pool requires the same input amount, output asset, network, and cost basis. DODO’s aggregator may find additional liquidity, but the decision still rests on the actual executable terms. Providing liquidity is a separate operation with different exposure; it is not a prerequisite for buying a token.

A limit order expresses a target price and expiration rather than accepting an immediate quote. Where that mode is available and the order meets its requirements, it offers another way to express the intended exchange, although submission does not establish a fill. If the output must exist before another action can begin, an unfilled order cannot satisfy that requirement.