Skip to main content
This error indicates that the expected return amount is below the minimum accepted threshold. It typically occurs due to market volatility or low liquidity.
This error occurs when the exchange rate changes between quoting and execution. You can increase the slippage tolerance to reduce failures, but be aware that it may result in a worse rate.For SDK users, implement acceptExchangeRateUpdateHook and return true to automatically accept updated rates.See SDK documentation
This error means the bridge version you used—mayanWH or mayanMCTP—does not support smart contracts as destination addresses.
Mayan MCTP runs on CCTP, which is slower and incurs higher gas costs on Ethereum mainnet. This method is typically used for large transfers when other bridges lack liquidity.
This error often means the fromAddress does not have enough balance to cover the transaction.
This error appears when the transaction has not yet been indexed by LI.FI. Once it is indexed, the scanner will display the transaction details.
This is likely a custom error from the DEX, such as MinimalOutputBalanceViolation. Most swap errors originate at the DEX level. If not, LI.FI has fallback validation logic. Error selectors vary depending on the DEX.
Refund eligibility depends on the bridge or tool used. Some bridges refund automatically after failure. Others may leave the transaction unresolved.
This substatus is triggered by cBridge. It indicates the transfer could not be processed due to price, gas, or liquidity changes. LI.FI then initiates a refund on the source chain.
PARTIAL is a final status. The full value was received, but in a different token than expected.
Same-chain swaps are atomic: they either succeed or revert (gas may still be spent). In cross-chain routes, the bridge can succeed while the destination swap fails; the user is then automatically refunded on the destination chain, typically in the bridged asset. If a destination swap fails, prompt a fresh quote and approval to finish the swap on the destination chain.