Layer 2 blockchain · settles to Ethereum
Mantle ticker MNT
Summary
Rollup on Ethereum derived from the OP Stack. One permissioned sequencer orders transactions into L2 blocks, and a batcher compresses them and posts the data to Ethereum as blob transactions. Block ranges are re-derived from that blob data and re-executed in the SP1 zkVM, and a Succinct proposer submits the aggregated validity proof to the MantleSuccinctL2OutputOracle contract on Ethereum. Since September 2025 withdrawals can finalize 12 hours after a proven output instead of after a 7-day challenge window. The oracle keeps a fallback optimistic mode that accepts outputs without proofs; Mantle says that mode uses a 7-day challenge window, and L2BEAT says a 3-of-7 Mantle multisig can switch it on or off and change the finalization period. Block production uses no stake or work of its own. 234567825
Design
- System
- Layer 2 blockchainMantle Mainnet (chain ID 5000) is an OP Stack-derived rollup on Ethereum that has used zero-knowledge validity proofs (OP Succinct with the SP1 zkVM) since September 2025. Since the Arsia upgrade in April 2026 its transaction data goes to Ethereum blobs; before that it used EigenDA, which put it outside L2BEAT's rollup category. MNT, not ETH, is the gas asset; bridged ETH is a token on Mantle.
- Settles to
- EthereumBatch data is posted to Ethereum blobs, and block ranges are finalized when an SP1 validity proof is accepted by the MantleSuccinctL2OutputOracle on Ethereum. Mantle's September 2025 notice cut the withdrawal finalization period from 7 days to 12 hours. Forced transactions go through the OptimismPortal contract on Ethereum; Mantle's docs give a 24-hour sequencing window, while L2BEAT says up to 12 hours.
- Settlement family
- Ethereum / EVM
- Scarce resource
- Other
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- One sequencer run by Mantle. Mantle's node-operator docs say sequencer, proposer, batcher and data-availability roles are not open to outside operators; only replica (verifier) nodes are. L2BEAT says only whitelisted proposers can publish state roots on Ethereum.
- Fork choice
- No open L2 fork choice: the canonical chain is derived from batch data posted to Ethereum, where Ethereum's own fork choice and finality apply. Mantle's forced-inclusion page says the L2 chain reorganizes to include a transaction submitted on Ethereum if the sequencer has not published it within the sequencing window.
Qualifications
- Scarce resource · Not applicable. Mantle block production uses no stake or work of its own; the sequencer is operator-assigned and security comes from Ethereum plus validity proofs.
- Finality · Partial. A sequencer block is only the operator's promise. Data becomes public once its batch is in an Ethereum blob, and a block range is settled only after its validity proof is accepted on Ethereum; L2BEAT reports proven state updates arrive about once an hour on average. Withdrawals then wait out a 12-hour finalization period. Mantle publishes no maximum reorg depth.
- Withdrawal window · Contested. Mantle's September 2025 notice says withdrawals finalize in 12 hours. Its user FAQ still says withdrawals can take up to a week, and its bridge guide, a walkthrough written for the Sepolia testnet that says mainnet works the same way, describes about 30 minutes to prove plus 30 minutes to claim.
- Data availability · Contested. Current evidence points to Ethereum blobs: Mantle's architecture and transaction-lifecycle pages, its migration notice and L2BEAT all say so. Its overview and its Mantle-versus-OP-Stack page still describe EigenDA, and the switch date is unclear: L2BEAT dates it 16 April 2026 and labels it the Arsia upgrade, Mantle's release sets the Arsia activation for 22 April 2026, and the migration notice is undated.
- Forced inclusion delay · Contested. Mantle's forced-inclusion page gives a 24-hour sequencing window; L2BEAT says forced transactions can be delayed up to 12 hours.
- Proof fallback · Partial. Mantle says the output oracle can fall back to the standard optimistic proposer route with a 7-day challenge window if the proving pipeline fails. L2BEAT says a 3-of-7 Mantle engineering multisig can switch that proof-less mode on or off, change the finalization period, delete proposed state roots and pause withdrawals, and names it as the challenger in that mode.
Tradeoffs
- Emphasizes
- Scalability and Security
- Gives up
- Decentralized operation and upgrade safety: one Mantle-run sequencer orders all transactions and only whitelisted proposers post state roots. Mantle's contract list names a Mantle security multisig as owner of the contract that upgrades its Ethereum contracts; L2BEAT reports that this 6-of-14 multisig can upgrade them with no delay, that a separate 3-of-7 engineering multisig can turn off proof checking, delete proposed state roots and pause withdrawals, and rates Mantle Stage 0. Withdrawals to Ethereum also wait at least 12 hours.The security emphasis refers to validity proofs checked on Ethereum and, since April 2026, data posted to Ethereum. It holds only while the SP1 prover and verifier are sound, the optimistic fallback mode is not in use, and the multisig key holders act honestly. The Ethereum data part of each fee is converted to MNT with a ratio set by Mantle's operator.
- Full node at home
- Demanding 1623Mantle's mainnet node guide recommends 8 or more CPU cores, at least 16 GB RAM, a 4 TB or larger disk (it says HDD works for now, SSD is better) and at least 10 Mb/s download; its size figures (about 75 GB full, 1.5 TB archive) date from December 2023. A node needs the operator's own Ethereum RPC and reads blob data from an Ethereum consensus-layer (beacon) endpoint; the Limb release moved that lookup to the newer beacon blob query.
- Throughput claims
- No classified figure recorded
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Unknown | A protocol-level trust-minimized swap mechanism on Mantle was not reviewed; EVM contracts could implement hash-locked swaps, but none was verified. |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Built into the protocolLimited scope | Mantle's protocol produces what a light client checks: each block range is finalized on Ethereum only after its validity proof is verified there, so someone following Ethereum can check proven Mantle outputs without re-executing the chain. Scope is limited: this does not hold while the fallback mode that accepts outputs without proofs is switched on, and no dedicated Mantle light-client software was reviewed. 3425 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel layer anchored to Mantle was reviewed. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Mantle runs EVM smart contracts and says contracts and tools that run on Ethereum work with minimal changes; some opcodes differ (for example the block coinbase is a fee vault and the randomness value is set by the sequencer). 113 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under this row's current definition. |
| Rollups | Unknown | Chains that settle to Mantle were not reviewed. Mantle itself is a rollup on Ethereum; its settlement is described in the mechanism and Ethereum dependency notes. |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | Established in the ecosystemMerchant Moe | Merchant Moe describes itself as a DEX built for Mantle with Liquidity Book (binned liquidity) and classic AMM pools. Liquidity depth was not measured and other venues were not reviewed. 26 |
| Issuer-native stablecoins | Established in the ecosystemUSDG (Paxos) | Paxos lists a Mantle token address for its USDG stablecoin, which reaches Mantle through LayerZero's omnichain token standard. USDT0 also has a Mantle contract, but it is minted by the USDT0 service against USDT locked on Ethereum and Tether's supported-protocols page does not list Mantle, so it is not counted as issuer-native. Circle's native USDC list does not include Mantle. Usage was not measured. 2728293940 |
| Algorithmic stablecoins | Unknown | Ethena's key-addresses page lists Mantle among the chains where its tokens, including the dollar token USDe, are deployed. How USDe is backed, whether it belongs in the algorithmic or hybrid class, and its usage on Mantle were not reviewed, and no other such stablecoin was checked. 33 |
| Bridges | Native to the protocolMantle canonical bridge (standard bridge and OptimismPortal contracts) | MNT, ETH and ERC-20 tokens move between Ethereum and Mantle through protocol contracts: tokens are locked on Ethereum and minted on Mantle, then burned and released on withdrawal. Starting a withdrawal costs MNT on Mantle, and claiming it on Ethereum costs gas in ETH. Third-party bridges were not reviewed. Risk: Withdrawals depend on the SP1 proof system, a 12-hour finalization period and whitelisted proposers; L2BEAT says withdrawals freeze if those proposers stop, and that a 3-of-7 multisig can pause withdrawals or switch the oracle to a mode without proofs. L2BEAT also reports the contracts can be upgraded instantly by a 6-of-14 multisig with no exit window, and Mantle's docs disagree on withdrawal times. 481718192025 |
| Block explorers | ThinMantlescan | Mantle's docs name only Mantlescan, built by the Etherscan team, as the mainnet explorer, and Mantle's own explorer address now redirects to it. No second mainnet explorer was verified. Explorer indexes are not canonical consensus. 1530 |
| Hardware wallets | Established in the ecosystemLedger (lower confidence), Trezor Safe 3, 5 and 7 (through MetaMask or Rabby) | See custody rows: Ledger Wallet code includes the Mantle network and Ledger's templated Mantle page suggests it is switched on (lower confidence); Trezor lists the Mantle network, but Trezor Suite does not include it, so Trezor use goes through MetaMask or Rabby. 31323438 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Native supportSame as native: Unknown | Can: Add a Mantle account in Ledger Live (now Ledger Wallet), per Ledger's Mantle coin pageLower confidence. Ledger Wallet's code includes a Mantle network behind a feature switch that is off by default, and the remote setting that can switch it on could not be read. Ledger's Mantle page is a templated coin page that names neither the Mantle network nor a device app, so it may cover only MNT on Ethereum; it is taken as the sign that the switch is on. 3234353637 |
| Trezor | Through an intermediaryMetaMask or Rabby (third-party wallet apps named by Trezor)Same as native: Unknown | Can: Use MNT and other assets on the Mantle network with a Trezor Safe 3, Safe 5 or Safe 7 through MetaMask or Rabby; Trezor's Mantle page lists the Mantle network Can: Hold MNT on Ethereum in Trezor Suite Cannot: Manage Mantle network accounts in Trezor Suite itself: Suite's current network list does not include MantleTrezor's Mantle page lists Mantle and Ethereum and names Trezor Suite, MetaMask and Rabby without tying them to networks. Because Trezor Suite's network code has no Mantle entry, Suite handles MNT only on Ethereum and the Mantle network goes through a third-party wallet. Older models and contract interactions were not reviewed. 3138 |
Public data
iKnow Blockchain has no public-data lookups for Mantle yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Mantle released node version 1.6.3 (Elysium) to stay compatible with Ethereum's Glamsterdam upgrade
Mantle published node release 1.6.3, named Elysium, so that block derivation, batch posting and cross-chain messaging keep working when Ethereum activates its Glamsterdam upgrade. The Mantle chain itself stays on its existing Arsia and Osaka rules; Ethereum's new Amsterdam execution behaviour is not switched on for Mantle in this release. It also ships version 1.6.0 of the cross-domain messenger contracts on both chains and changes how the sequencer prepares the next block.
- Implementation:released as op-geth and op-node 1.6.3
- Release:1.6.3 Elysium
- Activation:tied to Ethereum's Glamsterdam activation; date not stated in the release
-
Mantle scheduled the Arsia mainnet upgrade: new fee model, OP Stack alignment and Ethereum-only data
Mantle's v1.5.4 release scheduled the Arsia upgrade for Mantle Mainnet on 22 April 2026 at 07:00 UTC. Arsia replaced the fee model with an execution fee, an Ethereum data fee and a new operator fee, made the base fee dynamic, and activated the equivalent of eight upstream Optimism upgrades at once, bringing in features such as span batches and Brotli compression. L2BEAT records that Mantle's transaction data has gone only to Ethereum since this period, with the EigenDA path removed.
- Implementation:released as v1.5.4 with a CertiK audit report
- Release:v1.5.4 Mainnet Arsia
- Activation:scheduled for 2026-04-22 07:00 UTC; Mantle's September 2026 release describes the chain as running on Arsia rules
Sources: Mantle (GitHub) — v1.5.4 Mainnet Arsia (external site) · Mantle Network Documentation — What's New in Mantle v2 Arsia (external site) · Mantle Network Documentation — Migration of Data Availability to Ethereum Blobs (external site) · L2BEAT — Mantle (external site) · Mantle (GitHub) — 1.6.3 Elysium (external site)
-
Mantle released the Limb upgrade to support Ethereum's Fusaka changes
Mantle's 1.4.2 release scheduled the Limb upgrade for Mantle Mainnet on 14 January 2026 at 07:00 UTC. Limb brought Ethereum's Osaka execution changes to Mantle, such as the new CLZ opcode and precompile changes, and updated the batcher, node and proof pipeline for the blob format Ethereum uses after Fusaka. Mantle said it did not change fees and had no impact on ordinary users.
- Implementation:released as 1.4.2
- Release:1.4.2 Mainnet Limb
- Activation:scheduled for 2026-01-14 07:00 UTC; Mantle's September 2026 release describes the chain as running on Osaka rules
Sources: Mantle (GitHub) — 1.4.2 Mainnet Limb (external site) · Mantle Network Documentation — Limb Upgrade: Ensuring Mantle's Compatibility with Fusaka (external site) · Mantle (GitHub) — 1.6.3 Elysium (external site)
Topics your AI can explain
Your AI can explain these topics for Mantle through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Mantle's contract list names a Mantle security multisig as owner of the upgrade contract, but its threshold (6 of 14), the lack of any upgrade delay and the powers of a separate 3-of-7 engineering multisig come only from L2BEAT; the signers were not identified.
- The legal entity that runs the Mantle sequencer, and who operates the proving network Mantle's docs call the Op-Succinct prove network, were not sourced.
- Mantle's docs disagree on withdrawal time (12 hours in the September 2025 notice, up to a week in the user FAQ, about an hour in a bridge walkthrough written for the Sepolia testnet).
- Mantle's docs (24 hours) and L2BEAT (up to 12 hours) disagree on how long a forced transaction can be delayed.
- The date Mantle stopped using EigenDA is unclear: L2BEAT says 16 April 2026, the Arsia activation was 22 April 2026, and Mantle's migration notice is undated; two Mantle pages still describe EigenDA.
- No typical time from transaction to proof-verified settlement on Ethereum, and no block interval, was found in the Mantle docs reviewed; the hourly figure for proven state updates is L2BEAT's average.
- A read-only contract check on 27 September 2026 found the fallback mode without proofs switched off, but whether it has ever been switched on was not reviewed.
- Node sizing figures date from December 2023; requirements for the planned Reth-based node were not published in the pages reviewed.
- Ledger's Mantle page does not say whether the Mantle network or only MNT on Ethereum is supported, or which device app signs, and Ledger's full supported-assets list could not be checked; the native Ledger rating rests on that templated page plus a Mantle network behind a default-off switch in Ledger Wallet code, so it is lower confidence.
- Trezor coverage of older models and of contract interactions on Mantle was not reviewed; the Trezor rating rests on Trezor Suite's network code, which has no Mantle entry.
- Third-party bridges were not verified, including Mantle's own cross-chain portal; a reported 2026 switch of that portal from LayerZero to Chainlink CCIP was not checked against a primary page.
- DEX liquidity depth and venues other than Merchant Moe were not reviewed.
- Reserves, redemption terms and usage of USDT0 and USDG on Mantle were not reviewed; USDC on Mantle is not on Circle's native list and its issuer route was not checked.
- Atomic swaps, reversible transfers and recovery, channels and chains settling to Mantle were not reviewed, and USDe's backing and usage on Mantle were not reviewed.
- Sequencer outage history was not reviewed.
- Only one mainnet block explorer was verified.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Overviews (external site)
- Architecture (external site)
- Transaction Lifecycle (external site)
- zk Validity Proof (external site)
- SP1 Workflow (external site)
- Forced Transaction Inclusion (external site)
- Network Roles (external site)
- Mantle OP Succinct Mainnet Upgrade & Withdrawal Period Transition (external site)
- Migration of Data Availability to Ethereum Blobs (external site)
- What's New in Mantle v2 Arsia (external site)
- Fee Model Handbook (After Arsia) (external site)
- Fee Mechanism (external site)
- The Differences between Mantle, OP Stack, and Ethereum (external site)
- Bridging ETH with the Mantle SDK (external site)
- Quick Access (external site)
- Deploying a Rollup Verifier/Replica Node From Docker (Mainnet v1.5.4) (external site)
- FAQs (for users) (external site)
- Using Mantle Bridge (external site)
- Moving Assets and Data (external site)
- Key L1 Contract Address (external site)
- Roadmap (external site)
- Tokenomics (external site)
- 1.4.2 Mainnet Limb (external site)
- v1.5.4 Mainnet Arsia (external site)
- Mantle (external site)
- Merchant Moe documentation (external site)
- Deployments (external site)
- USDG mainnet addresses (external site)
- USDC Contract Addresses (external site)
- Mantle Mainnet Network (MNT) Blockchain Explorer (external site)
- Safe & secure Mantle wallet (external site)
- Mantle Wallet (external site)
- Key Addresses (external site)
- ledger-live: coin-module loaders (list of networks Ledger Wallet can add) (external site)
- ledger-live: currencyMantle feature switch (external site)
- ledger-live: feature-flag defaults (a switch declared with no value is off) (external site)
- ledger-live: useCurrenciesUnderFeatureFlag (hides networks whose feature switch is off) (external site)
- trezor-suite: Ethereum-style network configuration (develop branch) (external site)
- USDT0 documentation overview (external site)
- Supported Protocols (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding