Why a Mantle Bridge Quote Can Change After You Accept It

A bridge router can refresh your Mantle transfer quote seconds after you accept it, changing the estimated amount before your transaction reaches the source chain. “Accept” may acknowledge a screen update; it does not necessarily submit or lock in a transfer.

• A displayed quote is an estimate tied to a route and a moment in time.
• A wallet signature authorizes specific transaction details.
• A transaction sent to the network cannot have its terms silently rewritten.

What does accepting a bridge quote actually do?

Accepting a quote usually tells the app you are willing to proceed with the route and terms it currently displays. The app may then prepare a transaction, request a token approval, or ask your wallet to sign. Those are separate steps, and only the wallet request shows what you are actually being asked to authorize.

A route can include more than a direct transfer. It may swap your source token, send it across chains through a liquidity provider, then swap again on the destination chain. For a fuller explanation of how mantle bridge routes differ, see the guide to canonical routes. The route’s final estimate can change if a price, fee, or available liquidity changes before the transaction is built.

A canonical bridge transfer and a routed swap are different operations. A canonical route moves a supported asset between its mapped representations; a swap route trades one asset for another, so its output depends on exchange rates and pool conditions. Check which kind of transfer the screen describes before treating its estimated output as fixed.

Why can the amount change after you accept?

Most quotes are assembled from information that can move. A swap pool’s reserves change when other trades land. A liquidity provider may update its fee or available inventory. The app may also refresh its estimate after a delay, or use a different route when it prepares the transaction.

Some costs are estimates too. Network fees depend on the transaction and current network conditions; the app may recalculate them as it builds the transaction. That can change the estimated net amount without changing the token exchange rate. Look for a breakdown of the amount sent, any swap, provider or bridge fees, and the amount expected to arrive.

It also matters whether you have sent anything yet. A token approval, if needed, is often a separate transaction. Signing an approval lets a contract spend tokens up to the approved amount; it does not itself send the bridge transfer or guarantee the quote will still be available afterward.

What protects you when a quote moves?

Before you sign, inspect the transaction in your wallet and compare it with the app’s latest terms. For a swap, look for a minimum amount out or a slippage limit: these set a boundary on how much worse execution can be before the transaction fails. A tighter limit can protect the price, but a transaction may revert if the market moves too far before it executes.

That protection is not a promise that the displayed amount will arrive. The transaction may execute at a worse rate within the allowed limit, or fail and still cost a network fee. A bridge route without a swap may not use the same slippage setting, so check the route details and transaction fields rather than assuming every quote has one universal price guard.

• Confirm the source and destination networks, token, amount, and receiving address.
• Read the wallet’s transaction details; reject a request that differs from what you intend.
• Check the minimum output, deadline, and fees when the route includes a swap.
• If the amount changed and the terms are unclear, reject the request and get a fresh quote.

Once a transaction is signed, its encoded instructions are fixed. A website cannot silently edit the amount inside that signed transaction. The contract may still execute under its rules, revert if a limit is exceeded, or fail for another reason. If you have only accepted a screen prompt or signed an approval, the transfer itself may still be waiting for a separate transaction.

What should you do if the quote changes?

Pause before signing a changed transaction. Compare the new net amount and fees with the quote you accepted, then decide whether the route still suits your needs. If the wallet shows an unexpected token, recipient, or amount, reject it and return to the bridge app.

If you already submitted the transfer, check its status using the source transaction hash and the bridge’s tracking page. A quote changing in the interface does not by itself mean the submitted transaction changed. What happens next depends on whether the source transaction confirmed and on the route’s settlement process.

The practical rule is simple: treat a quote as a temporary estimate until you inspect and sign the transaction that will execute. Acceptance can begin that process, but your wallet is where the actual terms become visible.