A minimum received is the least amount of destination tokens your cross-chain swap promises under its current quote. It matters most when prices can move before the route finishes: you may receive less than the estimate, or the destination swap may fail.
When you compare a Mayan bridge route, check the minimum received and the destination token because a route may swap your asset before it arrives. The quoted amount is an estimate; the minimum is the transaction’s floor, if the route supports one.
How do you read the quote?
Read the quote from the amount you send through to the amount you should receive, then check what fees and conditions affect that result. “Slippage” is the difference between the quoted price and the price available when a swap executes.
For example, say you swap 1 SOL and the quote estimates 150 USDC. If the route applies 2% slippage tolerance, its minimum may be 147 USDC: 150 × 0.98. If the swap can only deliver 146.5 USDC, a minimum-output check should stop that swap from completing at the lower amount. The exact setting and failure behavior depend on the route.
Before you approve, check these details in the quote:
- Destination token: Confirm the token and network match what you intend to receive.
- Minimum received: Compare this with the estimate; a wide gap means you accept more price movement.
- Fees: Check source-network gas and any route or destination fees shown. The source fee may still be spent if the later swap fails.
- Quote expiry: If the quote expires, refresh it and review the new minimum before signing.
What if the amount changes or the swap stalls?
A cross-chain swap can have two stages: your source-chain transaction, then delivery or a swap on the destination chain. Because those stages can settle separately, a confirmed source transaction does not by itself prove that you received the destination token. The route’s status and recovery rules matter if the second stage is delayed or fails.
Keep the transaction ID after you submit. Solscan can show the source transaction on Solana, while Etherscan can show one on Ethereum; then check the route’s status for the destination stage. If the source transaction succeeded but delivery is pending, follow the route’s stated retry or recovery process instead of submitting the same transfer again. A Mayan bridge transfer can involve the same distinction between source confirmation and destination completion.
Should you set a higher slippage tolerance?
Only raise it when you understand why the swap is likely to move and the displayed minimum remains acceptable. A higher tolerance can help a volatile or thinly traded pair execute, but it also permits a worse exchange rate. If the minimum falls below what you are willing to receive, wait for a fresh quote or choose another time.
Can the source transaction succeed while the destination swap fails?
Yes. Some routes confirm the source transfer before attempting a destination-side swap, so a later failure may need a retry or recovery step rather than an automatic reversal. Check the route’s status using the transaction ID and follow its instructions; do not assume the funds are lost or send a replacement transfer before checking.
Which number should you compare between routes?
Compare the minimum destination amount after fees, using the same source amount and destination token. Headline estimates alone can hide different fees or slippage limits. Also check whether the destination network’s transaction cost is included; if it is not, the amount left after you pay that cost will be lower.