Treasury swap slippage budgets set the execution limit

A treasury slippage budget sets the largest execution shortfall a crypto treasury will accept before it submits a swap. It turns a quoted output into a minimum acceptable output, so the transaction either meets the treasury’s limit or reverts.

What does a slippage budget measure?

The budget measures the gap between the output a swap route quotes and the minimum output the treasury will accept at execution. A treasury can express that limit as a percentage or as a minimum token amount; the transaction’s parameters determine which one applies.

The quote is a snapshot, while execution happens later. If pool prices move before confirmation, the transaction may return fewer tokens than quoted. A route that divides the trade across pools can also change the expected output. For a closer look at route and pool trade-offs, see how a Base swap weighs route costs and speed. That comparison helps explain why the best quoted route is not always the cheapest to execute.

Slippage is not the same as every cost of a swap. The quoted output may account for pool fees and price impact, but network fees are separate, and the transaction’s minimum-output check does not cap them.

How should a treasury set its limit?

A treasury should set the limit from the trade’s purpose, size, liquidity and urgency, then compare it with the quote’s expected output. A tight limit protects the target amount but makes a price move or stale quote more likely to cause a failed transaction; a loose limit makes execution more likely while allowing a worse fill.

Before setting the limit, treasury staff can check:

• The quoted output and the minimum output the transaction will enforce.
• Pool depth and route composition, which affect how much the trade moves prices.
• Whether the trade can wait for a fresh quote or must execute promptly.
• Network fees and any internal spending limit, tracked separately from slippage.

A fixed percentage across all swaps is easy to administer, but it ignores differences in asset liquidity and trade size. A better policy sets a ceiling by trade type or risk tier, with tighter limits for routine conversions and documented exceptions when execution is time-sensitive.

What happens when a swap exceeds the budget?

If execution would fall below the transaction’s minimum output, the swap reverts instead of completing at that price. The treasury keeps its input tokens, but may still owe the network fee for the failed transaction.

Staff can respond by requesting a fresh quote, choosing another route, reducing the trade size or waiting for conditions to change. Splitting a large swap may reduce its effect on a pool, though extra transactions can add network fees and create more execution steps.

A slippage budget works best as one control in an execution policy: compare the quote with the minimum output, track fees separately, and record exceptions. The next decision is whether to retry, change the route or defer the swap.