Minimum Received on a Crypto Bridge: The Main Number

Minimum received on a crypto bridge is the value that lets a transfer acceptable, not the amount shown as the optimistic quote. It is the lower bound encoded in the sent transaction: if fees, price movement, or route conditions leave less than that amount, the transfer should not go through under those terms.

What “minimum received on a crypto bridge” actually means

Minimum received is the destination-side floor a bridge or bridge-and-swap route must meet for a transfer to complete as estimated. The starting amount is what goes out of the wallet; the estimate is what the screen expects; minimum received is the limit that decides whether the execution is acceptable. On Ethereum, agreements run according to public code rather than a later human decision, which is why this number means more than a reassuring status message from an interface. Ethereum’s overview sets out that core rule clearly.

Why the quote is not the number that decides it

A transfer can include more than one working piece: a source-chain swap, bridge fee, relayer or liquidity fill, and a destination-chain swap. The listed quote is figured before the wallet signs. Minimum received is worked out from that estimate after the set deterioration—often called slippage—has been applied.

For an illustrative quote of 1,000 USDC with a 0.5% margin, the minimum received is 995 USDC. If the route can deliver 997, it passes. If it is able to deliver only 994, a correctly designed route must stop it rather than silently deliver less. Gas is usually paid on its own in the network’s native token, so it should not be confused with this output limit.

Where the limit lives in the transaction

The interface may call it “minimum received,” “min amount out,” “output amount,” or a route-specific limit. The label changes; the job does not. It becomes calldata sent to a contract or instruction passed to the protocol handling the route. A canonical transfer of the same asset may have fewer price-sensitive steps than a bridge-plus-swap, but fees and route rules can still determine whether a small transfer is viable.

Gnosis Bridge is a useful example of why the route matters: its Ethereum-to-Gnosis canonical route makes the asset and destination explicit, so the relevant limit is about what that selected route can deliver—not a generic “bridge price.” By contrast, Across illustrates an intent-based bridge-and-swap flow, where the output promise is especially central because a filler delivers the destination-side result.

How to set it without guessing

• Use a tighter limit when the exact destination amount is essential, such as funding a payment or a follow-on swap.
• Use more tolerance only when execution matters more than a precise output and the route is known to move.
• Do not make the limit so tight that normal fee or price changes cause repeated reverts.

How to verify it really happened

I verify the source transaction succeeded, then check the destination-chain transaction or balance change and compare the actual received amount with the signed minimum. “Submitted,” “confirmed,” and “filled” are different milestones; only the destination-side result proves the limit was met.