Why Minimum Received Matters in a Mantle Bridge Swap

Minimum received sets the least amount of destination tokens a bridge swap can deliver before the transaction should fail, protecting you from a worse exchange rate than the one you accepted. Without that floor, a swap may complete at a lower output if prices move or available liquidity changes between quotation and execution. With it, the trade-off is explicit: a stricter floor protects the rate but makes the transaction more likely to revert.

That matters because a bridge swap combines steps that a simple token swap does not. Assets may need to leave one network, arrive on another, and be exchanged along the way or after delivery. The displayed estimate is a forecast for the route, while minimum received is the boundary the route is allowed to cross. The setting cannot make the estimate certain; it gives the transaction a defined condition for proceeding.

For a fuller explanation of the checks around this route, see mantle bridge. The key point here is narrower: minimum received is about the token output the swap accepts, not a promise that every bridge step will be instant or cost-free.

What does minimum received mean in a bridge swap?

Minimum received is the lowest destination-token amount the swap will accept when it executes. If a quote estimates 100 units of a token and the minimum is 98, the transaction is permitted to complete at 98 or above; below that threshold, a route using an on-chain swap limit should fail instead of delivering less. The exact label and calculation can differ by interface, so check which amount the displayed floor refers to: the swapped output, the bridged delivery, or a combined estimate.

The estimate and the floor serve different purposes. An estimate helps compare routes and understand the likely outcome. The floor defines a limit on the execution outcome. It is not an extra fee, and it does not increase the number of tokens sent. Nor does it mean you are guaranteed to receive the estimate: a result between the estimate and the floor may still be accepted.

On-chain swap contracts commonly enforce a minimum output as part of their trade conditions. A bridge flow can include separate contracts or services for transfer and swapping, though, so do not assume one visible minimum governs every stage. Read the transaction summary and confirmation details to see whether the limit applies to the swap only or to the amount expected on the destination network.

Why can the amount change after the quote?

A quote is assembled from conditions that can change before execution. The main sources are price movement and liquidity: if the market price shifts, or the route can no longer trade against the same depth, the output may differ. A multi-step route can also depend on several pools or conversions, so a change at one point can affect the final token amount.

Fees are related but distinct. Network fees pay for transaction processing, and bridge or route fees may be deducted according to the service’s design. A minimum received figure should not be read as a cap on those costs unless the interface explicitly says it includes them. Compare the quoted output, estimated fees, and minimum as separate figures where they are shown.

There is also a difference between price impact and slippage. Price impact is the effect of a trade’s size on the price available from current liquidity. Slippage is the difference between the quoted and executed result, which can arise as conditions change before the trade lands. A minimum received setting limits the outcome you accept; it does not erase price impact or hold a quote open while the transaction waits.

How should you choose a minimum received?

Choose a floor that reflects the amount you are actually willing to receive, then compare it with the quoted output before signing. A very tight floor offers stronger protection against a deteriorating rate, but it can cause a revert during ordinary market movement. A loose floor is easier to execute, but it authorizes a larger shortfall. There is no universal percentage that is right for every token pair or route.

Before confirming, check these details:

• Confirm the source and destination networks, and the token you expect to receive.
• Compare the estimated output with minimum received, including the units and decimals shown.
• Review whether displayed fees are deducted from the output or charged separately.
• Check the route’s stated failure behavior and what happens to assets if a swap step does not complete.

If the floor is crossed and the swap reverts, the intended exchange does not complete. A failed transaction can still consume a network fee, and a bridge involving multiple stages may have its own recovery or refund process. Those outcomes depend on the route’s design, so inspect its transaction details rather than assuming a failed swap means every asset returns immediately to the original wallet.

For most readers, the better choice is a floor they can explain in token terms: “below this amount, I would rather the swap stop.” Set it from the displayed estimate and your tolerance for a worse rate, not from a desire to force execution. If a transaction repeatedly fails, compare a fresh quote and the route details before deciding whether a wider floor is acceptable.

What should you watch after setting the floor?

Watch the quoted output, minimum received, and fee breakdown at the moment of confirmation, then check the transaction status and destination balance after submission. A pending transaction can face different market conditions from the quote, and a completed source-network transaction does not by itself prove that every destination-side step has finished.

The useful distinction is simple: the estimate says what the route expects; minimum received says how poor the swap result may become before it stops. Track whether the interface states that the floor covers the swap or the full bridge route, how it handles a reverted step, and whether fees remain payable on failure. Those specifics determine how much protection the setting actually provides.