Mantle 백서

Mantle

원문

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

s Ethereum’s consensus holds, Mantle’s data is guaranteed to be available. This closes the security loop: ZK proofs verify state correctness, and Blobs guarantee data transparency. #### 2. Economic Predictability & Stability With the successful completion of the Fusaka upgrade and the implementation of BPO2, Ethereum is progressively realizing its vision for industrial-scale data availability.The current network parameters—Target=14 and Max=21 blobs per block—represent a massive leap in throughput capacity compared to the Pectra era (Target=6, Max=9). This dramatic expansion in supply has fundamentally reshaped the fee market. We have observed that Blob pricing currently remains at a highly competitive baseline, creating a perfect window for migration. This environment allows Mantle to secure the uncompromised safety of Layer 1 without the historical cost penalty, offering a cost structure that is both predictable and sustainable for our high-performance network. #### 3. Engineering Alignment with OP Stack Migrating to Blobs allows Mantle to align more closely with the upstream OP Stack. * **Reduced Complexity:** Maintaining a custom integration for EigenDA required extensive modifications to the `op-batcher` and `op-node`. * **Native Compatibility:** Switching to Blobs enables us to utilize the native data submission logic of the OP Stack. This reduces technical debt, accelerates our ability to merge upstream updates, and minimizes the risk of bugs derived from custom adaptations. ### What This Means for the Ecosystem #### For Users * No action required * Improved withdrawal safety under Ethereum-native DA guarantees #### For Developers & Infrastructure Providers * No API or RPC changes * Improved compatibility with Ethereum tooling and rollup standards #### For Mantle Network * Classification as a **standard ZK Rollup** * Stronger alignment with L2Beat rollup security criteria * Clear path toward **Stage 1 decentralization milestones** *** This migration reflects our commitment to building the most secure and scalable financial infrastructure. By combining Ethereum-native DA with OP Succinct’s ZK proving system, Mantle continues to advance toward a secure, scalable, and Ethereum-aligned rollup architecture. # Limb Upgrade: Ensuring Mantle’s Compatibility with Fusaka ### Overview Mantle Network will complete the **Limb Upgrade** on Sepolia.\ This upgrade ensures full compatibility and stable operation as Ethereum approaches the **Fusaka hard fork**, which includes PeerDAS and the Osaka EVM changes.\ The upgrade will not affect normal user activity and will not modify the network’s economic model. ### Purpose of the Upgrade Fusaka is a major upcoming Ethereum release introducing deep protocol-level changes across the data availability pipeline, the EVM instruction set, and precompiled contracts. For example, **Peer Data Availability Sampling (PeerDAS)** will become a foundational component of Ethereum’s long-term scalability roadmap, and the newly introduced **CellProofs Blob** format will become the default structure for blob submissions. At the same time, the full set of **Osaka-era EVM behaviors** will be activated. To ensure that Mantle Network continues to operate safely after Fusaka activation, the Limb Upgrade focuses on three key objectives: 1. Aligning Mantle’s execution layer with Ethereum’s latest EVM semantics. 2. Ensuring the new blob submission and verification flow functions correctly within the rollup architecture. 3. Establishing forward compatibility with the PeerDAS-based data availability pathway. ### What’s New in This Upgrade? The Limb Upgrade primarily introduces **low-level compatibility updates**. While these changes do not alter developer-facing APIs or smart-contract execution semantics, they are critical for long-term stability. #### Osaka EVM Compatibility Mantle’s execution layer will fully support the **Osaka EVM**.\ This includes activation of all EVM behaviors shipped with Ethereum’s Osaka spec, such as: * New opcodes (e.g., **CLZ** from EIP-7939) * New precompiled contracts (**EIP-7883** and **EIP-7951**) * Gas schedule adjustments and EVM logic refinements #### Updated Blob Handling The upgrade introduces support for Ethereum’s Fusaka-era **CellProofs-based blob format**.\ Ethereum is migrating from the previous blob structure to a new format designed for PeerDAS sampling. Mantle’s batcher, node derivation pipeline, and Beacon RPC query logic have all been updated accordingly, ensuring that after Fusaka activation, Mantle can continue to reliably read and verify blob data from L1. #### ZKP Pipeline Alignment Changes to the blob structure and submission process also require updates in the ZKP pipeline (kona / succinct).\ The goal is to ensure that Mantle’s L2 Output proofs continue to be valid, robust, and compatible with the new data paths, while establishing a foundation for future optimizations in proof generation. ### Impact Assessment This upgrade has **no impact** on regular users, DApps, or on-chain asset operations.\ It does **not** introduce any modifications to the fee mechanism or protocol economics. For developers, all application-layer interfaces and contract environments remain fully unchanged — no migration or adaptation is required. Node operators are the primary group that must pay attention to the upgrade window. They must ensure that all relevant components are updated during the transition to maintain correct node synchronization and interaction with Ethereum L1. Further details are available [here](/network/for-node-operators/network-updates/changelogs/mantle-v2-v1.4.1-limb-upgrade-sepolia). ### Summary The Limb Upgrade is a critical preparation step for Mantle Network ahead of Ethereum’s Fusaka era.\ After the upgrade, Mantle will: * Support the new blob submission structure, enabling lower rollup costs * Benefit directly from PeerDAS improvements on Ethereum L1 * Achieve complete Osaka EVM compatibility The Mantle team will continue to monitor network conditions and provide updates to the community before and after the upgrade. # Mantle OP Succinct Mainnet Upgrade & Withdrawal Period Transition Mantle is excited to announce our upcoming mainnet upgrade to **OP Succinct**, scheduled to begin on **September 16, 2025**.This upgrade is a monumental step, transitioning Mantle into the largest ZK validity Layer 2 in the ecosystem. By integrating ZK proofs for state validation, we are enhancing security and fundamentally improving the user experience.During this upgrade, we will be deploying essential contract updates. The most significant impact on users will be a dramatic improvement to the Mantle Canonical Bridge withdrawal process.To ensure transparency and prevent confusion during this transition, please review how withdrawals will be handled. ## **The Key Change: From a 7-Day to a 12-Hour Withdrawal** Previously, as an Optimistic L2, Mantle required a 7-day "challenge period" for all withdrawals via the canonical bridge. This delay is the standard security mechanism for all Optimistic rollups, allowing time for network observers to challenge potentially fraudulent state transitions.With the move to ZK validity, the network’s state is confirmed by cryptographic proofs rather than relying on a challenge window. This allows us to **reduce the withdrawal finalization period from 7 days to just 1 2hours.**&#x48;owever, this change requires a specific transition period to safely finalize the old system and activate the new one. {% hint style="success" %} **Why do we choose 12 hours?** Security Rationale for the 12-Hour Challenge Period While a ZK-proof system theoretically allows for a much shorter challenge period, setting it to 12 hours is a deliberate security measure. This duration serves as a critical safety buffer for the official bridge. In an extreme security event, such as a hack, this window provides the team with the necessary time to respond and mitigate risks, thereby providing maximum protection for user assets. {% endhint %} ## **The Transition Timeline Explained** <figure><img src="https://3885809119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQliZlRNwHhmzesDU1Ksq%2Fuploads%2FQlAM95Fpj3vNhmRKUOQ6%2Fimage.png?alt=media&amp;token=f19dbcc5-5de8-45c5-a243-cb8e26847cc0" alt=""><figcaption></figcaption></figure> The upgrade involves a multi-stage rollout. In netshell, rationale for the 7-Day Waiting Period Prior to the ZK Proposer launch, L2 state outputs were submitted using a non-ZK method. According to the security model, these historical outputs must complete their original 7-day challenge period to guarantee their finality and security. Therefore, the parameter update will be executed 7 days after the ZK Proposer is live to ensure all data submitted via the non-ZK method has been securely finalized.Here is the precise schedule and what users initiating withdrawals should expect: 1. **Phase 1: ZK Proofs Begin (After Sep 16, 2025 \~15:00 UTC\*)** Starting on September 16, all new state roots on Mantle will be submitted and verified using ZK proofs. 2. **Phase 2: The Transition Window (Sep 16 – Sep 23)** During this one-week transition window, although new state roots are ZK-proven, the original 7-day challenge period logic will **remain active** in the bridge contracts. This is necessary to securely finalize any remaining state from the Optimistic system. 3. **Phase 3: The New Standard (After Sep 23, 2025 \~15:00 UTC\*)** On September 23, the final contract upgrade activates the new 12-hour withdrawal logic. This new, shorter finalization period will apply to **all pending and all new withdrawals** moving forward. *\*Note: 15:00 UTC (3:00 PM UTC) is used as the target activation time. Actual activation may vary slightly based on network conditions.* *** ## **Withdrawal Scenarios: What Will Happen to My Funds?** To make this clear, here are practical examples covering every scenario during the upgrade. **Scenario 1: Withdrawal initiated BEFORE the upgrade (e.g., Sep 14)** * **Status:** Your withdrawal is already in the challenge period before the Sep 16 upgrade begins. * **Result:** You must wait for the **full, original 7-day challenge period**. The new logic does not apply retroactively to withdrawals already finalized under the old Optimistic system. **Scenario 2: Withdrawal initiated DURING the transition (e.g., Sep 18)** This is the most critical scenario. You initiated your withdrawal *after* ZK proofs started, but *before* the 12-hour rule was activated. * **What you see (Sep 18 – Sep 23):** Your withdrawal will enter the legacy 7-day challenge period. The UI will show a 7-day countdown (e.g., "6 days remaining," "5 days remaining," etc.). * **What happens (On Sep 23, \~15:00 UTC):** The new 12-hour logic is applied to **all** pending withdrawals. Since your wait time (from Sep 18 to Sep 23) is already much longer than 12 hours, your withdrawal will become **immediately claimable** the moment the Sep 23 upgrade is finalized. **Scenario 3: Withdrawal initiated JUST BEFORE the final activation (e.g., Sep 23 at 14:00 UTC)** You initiate a withdrawal just one hour before the final upgrade activates. * **What you see (14:00 – 14:59 UTC):** The UI will temporarily show the legacy 7-day challenge period. * **What happens (After 15:00 UTC):** The new 12-hour rule activates. The system recalculates your requirement. Since you have already waited 1 hour (from 14:00 to 15:00), your withdrawal timer will automatically update to show only **11 hours remaining**. Thank you for your patience and support as we complete this landmark upgrade. We are thrilled to deliver the next generation of scaling with the security of ZK validity and a vastly superior bridge experience.<br> # Mantle Network Mainnet v2 Everest Upgrade After more than one year of stable operation of Mantle Tectonic, we proudly present the **Everest Upgrade**—a significant leap forward for the Mantle network. This upgrade not only strengthens our existing infrastructure but also prepares us fully for the upcoming **Ethereum Pectra Upgrade**, ensuring seamless compatibility with the Mantle network and laying a solid foundation for future development. As one of the core highlights of the Everest Upgrade, the official launch of **EigenDA** will introduce a revolutionary data availability solution to the network, significantly enhancing the efficiency of data management and security. ## Enhancements in Mantle v2 Everest Compared to Mantle v2 Tectonic <a href="#enhancements-in-mantle-v2-tectonic-compared-to-mantle-v1" id="enhancements-in-mantle-v2-tectonic-compared-to-mantle-v1"></a> ### EigenDA Integration Mantle has maintained deep collaboration with EigenDA. Before EigenDA's mainnet launch, Mantle used Mantle DA (a third-party DA Layer powered by EigenDA) as its DA Layer. Therefore, when EigenDA went live, we immediately completed the migration on testnet and, after production environment testing, finally migrated on Mantle mainnet. For detailed information about EigenDA, please check [here](broken://pages/n2tk77lxhcut6QDAf40l). ### L2 Adaptation for Ethereum Pectra Upgrade Ethereum is about to welcome the highly anticipated Pectra upgrade. As an Ethereum L2, Mantle immediately began adaptation work for the changes brought by the Pectra upgrade, including the new `RequestsHash` field in block headers from EIP-7685, and the new `SetCodeTx` transaction type introduced in EIP-7702. ### New Feature Introduction Since building on OP Stack Bedrock, Mantle has been committed to enhancing op-geth's functionality through extensibility development. In this upgrade, new RIP-7212 precompiled contract support was introduced, along with the addition of the `eth_getBlockReceipts` jsonRPC interface. ### MetaTX Feature Deprecation MetaTX, independently developed by Mantle, provided gas fee sponsorship functionality, aiming to minimize barriers for users entering the Mantle ecosystem. With the introduction of EIP-7702 in the Ethereum Pectra upgrade, Mantle will provide the same gas fee sponsorship functionality based on it, therefore MetaTX will no longer be supported.[​](https://docs-v2.mantle.xyz/intro/whats-new-in-mantle-v2#enhancements-in-mantle-v2-tectonic-compared-to-mantle-v1) [​](https://docs-v2.mantle.xyz/intro/whats-new-in-mantle-v2#distinctions-between-mantle-v2-tectonic-and-op-stack-bedrock) # EigenDA Migration for Mantle Sepolia {% hint style="info" %} This hardfork upgrade is currently only happening on the Mantle Sepolia test network. {% endhint %} Welcome to the upgrade guide for migrating your node and applications from v1.0.0 to v1.0.1. Below, we provide tailored instructions for different user roles to ensure a smooth upgrade process. ## What's New in This Upgrade?[​](https://docs-v2.mantle.xyz/intro/migration-guides-sepolia#whats-new-in-this-upgrade) <a href="#whats-new-in-this-upgrade" id="whats-new-in-this-upgrade"></a> In this hardfork upgrade we will include the following upgrades: * **Migrate Mantle DA to EigenDA** - With the launch of EigenDA, we will switch Mantle DA powered by EigenDA to EigenDA for a better and more stable DA service! * **Fix some bugs of MetaTX service** - MetaTX, as a gasless service for Mantle, was found to have a few bugs, which we've modified. ## For Node Operators[​](https://docs-v2.mantle.xyz/intro/migration-guides-sepolia#for-node-operators) <a href="#for-node-operators" id="for-node-operators"></a> **Node operators should restart their nodes using the new version of Mantle v2 Tectonic (v1.0.1).** Please follow the node running [tutorial](/network/for-node-operators/deployment-guides/testnet-v1.6.3/deploying-a-sepolia-rollup-verifier-replica-node-from-docker) we provide, which contains the running environment requirements and the corresponding steps. [Changelogs](/network/for-node-operators/network-updates/changelogs/mantle-v2-v1.0.2) corresponding to this hardfork upgrade is available, detailing changes and new features. Review these changelogs to understand post-upgrade alterations and optimizations. ## For Developers[​](https://docs-v2.mantle.xyz/intro/migration-guides-sepolia#for-developers) <a href="#for-developers" id="for-developers"></a> In this upgrade, we have addressed and optimized a series of bugs and issues that were occurring with the MetaTX service. These improvements are aimed at enhancing the overall stability and performance of MetaTX, ensuring a smoother and more reliable experience for developers utilizing this service. *** While upgrade operations may cause temporary inconvenience, we believe that with your support and cooperation, we can smoothly finish this upgrade. If you have any questions or need further assistance regarding to this upgrade, feel free to contact our support team. Happy upgrading! 🎉🎉🎉 # Mantle Network Mainnet v2 Tectonic Upgrade Guide Welcome to the upgrade guide for migrating your node and applications from Mantle Network Mainnet Alpha v1 (Mantle v1) to Mantle Network Mainnet v2 Tectonic (Mantle v2 Tectonic). Below, we provide tailored instructions for different user roles to ensure a smooth upgrade process. ## For Node Operators[​](https://docs-v2.mantle.xyz/intro/migration-guides#for-node-operators) <a href="#for-node-operators" id="for-node-operators"></a> **Node operators should restart their nodes using the new version of Mantle v2 Tectonic.** Please follow the node running [tutorial](/network/for-node-operators/deployment-guides/mainnet-v1.5.4/deploying-a-rollup-verifier-replica-node-from-docker) we provide, which contains the running environment requirements and the corresponding steps. [Changelogs](/network/for-node-operators/network-updates/changelogs/mantle-v2-v1.0.0) corresponding to Mantle v2 Tectonic versions are available, detailing changes and new features. Review these changelogs to understand post-upgrade alterations and optimizations. ## For Developers[​](https://docs-v2.mantle.xyz/intro/migration-guides#for-developers) <a href="#for-developers" id="for-developers"></a> **Developers should ensure your contracts adapt to new features and updates introduced in Mantle v2 Tectonic, such as** [**gas estimation**](/network/system-information/fee-mechanism/estimate-fees#why-we-need-to-use-estimategas)**.** Mantle v2 Tectonic supports multiple contract deployment tools, for more information please check [here](/network/for-developers/how-to-guides/how-to-deploy-smart-contracts). {% hint style="info" %} * Mantle v2 has modified and optimized fee mechanisms. When constructing transactions, remember to call the `estimateGas` interface to ensure your transactions execute smoothly and receive appropriate fees. More details [here](/network/system-information/fee-mechanism/estimate-fees). * Our Goerli testnet has been upgraded to Mantle v2 Tectonic. Developers are advised to check the status of your contracts on this testnet. If any issues arise, it's essential to address and fix them to avoid potential problems on the mainnet and redeploy your contracts. * Mantle v2 Tectonic introduces a new fee collection which will minimize your transaction fees, for information on optimizing gas fees, please check [here](/network/for-developers/optimize-your-transaction-fees). {% endhint %} ## For Users[​](https://docs-v2.mantle.xyz/intro/migration-guides#for-users) <a href="#for-users" id="for-users"></a> **Users should suspend the use of on-chain products related to Mantle Netork during the upgrade process to avoid assets loss.** For the new features of Mantle v2, please check [here](/network/introduction/whats-new-in-mantle-v2-arsia). #### Bridge Assets[​](https://docs-v2.mantle.xyz/intro/migration-guides#bridge-assets) <a href="#bridge-assets" id="bridge-assets"></a> During the upgrade process, we will suspend the use of the bridge, so after the upgrade, you may face the following issues: * If you ha
프로젝트로 돌아가기