
A bridge minimum is the smallest amount a route will accept for a cross-chain transfer. The binding condition is the route’s minimum after token-unit rounding and any amount deductions, not simply whether the source wallet holds enough.
Why can a small deposit be rejected?
A minimum can come from the bridge contract, a relayer or liquidity provider, or a route-specific rule that filters out transfers too small to process economically. For a developer moving assets between Ethereum and Mantle Network, the Mantle Bridge is one way to make that transfer; the integration still needs to handle the minimum that applies to its selected route.
Cross-chain transfers also take more than one step. A source-chain transaction is submitted and finalized; then a bridge mechanism relays or verifies its message before the destination chain releases or mints the asset. A small amount may be technically valid at the token-contract level yet rejected by a route, or arrive as dust that is too small to use in a later transaction.
Token amounts are stored as integers in the token’s smallest units. An integrator should convert human-readable amounts using the token’s decimals, then round down only if the route permits it. Rounding a value near the minimum can put the submitted amount below the threshold.
How much does the minimum change the economics?
A fixed transaction cost takes a larger share of a small deposit. As an illustrative example, if source-side gas and other fixed costs total $5, they equal 20% of a $25 deposit but 1% of a $500 deposit; the actual cost varies with network conditions and the route. That cost may be paid separately from the bridged amount, or deducted from it, so the integrator must establish which amount the minimum applies to.
For example, imagine a route requiring at least 10 USDT to arrive, while the source amount is 10.2 USDT and a 0.3 USDT deduction applies. If the minimum is checked against the destination amount, the transfer falls short even though the source amount exceeds 10 USDT. Treat this as a test case, not a claim about a particular service’s current rules.
The trade-off is between accepting small deposits promptly and batching them to spread fixed costs. Batching can improve cost per user, but it adds waiting time, accounting work, and the need to track each user’s claim against the eventual aggregate transfer. For an integration, set a product minimum that covers the route minimum plus a margin for rounding or deductions, and explain when a deposit will be held for batching.
What should an integration check?
Check the effective minimum for the exact asset and direction before submitting, and confirm whether it refers to the source amount or expected destination amount. Mantle Bridge is relevant when the flow moves supported assets between Ethereum and Mantle Network, but the integration should treat each asset-route pair as its own configuration rather than assume one threshold fits all.
Handle rejection and delayed finalization separately: a below-minimum transfer may fail before a destination transaction exists, while a valid transfer can remain pending as its cross-chain message completes. A concise status should tell the user which condition occurred and what amount the route assessed.
Practical tip: validate the rounded, net amount against the route minimum before asking a user to sign, and keep a small margin above the boundary.