Use Manta Bridge for secure, auditable routes across the Manta Network ecosystem.
This guide explains route selection, finality & withdrawal windows, fees (L1/L2 gas + relayer/proof), min-received protection,
MEV-aware execution, KPIs, and an operations runbook.
Manta Bridge Overview: Models, Routing & Finality on Manta Network
Manta Bridge connects supported networks to and from the Manta Network stack. The route selector weighs gas on origin/destination,
any relayer/proof costs, available liquidity after arrival, and time-to-finality. The objective is the best effective outcome —
not just a headline quote — with clear steps and predictable settlement.
Core Components in Manta Bridge (Manta Network)
Route Selector: Chooses canonical paths; penalizes gas-heavy or slow-finality routes; surfaces ETA and cost breakdown.
Execution Kernel: Batches approvals + bridge calls; enforces strict minReceived; fails fast on adverse re-quotes.
Effective price: Include L1/L2 gas, relayer/proof fees, and optional pre/post-swap costs; measure by realized net.
Liquidity depth: If you plan to swap after arrival, check destination pools on Manta Network first.
Reliability: For size, split into tranches; verify settlement between stages; adapt to network load.
Note: When time is critical, prefer routes with faster finality even at a slightly higher relayer/proof cost.
For cost-sensitive flows, choose slower-but-cheaper routes if your SLA permits.
Security & Operational Safety with Manta Bridge
Settlement is non-custodial to your wallet. Treat every action like production deployment: verify official links, contracts, and amounts.
Manta Bridge reduces operational risk with guard rails, but wallet hygiene still determines safety.
Wallet & Allowance Hygiene on Manta Network
Prefer a hardware wallet for approvals/initiations; confirm spender and exact allowance on-device.
Approve only the minimum required; periodically revoke stale allowances.
Bookmark official Manta Bridge / Manta Network URLs; avoid search-ad impostors and unsolicited “support”.
Threat Model & MEV Mitigations (Manta Bridge)
Sandwich risk around swaps: Set conservative slippage; consider private/builder RPC; chunk large orders.
Impostor tokens: Verify addresses/decimals; never trust tickers/icons alone.
Volatile gas: During spikes, bump priority fee or wait for calmer windows; avoid resubmitting duplicates.
Choose origin/destination, token, amount. Review the quote (gas + relayer/proof + min received bound).
Approve once per token/chain, then execute. Finality/exit windows depend on the route and network conditions.
Optional Pre/Post Swaps on Manta Network
Swap before bridging to consolidate assets; or after to reach deeper liquidity on destination.
Track price impact & slippage; prefer venues with audited contracts and depth on Manta Network.
For DCA/limits (if supported by your UI), schedule execution post-finality only.
Execution KPIs for Manta Bridge
Metric
Target / Heuristic
Why it matters
Quoted → Realized Output
Δ ≤ 0.30–0.80%
Flags congestion, thin depth, or stale quotes.
Effective Price
≤ Quote × (1+0.30%)
Includes gas + proof/relayer + swap/partner fees.
Fail/Revert Rate
< 1%
Re-tune slippage, chunk size, or RPC if higher.
Time-to-Finality
Prefer faster routes for urgency
Select by urgency vs cost; set expectations.
Runbook: Reliable Results with Manta Bridge
Before You Start (Manta Network)
Hold native gas on both ends (origin/destination) for approvals and finalize steps.
Verify token addresses/decimals; fee-on-transfer tokens can affect minReceived.
Bridge a micro-amount; confirm arrival, then proceed in tranches for size.
Slippage & Gas Guidance — Manta Bridge
Deep stables/majors: 0.10–0.50% slippage.
Mid-caps/moderate depth: 0.50–1.50% depending on venue and volatility.
Illiquid: 1.50%+; split orders or pivot via deeper pairs after finality.
Troubleshooting — Common Issues on Manta Bridge
Pending too long: bump priority fee or switch RPC; avoid peak volatility; do not spam resubmits.
Reverted / insufficient output: refresh quotes, modestly widen slippage, or reduce size and retry.
Exit delay: monitor the route’s finality progress rather than broadcasting duplicates.
Tip: For large transfers on Manta Bridge, enforce minReceived, verify destination balance,
then continue with subsequent tranches on Manta Network.