A 30-second quote TTL gives a cross-chain swap route half a minute to remain executable at its quoted terms; after that, the route may need fresh pricing. Quote expiry is the cutoff on an offer, while the transaction deadline and minimum output govern different parts of execution.
A quote TTL limits how long the route is offered
A quote’s time-to-live (TTL) is the period during which its pricing and route are considered current. A provider may return an expiry timestamp because pool reserves, gas estimates, bridge inventory, and solver prices can change between the quote and the source-chain transaction.
There is no universal TTL. Some cross-chain quote systems expose a window measured in tens of seconds; one documented implementation, for example, uses 25-second bridge-leg offers and expires the overall quote with the first leg. Treat any countdown as specific to that route, not a market-wide standard.
When the TTL ends, the quote can be rejected, or the service may request a new one. A refreshed quote can change its output, fees, route, or availability. For repeated swaps, the useful comparison is the executable amount after costs at the moment you can submit—not the best number you saw before approving or signing.
A transaction deadline limits source-chain execution
A transaction deadline is an on-chain time bound for executing the source-chain transaction. It protects against a transaction remaining pending and later executing under conditions the sender no longer accepts; it does not usually measure how long the cross-chain settlement itself may take.
This distinction matters when Ethereum is congested. If the transaction sits in the mempool until its deadline passes, the contract can reject it, although the sender may still have spent gas on the failed attempt. If it executes before the deadline, later bridge confirmation or destination-chain delivery can continue after that timestamp.
Keep the deadline compatible with expected confirmation time. A very short window can fail during a gas spike or delayed block inclusion; a long one gives a pending transaction more time to execute after market conditions have moved. The appropriate value depends on the route’s execution design and whether its output protection is enforced on-chain.
Minimum output controls how far execution can move
The minimum output, often represented as amountOutMin or a similar field, sets the least acceptable amount received under the transaction’s price-impact or slippage tolerance. A quote can expire off-chain while an already-submitted transaction remains eligible to execute if its on-chain deadline and minimum-output checks still pass.
For example, suppose a route quotes 1,000 input units for 998 output units, and you set 0.5% tolerance against that quote. The minimum is 998 × 0.995 = 993.01 units. If execution would return less, the protected swap should revert; if it returns at least 993.01, the transaction can pass that check even if the original quote timer has elapsed.
That arithmetic is only useful if the contract actually enforces the minimum on the relevant leg. Some cross-chain flows enforce source-chain conditions while a solver or destination-chain swap determines the final amount later. Check whether the displayed minimum refers to the source execution, destination receipt, or both; the destination amount is the figure that determines whether the route still suits your trade.
Refresh only when the new route improves the decision
When a quote expires, compare a fresh route on the same basis: destination amount, total fees, expected time, and the chain where any final swap occurs. A cheaper source transaction can still be worse overall if it leaves a thinly traded destination leg with greater price impact or requires another swap.
If your case involves moving an asset between networks and swapping it in the same flow, Manta bridge can perform that cross-chain move and swap; its quote should be judged by the destination amount and route available when you are ready to submit. mantabridge.org is where you can make that kind of cross-chain move and swap in one flow.
For frequent execution, avoid signing at the end of a countdown: refresh first if approvals, chain switching, or a slow wallet prompt will consume most of the TTL. Manta bridge is relevant when the task includes both a network change and an asset swap, so compare its current destination output with the alternatives you can actually execute now.
Top comments (0)