Mantle 백서

Mantle

원문

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 37쪽 중 1쪽

# Overviews Mantle Network is an EVM-compatible scaling solution for Ethereum built as a **ZK Validity Rollup**. All contracts and tools that run on Ethereum can be used on Mantle with minimal modification.\ Leveraging its modular architecture, Mantle separates execution, data availability, proof generation, and settlement into independent modules. Mantle now uses **ZK validity proofs** together with innovative data availability solutions to provide lower-cost and more accessible data availability while fully inheriting Ethereum’s security guarantees. Our protocol design philosophy aims to offer users a less costly and more user-friendly experience, provide developers with a simpler and more flexible development environment, and deliver a comprehensive set of infrastructure for the next wave of mass-adopted dApps. <table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden></th></tr></thead><tbody><tr><td><span data-gb-custom-inline data-tag="emoji" data-code="2328">⌨️</span> <strong>Developers</strong></td><td>Get started with Mantle development</td><td><a href="/network/for-developers/quick-access">Quick Access</a></td><td></td></tr><tr><td><span data-gb-custom-inline data-tag="emoji" data-code="1f4bb">💻</span> <strong>Node Operators</strong></td><td>Contribute to the network security</td><td><a href="/network/for-node-operators/network-roles">Network Roles</a></td><td></td></tr><tr><td><span data-gb-custom-inline data-tag="emoji" data-code="1f604">😄</span> <strong>Users</strong></td><td>Utilize webhooks to push real-time updates to your server</td><td><a href="/network/for-users/how-to-guides/connecting-wallet-to-mantle-network">Connecting Wallet to Mantle Network</a></td><td></td></tr></tbody></table> ## Key Features of Mantle Network <a href="#key-features-of-mantle-network" id="key-features-of-mantle-network"></a> * **Built as a Rollup** * Utilizes Ethereum validators and consensus protocols to significantly reduce gas fees, decrease latency, and increase throughput. Users can customize transaction confirmation requirements to provide near real-time confirmation latency with minimal security settings. * **Modular Architecture** * Unlike traditional [monolithic chains](/network/more/glossary#monolithic-chains) that execute transaction execution, consensus, settlement, and storage at the same network layer, Mantle separates these functions into individual modules as a [modular chain](/network/more/glossary#modular-chains). These include an EVM-compatible execution layer developed by Mantle for transaction execution, a consensus layer and settlement layer completed on Ethereum, and an external DA component. * **Secured by Ethereum** * All Rollup state transitions must pass through Ethereum’s verification process via **ZK validity proofs**, ensuring that only mathematically correct state roots are finalized. Once verified by the Ethereum settlement contract, the batch achieves immediate finality without requiring any challenge period. * **Modular Data Availability** * Independent DA modules, such as EigenDA technology. According to internal assessments, this translates to potential cost savings of more than **90%** compared to on-chain L1. # Updated Notices # Elysium Upgrade: Preparing Mantle Sepolia for Ethereum’s Glamsterdam Upgrade ### Overview Mantle Network will undergo the **Elysium Upgrade** on Sepolia.This upgrade ensures continued compatibility and stable operation across block derivation, batch submission, and cross-chain messaging as Ethereum L1 activates the **Glamsterdam hard fork**. It also introduces sequencer and preconfirmation improvements, RPC compatibility fixes, and updates to internal indexing services.**The current rollout retains Mantle’s existing Arsia/Osaka L2 execution rules. Amsterdam EVM behavior will not be activated on L2 as part of this upgrade.** ### Purpose of the Upgrade Ethereum Glamsterdam introduces changes to block headers, execution payloads, node interfaces, and gas accounting. Mantle’s rollup node, execution client, and cross-chain messaging components must be updated accordingly to maintain compatibility with Ethereum L1.The Elysium Upgrade focuses on three key objectives: 1. **Maintaining L1 compatibility** — Supporting Glamsterdam’s block data and interface changes to keep block derivation and batch submission operational. 2. **Ensuring reliable cross-chain messaging** — Adjusting relay gas budgets and improving the handling of large messages. 3. **Improving consistency across nodes and supporting services** — Refining sequencer and preconfirmation behavior, correcting RPC and deposit accounting issues, and adapting internal indexing services. ### What’s New in This Upgrade? #### **Ethereum L1 Glamsterdam Compatibility** Elysium updates Mantle’s rollup node and execution client to support: * L1 Amsterdam headers and compatible execution payloads. * Related Engine API and Beacon API changes. * Blob Parameter Only (BPO) schedules. * The new calldata gas floor for batch submission. The execution client is based on upstream **`go-ethereum v1.17.3`**, retaining Mantle-specific BVM\_ETH, fee accounting, preconfirmation, deposit, and fork behavior.While the codebase includes Amsterdam support for compatibility and testing, **this rollout does not activate Amsterdam EVM behavior on Mantle L2**. #### **Sequencer and Preconfirmation Improvements** The upgrade introduces eager next-block construction, reducing the interval between sealing one block and accepting transactions for the next.It also improves consistency across preconfirmation block size, timestamps, base fees, and next-block state, and includes L1 and operator fees when evaluating pending transactions. #### **Cross-Chain Messaging Updates** The release includes L1 and L2 **`CrossDomainMessenger 1.6.0`**, providing: * Relay gas budgets adapted for Amsterdam. * Safer handling of large cross-chain messages. * Supporting deployment and verification scripts. #### **RPC and Deposit Accounting Fixes** The upgrade includes the following compatibility and consistency fixes: * **`eth_simulateV1`** — Supports Mantle fee calculation. * **`eth_config`** — Improves compatibility with blobless OP Stack configurations and Amsterdam fork configurations. * **Deposit accounting** — Corrects gas accounting for failed BVM\_ETH deposits across the gas pool, receipts, cumulative gas, and block headers, along with deposit JSON encoding. * **Block header JSON fields** — Uses the canonical `blockAccessListHash` field for EIP-7928 block headers. This compatibility update does not activate EIP-7928 on Mantle L2 in the current rollout. #### **Internal Indexing Service Alignment** The upgrade also includes compatibility work for Mantle’s internal indexing services to support the updated node clients and related data processing flows. ### Impact Assessment **For users:** This upgrade primarily focuses on underlying compatibility and infrastructure improvements. Mantle L2 will continue to use the existing Arsia/Osaka execution rules.**For developers:** The upgrade does not introduce Amsterdam EVM execution behavior on Mantle L2. Developers using `eth_simulateV1`, `eth_config`, or integrations that rely on deposit receipts and block data should validate compatibility with the updated clients on Sepolia.**For node operators:** This is a **required upgrade**. All Mantle Sepolia node operators must update both the rollup node and execution client to **`v1.6.3`** before the configured Ethereum Sepolia Glamsterdam activation point. Component versions and full changes are available [here](/network/for-node-operators/network-updates/changelogs/mantle-v2-v1.6.3-elysium-upgrade). ### Summary The Elysium Upgrade is a critical preparation step for Mantle Network ahead of Ethereum’s Glamsterdam upgrade. After the upgrade, Mantle will: * Support the L1 data and interface changes required for Glamsterdam. * Improve cross-chain message relaying and large-message handling. * Strengthen consistency across sequencing, preconfirmations, and deposit accounting. * Support updated RPC behavior and internal indexing service compatibility. The Mantle team will continue to monitor network conditions and provide updates to the community before and after the upgrade. # Mantle Hoodi Testnet is Live Mantle's Hoodi testnet is now open. We switched the sequencer execution client from op-geth to a Mantle-adapted version of reth, building on the Arsia upgrade foundation. This gives Hoodi a production-ready, modular Rust execution base aligned with where the broader OP Stack ecosystem is heading. Connect now, deploy your contracts, and tell us what breaks. ### Why Hoodi We launched Hoodi to test Mantle's reth-based execution stack in a live network before wider rollout. Three things drove this: 1. **Validate the reth migration.** Hoodi runs on a Mantle-adapted reth — the same Rust execution client family powering op-reth, Base's base-reth-node, and BNB Chain's Reth-BSC. Optimism has set op-geth EOL at 2026-05-31. Hoodi lets us validate our reth integration before mainnet. 2. **Mirror the mainnet execution environment.** Developers need a testnet that reflects what mainnet will actually run. Hoodi's reth-based stack is that environment. 3. **Collect early signal.** Integration feedback, bug reports, and tooling compatibility data — we want all of it before broader rollout. Hoodi is the low-stakes place to send it. Hoodi is scoped specifically for reth execution validation. It complements Sepolia, which remains the primary environment for application and tooling development. ### Network Information <table data-header-hidden><thead><tr><th width="234.94921875"></th><th></th></tr></thead><tbody><tr><td>Parameter</td><td>Value</td></tr><tr><td>Network Name</td><td>Mantle Hoodi Testnet</td></tr><tr><td>Chain ID</td><td>50002</td></tr><tr><td>RPC Endpoint</td><td><code>https://rpc.hoodi.mantle.xyz</code></td></tr><tr><td>Block Explorer</td><td><a href="https://explorer.hoodi.mantle.xyz/">explorer.hoodi.mantle.xyz</a></td></tr><tr><td>Faucet</td><td><a href="https://faucet.mantle.xyz/">faucet.mantle.xyz</a></td></tr><tr><td>Bridge</td><td><a href="https://app.mantle.xyz/bridge?network=hoodi">https://app.mantle.xyz/bridge?network=hoodi</a></td></tr></tbody></table> ### What's Available * **Execution client.** The sequencer runs on a Mantle-adapted reth. Reth is a Rust-based, modular Ethereum execution client developed by Paradigm. Its staged sync pipeline, MDBX storage layer, REVM integration, and ExEx extension points give us a production-ready foundation — and a path to ongoing performance and maintainability improvements. * **EVM compatibility.** Hoodi supports the same EVM behavior as Mantle mainnet. Existing contracts and developer tooling — Hardhat, Foundry, ethers.js, viem — work without changes. Standard RPC methods are supported. * **Arsia baseline.** Hoodi's reth integration builds on the Arsia upgrade. The execution improvements from Arsia carry over, plus reth's operability and storage characteristics. ### Who Should Do What <table data-header-hidden><thead><tr><th width="260.6953125"></th><th></th></tr></thead><tbody><tr><td><strong>Audience</strong></td><td><strong>Action</strong></td></tr><tr><td><strong>Smart contract developers</strong></td><td>Connect to the Hoodi RPC, deploy contracts, test EVM behavior. Report any compatibility issues or unexpected RPC responses.</td></tr><tr><td><strong>Bridge and tooling teams</strong></td><td>Test cross-chain integration against the Hoodi bridge. Verify your tooling against the new execution client behavior.</td></tr><tr><td><strong>General testers</strong></td><td>Get test ETH from the faucet, send transactions, interact with deployed contracts. Report anything that behaves unexpectedly.</td></tr></tbody></table> ### Feedback & Support Report bugs and compatibility issues on our github repo. For questions, discussion, and general feedback, please refer to our Telegram and Discord. If something breaks, file a report. That's why Hoodi exists. ### Next Steps Hoodi will keep running. There is no planned shutdown date. We'll operate the network continuously while we collect stability data, compatibility reports, and performance metrics from real usage. Once we're confident the reth-based stack is stable and validated on Hoodi, we'll publish a timeline for migrating mainnet from op-geth to reth. Until then, Hoodi is the proving ground.<br> # Arsia Upgrade: Mantle's New Fee Model and OP Stack Alignment ### Overview Mantle Network will complete the **Arsia Upgrade** on Sepolia. This is a major network upgrade that replaces the legacy Bedrock-era fee model with a modern compression-based fee architecture, introduces an operator fee, and aligns Mantle with the latest OP Stack protocol versions (Canyon through Jovian). The upgrade brings significant improvements to fee accuracy, base fee dynamics, and block capacity management. ### Purpose of the Upgrade The Arsia Upgrade addresses several long-standing limitations in Mantle's fee model and protocol alignment: 1. **Accurate L1 data cost pricing** -- The legacy Bedrock model estimates L1 costs using raw byte counts and a flat overhead. Arsia replaces this with a compression-based model that uses FastLZ to estimate the actual DA size, resulting in more accurate and generally lower L1 data fees. 2. **Operator fee mechanism** -- A new fee component allows the network operator to charge a configurable fee for sequencing services, separate from L1 data costs and L2 execution costs. 3. **Dynamic EIP-1559 parameters** -- The base fee is no longer a fixed value. Arsia enables the sequencer to adjust EIP-1559 curve parameters (denominator, elasticity, minimum base fee) per block via the block's extra data field, enabling responsive fee markets. 4. **DA footprint-aware block sizing** -- A new DA footprint gas scalar converts each transaction's estimated DA size into a gas-equivalent value used for base fee targeting, preventing blocks from growing too large in data terms even when execution gas is low. 5. **OP Stack fork alignment** -- Arsia simultaneously activates the equivalent of Optimism's Canyon, Delta, Ecotone, Fjord, Granite, Holocene, Isthmus, and Jovian forks, bringing Mantle's protocol layer up to date with the latest OP Stack features. ### What's New in This Upgrade? #### **Compression-Based L1 Data Fee** The L1 rollup fee calculation is fundamentally redesigned: * Transaction data is compressed using **FastLZ**, and the compressed size is mapped to an estimated Brotli-compressed DA size via linear regression. * The new formula uses dual scalars -- `baseFeeScalar` for calldata pricing and `blobBaseFeeScalar` for blob fee pricing -- replacing the legacy flat `overhead + scalar` model. For the detailed formula, see [Fee Model Handbook](/network/system-information/fee-mechanism/fee-model-handbook-after-arsia). #### **Operator Fee** A new **operator fee** is introduced as a third fee component: * Calculated as: `gasUsed * operatorFeeScalar * 100 + operatorFeeConstant` * Collected by the new **`OperatorFeeVault`** contract. * Parameters are stored in the `L1Block` contract and configured through `SystemConfig` on L1. The total transaction fee is now: **L2 Execution Fee + L1 Data Fee + Operator Fee**. #### **Dynamic EIP-1559 Base Fee** * The block `extraData` field now carries EIP-1559 parameters: denominator, elasticity, and a minimum base fee. * The base fee is no longer fixed at 0.02 gwei. It adjusts dynamically based on network utilization. * The DA footprint (estimated data size per block) is used alongside execution gas for base fee targeting, preventing data-heavy blocks from being underpriced. #### **New RPC API** * **`eth_estimateTotalFee`** -- A new RPC method that returns the total estimated transaction cost, including all three fee components (L2 execution, L1 data, and operator fee). * **`eth_getBlockRange`** is deprecated and will be removed in a future upgrade. #### **Contract Upgrades** At the Arsia activation block, the following L2 contracts are upgraded via deposit transactions: * **L1Block** -- New storage layout with operator fee and DA footprint gas scalar fields. * **GasPriceOracle** -- Compression-based fee calculation and token ratio bounds enforcement. * **OperatorFeeVault** -- New contract for collecting operator fees. We also upgrade the L1 contract here: * **SystemConfig --** The SystemConfig contract on Ethereum L1 is upgraded to support Arsia's new fee parameters. * The upgrade adds owner-callable functions for configuring Arsia-specific parameters: `setGasConfigArsia` (dual base fee / blob fee scalars), `setOperatorFeeScalars`, `setEIP1559Params`, `setMinBaseFee`, and `setDAFootprintGasScalar`. These parameters are propagated to L2 via `ConfigUpdate` events and picked up by the L2 derivation pipeline. * The legacy `setGasConfig(overhead, scalar)` function is deprecated. #### **Node-Level Improvements** * **OP Stack baseline** -- The node stack is rebased on Optimism op-node v1.16.3. * **Blob encoding migration** -- Starting with Arsia, the batcher switches from Mantle's custom blob encoding (RLP-encoded frame array spanning multiple blobs) to the standard OP Stack blob format (one frame per blob). The derivation pipeline handles this transition with dual-mode decoding: it first attempts the legacy Mantle format, and upon failure, falls back to the standard format and switches permanently for subsequent blocks. ### Impact Assessment **For users**: Transaction fees will be calculated differently. The overall fee structure becomes more transparent with three clearly separated components. Users should see more predictable and generally fair pricing that reflects actual DA costs. **For developers**: The `estimateGas` RPC continues to work, but developers should adopt the new `eth_estimateTotalFee` API for more accurate total fee estimates. The fee model documentation has been updated -- see the [Fee Model Handbook here](/network/system-information/fee-mechanism/fee-model-handbook-after-arsia).&#x20; **For node operators**: This is a **required upgrade**. All operators of Mantle Network must update their node software before the fork activation time. See the Arsia changelog for component versions and upgrade instructions. ### Summary The Arsia Upgrade is a comprehensive protocol upgrade that modernizes Mantle's fee model and aligns the network with the latest OP Stack advances. After the upgrade, Mantle will: * Use compression-based L1 data fee pricing for more accurate cost estimation * Support a transparent three-component fee structure (L2 execution + L1 data + operator fee) * Feature a dynamic EIP-1559 base fee with DA-aware block targeting * Offer the `eth_estimateTotalFee` API for comprehensive fee estimation The Mantle team will continue to monitor network conditions and provide updates to the community before and after the upgrade. # Migration of Data Availability to Ethereum Blobs Mantle Network is initiating a strategic migration of its Data Availability (DA) layer from EigenDA to Ethereum Blobs (EIP-4844). This transition marks a significant milestone in our technical roadmap, effectively transitioning Mantle from a Validium architecture to a standard ZK Rollup. ### Key Drivers for Migration #### 1. Security Upgrade: From Validium to True Rollup The most critical driver for this migration is the qualitative leap in security. * **Current State (EigenDA):** Under L2Beat’s framework, Mantle is currently classified as “Others”. Security relies on the honesty of external EigenDA operators. While robust, this introduces a trusted dependency outside of Ethereum. * **Future State (Blobs):** By posting data directly to Ethereum Blobs, Mantle inherits the full cryptoeconomic security of Ethereum. As long a
프로젝트로 돌아가기