Go to article content
Transitswap

Transitswap slippage

For a fixed input amount, slippage is the difference between quoted and executed swap output. Transit Swap’s documented Router v3 aggregation uses a minimum-output condition to bound acceptable execution.

Estimated output
totalAmountOut is the estimated destination-token amount in the Router v3 aggregation response.
Requested floor
amountOutMin specifies the minimum received amount. The Router v3 instructions use 0 for the initial query and the last query’s minimum for transaction submission.
Tolerance parameter
impact is the Router v3 slippage-tolerance input. The reference gives conflicting scale wording, so its raw values need verification before use.
Route information
dexPath identifies the DEX sources and used parts in the Router v3 aggregation response.

Quoted rate, market movement, and price impact

A quoted rate relates estimated destination-token output to the amount sold. Price impact describes how the trade’s size interacts with liquidity along its route, potentially affecting the quote itself.

Prices can also move while a transaction waits for confirmation. Network congestion can lengthen that waiting period, increasing exposure to price changes. Slippage tolerance expresses the adverse variation the user permits.

Router v3 calls its slippage-tolerance input impact ; the name does not establish a measured price impact for the route.

Minimum-output arithmetic

For a percentage tolerance applied to quoted destination-token output, the corresponding floor follows this relationship:

minimum_output = quoted_output * (1 - tolerance_percent / 100)

Both output terms must use the same destination token and units. Raising tolerance lowers this calculated floor, permitting a worse fill. This arithmetic does not specify the router’s integer encoding or rounding.

The minimum-output condition requires execution output at or above the submitted floor, while other transaction requirements can still prevent completion.

The Router v3 request separates decimal0 , the sell token’s decimals, from decimal1 , the buy token’s decimals. Its documented amountIn calculation uses the sell token’s decimal scale. Keep the destination token’s units consistent when interpreting its output threshold.

Router v3 query and encoding conditions

The Transit Swap Aggregation reference gives 1% = 100 for impact , alongside incompatible base 1000 wording. Its documented integer range of 0 to 10,000 does not resolve that inconsistency. Confirm the intended encoding before translating a percentage into the API parameter.

The zero minimum documented for the initial query supplies no positive execution floor; submission must use the previous query’s minimum.

What to inspect before retrying

Inspect the recorded transaction result and any available failure details before attributing a failure to slippage.

  • Keep token addresses, network, input amount, the part input-amount scale, and token decimals consistent when comparing quotes.
  • Compare the submitted amountOutMin and the original response’s totalAmountOutMin with a fresh totalAmountOut estimate for those inputs.
  • Read dexPath for changes in the proposed DEX route and used parts.

Although a fresh estimate below the old floor fails that output boundary, it does not diagnose the previous failure.

A successful aggregation API response supplies quote information and ABI data for contract interaction, without establishing transaction submission, execution, or destination-token receipt. Transit Finance’s Risk Disclosure notes that an on-chain revert does not refund gas fees already consumed.

Transitswap slippage: What to inspect before retrying - illustration

View image file

- updated