Mantle Bridge
This review rejects Mantle Network on the same grounds that led this registry to reject World Chain and Linea in this batch. Mantle Network has made real technical progress: an OP-Succinct upgrade in September 2025 replaced optimistic fraud-proof validation with SP1 zkVM validity proofs, and an April 2026 upgrade moved data availability to native Ethereum blob space. But L2Beat rates its exit window as ”None,” the same rating already used to reject Linea in this registry, because a 6-of-14 multisig can upgrade contracts at once, with no delay on any material contract except the token itself. State-root proposers are permissioned, not open, much like the permissioned-validator structures already rejected for Robinhood Chain and World Chain. The technical progress does not change the concentrated governance that this registry weighs in its judgment.
- State-root proposer verification becomes permissionless, removing the current whitelist requirement
- A minimum standing delay, even 24 to 72 hours, is introduced between MantleSecurityMultisig upgrade approval and execution
- L2Beat no longer rates Mantle’s exit window as ”None”
- Current withdrawal timing is independently confirmed against a live transaction rather than conflicting documentation
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-17.
The research file
Mechanism
Mantle Network is a rollup derived from the OP Stack. Two recent architecture changes matter: the OP-Succinct upgrade of 2025-09-16 replaced optimistic fraud-proof validation with SP1 zkVM validity proofs, and the Arsia upgrade of April 2026 moved data availability from EigenDA to native Ethereum blob space. Sources conflict on current withdrawal timing. Mantle’s own bridging documentation still describes a seven-day rollup challenge period, while independent reporting says the ZK upgrade cut withdrawals to roughly six hours. This review could not check the difference against a live transaction. That is a concern about the quality of the documentation, apart from the governance findings below.
Control and governance
L2Beat directly confirms that Mantle’s exit window is rated ”None,” the same as the already-rejected Linea. Most contracts can be upgraded at once by a 6-of-14 MantleSecurityMultisig; only the L1MantleToken itself has a one-day timelock. State-root proposers are permissioned and limited to a whitelist, much like the already-rejected Robinhood Chain and World Chain’s permissioned-validator structures. The sequencer is centralized, with a 12-hour force-inclusion fallback for censored transactions. L2Beat rates Mantle Stage 0, with five of eight requirements met and three unresolved for Stage 1. It flags instant contract upgrades as a CRITICAL risk, along with centralized-validator and permissioned-proposer risks. This is the same critical-risk pattern that led this registry to reject World Chain and Robinhood Chain in this batch.
Incident record
This review found no exploit of Mantle’s own bridge or core contracts. Mantle publicly clarified on 2025-04-15 that the Kelp DAO/LayerZero rsETH exploit already rejected in this registry’s `layerzero-v2` entry did not touch Mantle’s official bridge or core infrastructure, even though LayerZero-bridged rsETH circulated on Mantle and more than 20 other chains. It was a close call tied to a dependency, not a failure specific to Mantle.
Exit under stress
Whatever the current numeric withdrawal window proves to be, the key fact is the same one that led this registry to reject Linea. With zero delay on contract upgrades, there is no exit window if the 6-of-14 multisig approves a malicious or coerced change, no matter how fast withdrawals are through the normal path.
Comparison
Mantle is weaker than Base, Arbitrum, and Optimism, all approved with limits in this registry, on the same two grounds that already disqualified World Chain, Robinhood Chain, and Linea. Its validator or proposer set is permissioned rather than permissionless, and its upgrade path has no standing delay. L2Beat rates that path ”None,” just as it rates Linea’s. Mantle’s move to ZK validity proofs and Ethereum-blob data availability is a real technical improvement, but it does not change the concentrated governance that forms the basis for this rejection.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- L2Beat — Mantle · primary · accessed 2026-08-17
Supports: exit window: None, 6-of-14 MantleSecurityMultisig, permissioned proposer, Stage 0, critical risk flags - Mantle Network — bridging on Mantle mainnet · primary · accessed 2026-08-17
Supports: deposit and withdrawal flow - Coin Bureau — Mantle Network review 2026 · secondary · accessed 2026-08-17
Supports: OP-Succinct upgrade, Arsia DA migration, reported withdrawal timing - Cryptonews — Mantle Network stands resilient, core infrastructure unscathed by Kelp DAO breach · secondary · accessed 2026-08-17
Supports: Mantle statement distinguishing its bridge from the LayerZero exploit - Mantle Bridge FAQ · primary · accessed 2026-08-17
Supports: withdrawal FAQ
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| Ethereum | Approved | No freeze key | No sequencer, no upgrade key, no operator who can be compelled. Rule changes require social consensus. |