Orbiterfinance swap slippage settings and minimum output

Orbiterfinance accepts a slippage percentage that expresses your tolerance for price movement within a swap quote. To change it, include the chosen percentage in a new quote request and examine the returned minimum destination amount. A tighter setting allows less deterioration; a wider setting allows more within the same swap comparison. Route availability and the transaction's output requirement still determine execution.

The expected output, the minimum output, and the eventual received balance have different meanings. Changing the tolerance affects the terms that you'll accept before execution. It doesn't edit a transaction that you've already signed.

A wider slippage setting permits a lower swap output, so compare the minimum received amount before accepting a refreshed quote.

Tighter and wider tolerances share an output boundary

Both settings express how much unfavorable movement a swap request can accommodate against its quote. A lower tolerance keeps the acceptable output closer to the quoted amount. A higher tolerance gives the transaction more room to execute after a price change, while accepting a larger possible reduction. Neither setting improves the price that the available liquidity offers.

The comparison holds when the input amount, token pair, and quoted output remain unchanged. A refreshed quote can move the starting point. Keeping the same percentage therefore doesn't necessarily preserve the same token minimum across different requests. Choose the tolerance by considering the output reduction you can accept. A successful swap can still produce an amount you consider unattractive.

The percentage determines the room below a quote

Orbiterfinance's quote request treats slippage as a percentage, separately from the token amount that you're exchanging. The percentage describes an acceptable price fluctuation. It isn't an amount of the input token, a gas budget, or a fee payment.

For a simple percentage comparison, let Q represent the quoted output and t represent the tolerance percentage. The corresponding output floor is Q multiplied by (1 - t/100). A larger t lowers that floor. This arithmetic explains the relationship; a route's returned minimum supplies the amount applicable to its transaction.

Token precision also matters when expressing the floor as a transferable amount. Calculations must respect the output token's decimal units.

Quote amounts and contract thresholds describe different limits

The quote's details distinguish expected destination output from the minimum destination output that the request accepts. Read both amounts in the destination token's units. They don't establish a completed payment, and comparing them with the input quantity can mislead when the swap changes the asset.

The destination amount in the quote

The field destTokenAmount identifies the quoted destination quantity; minDestTokenAmount identifies the minimum acceptable destination quantity. Their difference describes output flexibility within that quote. An integration needs the correct token precision to display these quantities intelligibly, while preserving the underlying amounts that the request returns.

The boundary used during execution

The swap contract's output requirement

The Aggregator's executeSwap method requires its output to exceed minOutputAmount. This parameter belongs to the swap request alongside its input token, output token, amount, and recipient. It gives that operation an explicit output condition.

The scope of the destination minimum

A destination minimum and a swap contract minimum can describe different stages of a combined route. Compare them only after establishing their token and execution scope. A final destination quantity doesn't automatically describe an intermediate swap's output requirement.

Liquidity determines the price that tolerance starts from

Price impact describes the price change that a trade itself causes in the available liquidity. Slippage describes the difference between the expected exchange price and the execution price. A quote can already reflect the trade's effect on the pool before later market movement changes the output again.

Raising tolerance leaves that starting price unchanged when everything else stays equal. If the quoted exchange is already unfavorable, permitting further deterioration won't repair it. Available liquidity and trade size affect pool pricing, so changing the input amount can produce a different quote. That is a different comparison from changing tolerance against an unchanged quote.

The route determines where a swap limit applies

A same-chain swap and a cross-chain swap can both include token exchange, so output conditions matter in either case. A same-chain exchange keeps the selected network unchanged. A cross-chain route can combine token exchange with a bridge, introducing a destination amount beyond the swap's immediate output.

The returned actions identify the route that the quote actually proposes. Quotes can include approval, swap, and bridge actions where the chosen route requires them. Their order matters. A setting that affects a swap doesn't establish that the entire cross-chain transfer shares one atomic execution boundary. Keep the minimum attached to the operation and token that it governs. Bridge fees and destination settlement remain separate considerations when the requested route includes a network transfer.

Fees and gas remain separate from acceptable movement

Slippage tolerance permits an output difference; it isn't a charge that the service automatically collects. The quote supplies fee information separately, including swap and transfer-related fields where applicable. Increasing the percentage doesn't mean that the transaction must lose that percentage, and a tighter tolerance doesn't remove the charges attached to its route.

Open full-size image

Gas pays for network execution and has a different purpose from an output threshold. A swap with an acceptable output still needs the resources required to execute its transaction. When comparing requests, keep the quoted destination amount and applicable charges on a consistent basis. Mixing token quantities with monetary fee estimates obscures what reaches the recipient.

Transaction data fixes the terms that you sign

A revised tolerance belongs in a revised quote before the corresponding transaction receives your signature. The quote returns transaction information, and the signable transaction carries its destination, encoded data, value, and gas limit. An interface label changing afterward doesn't rewrite those signed fields. If a quote changes while a wallet confirmation remains open, the transaction awaiting approval still uses the data supplied to the wallet. Accepting an updated quote requires the transaction prepared from those updated terms; it can't rely on a percentage shown elsewhere in the application.

After submission, a new quote doesn't amend the submitted transaction. Its execution status determines whether another submission is appropriate.

The failed condition determines whether adjustment helps

A failed minimum-output check concerns the amount received; an unsupported wallet network concerns transaction access. Increasing slippage doesn't add a network to a wallet connector. It also doesn't supply a missing token allowance or replenish the balance needed for execution.

A price-related rejection

When the swap's output requirement blocks execution, a refreshed quote can reveal whether market conditions have changed. Accepting a wider tolerance allows more deterioration only where that condition governs the failure. Keeping the tighter requirement is also a valid choice if the newly offered output is unacceptable.

A failure outside the output check

Allowance, available funds, and transaction compatibility have their own requirements. An integration should distinguish a quote error from a transaction execution error. A failed quote hasn't demonstrated an on-chain failure, while a submitted transaction needs its own execution status. A generic error message alone doesn't establish that slippage caused the problem.

A fresh quote supports alternatives to widening tolerance

Waiting for a new quote or changing the requested input amount can produce different swap terms without first increasing tolerance. Waiting doesn't promise a better price. A smaller trade can have less impact in a liquidity pool, although the chosen route and available liquidity determine the actual change. Compare the new output against the input that now applies.

An application can request another quote for the same supported combination while retaining its preferred percentage. The relevant comparison then includes the newly quoted output and minimum, alongside its execution actions and charges. This keeps a percentage preference separate from accepting a particular exchange rate.

A smaller request also needs transaction data for its revised input amount. The Aggregator carries that amount in inputAmount.

Frequently asked questions about Orbiterfinance