Mantle Approved Up to 5,000 ETH for Bridge Liquidity

Mantle governance approved up to 5,000 ETH and $10 million in USDx for third-party bridge liquidity on Sept. 12, 2023, under proposal MIP-26. The authorization created room for treasury assets to support bridge services; it did not specify that the full amount would be deployed or reserved for Mantle’s canonical bridge.

How can treasury ETH help bridge withdrawals?

Treasury ETH can let a third-party bridge pay a user on Ethereum before Mantle’s own withdrawal settlement is complete. The provider uses ETH already available on the destination chain, then settles or replenishes its position later, so the user trades waiting time for the provider’s fee and liquidity terms.

That differs from the canonical route, where a withdrawal must pass through Mantle’s settlement process before the user claims funds on Ethereum. For the mechanics and trade-offs of Mantle Bridge, the key distinction is settlement-backed withdrawal versus an earlier payout from a liquidity provider.

MIP-26 grouped bridge support among several treasury strategies and authorized the Economics Committee to work with service providers on deployment. A liquidity route could use ETH inventory to:

• Pay withdrawals on Ethereum while protocol settlement is pending.
• Let providers serve users without waiting for each individual withdrawal to finish.
• Rebalance destination-chain inventory as completed transfers settle.

The trade-off is that faster payment depends on available pool liquidity and provider operations. A route can quote a price, but a large withdrawal may exceed its available ETH or incur greater fees; the canonical process and a liquidity route therefore have different wait, capacity and contract risks.

Does the authorization shorten the canonical withdrawal?

No; the MIP-26 allowance concerns third-party bridge liquidity and does not itself change the canonical bridge’s settlement rules. Treasury ETH supplied to a separate provider can fund an earlier payout, but it does not make that payout a completed canonical withdrawal.

Users comparing routes should check the amount that will arrive, the provider’s available liquidity, fees and the contract handling the transfer. A liquidity route can suit someone who values faster access and accepts those costs; the canonical route avoids depending on a provider’s prefunded pool, while requiring the user to wait for settlement and claim.

What does the MIP-26 cap confirm?

MIP-26 set a maximum allowance, not a report of assets actually deployed. ChainCatcher’s account of the approved proposal says the bridge allocation was capped at 10 million USDx and 5,000 ETH, and notes that allocations could overlap and might take time to reach their limits.

That distinction matters when reading treasury figures: an authorization is permission to deploy within a ceiling, not evidence of current bridge reserves or guaranteed withdrawal capacity. The next useful confirmation would be a treasury or provider disclosure identifying any deployment, the route it supports and the amount still available; the approval alone does not establish those details.