bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 37쪽 중 3쪽
ve already applied to withdraw your assets on the mainnet and have completed the 7-days challenge period before the upgrade, please withdraw as soon as possible.
* If you haven't withdrawn your assets before the upgrade (no matter if you have completed your challenge period), you will need to prove your withdraw request after the upgrade and then wait for another 7 days.
{% hint style="info" %}
* In Mantle v2 Tectonic, if you need to withdraw your assets via bridge, we have introduced a new two-step withdrawal process. Before entering the 7-days challenge period, you will also need to perform the "prove" operation. For more details, please refer to [this](/network/for-users/how-to-guides/using-mantle-bridge#withdraw-mnt).
* If you want to experience the ultimate trading experience and low transaction fees on Mantle v2 Tectonic, please configure your wallet, for more information please check [here](/network/for-users/how-to-guides/connecting-wallet-to-mantle-network)!
{% endhint %}
While upgrade operations may cause temporary inconvenience, we believe that with your support and cooperation, we can smoothly transition from Mantle v1 to v2.
If you have any questions or need further assistance regarding Mantle v2 Tectonic, feel free to contact our support team.
Happy upgrading! 🎉🎉🎉
# What's New in Mantle v2 Arsia
The **Arsia Upgrade** is a major release that overhauls the fee model, aligns with the latest OP Stack protocol versions, and introduces DA-aware block management.
### Key Changes
#### **Modular Three-Component Fee Model**
The legacy fee model is replaced by a **transparent, modular fee model** where each cost component is independently calculated:
```
TotalFee = L2ExecutionFee + L1DataFee + OperatorFee
```
* **L2 Execution Fee** — Reflects pure EVM execution cost only. The legacy `tokenRatio` multiplier is removed, and `eth_estimateGas` returns a stable value unaffected by L1 fee market conditions.
* **L1 Data Fee** — Separated from gas consumption and deducted directly from the sender's balance. Uses compression-based estimation for more accurate and generally lower fees.
* **Operator Fee** — A new component providing node operators with a transparent revenue stream, collected by the new `OperatorFeeVault` predeploy.
For the full formula breakdown, see the [Fee Model Handbook](/network/system-information/fee-mechanism/fee-model-handbook-after-arsia).
#### **Dynamic EIP-1559 Base Fee**
Before Arsia, the L2 base fee was effectively static. Arsia restores a **full dynamic EIP-1559 fee market** — the base fee adjusts based on block gas usage, with a configurable minimum floor and explicit priority fee support.
#### **DA Footprint-Aware Block Management**
Each transaction's estimated DA size is converted into a **gas-equivalent DA footprint**, which feeds into the EIP-1559 base fee calculation. This ensures data-heavy blocks are priced accordingly, even when execution gas usage is low.
#### **OP Stack Fork Alignment**
Arsia simultaneously activates the equivalent of **eight upstream Optimism forks** (Canyon through Jovian) at a single timestamp, rebased on **Optimism op-node v1.16.3**. Key capabilities include span batches, Brotli compression, dual-scalar L1 fee model, FastLZ-based fee estimation, operator fee support, and DA footprint gas scalar.
#### **New RPC: `eth_estimateTotalFee`**
A new RPC endpoint returns the **total estimated transaction cost** including all three fee components. The corresponding `estimateTotalFee` method is also available in the Mantle-Viem SDK.
### **Contract Upgrades**
At the Arsia activation block, the following contracts are upgraded:
* **L1Block** — New fields for operator fee and DA footprint parameters.
* **GasPriceOracle** — Rewritten with compression-based L1 fee and operator fee calculation.
* **OperatorFeeVault** — New predeploy at `0x420000000000000000000000000000000000001b`.
* **SystemConfig** (L1) — New owner-callable functions for configuring Arsia-era fee parameters.
### Impact
**For users**: Fees are now transparently decomposed into three components. Pricing is more predictable, with L2 gas estimates stable regardless of L1 fee market volatility.
**For developers**: Adopt `eth_estimateTotalFee` or the Mantle-Viem SDK's `estimateTotalFee` for accurate total fee estimation. See the [Fee Model Handbook](/network/system-information/fee-mechanism/fee-model-handbook-after-arsia) for details.
**For node operators**: This is a **mandatory upgrade**. See the [Arsia changelog](/network/for-node-operators/network-updates/changelogs/mantle-v2-v1.5.4-arsia-upgrade) for upgrade instructions.
# Architecture
## Architecture Overviews[](https://docs-v2.mantle.xyz/intro/system-components/architecture#architecture-overviews) <a href="#architecture-overviews" id="architecture-overviews"></a>
<figure><img src="https://3885809119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQliZlRNwHhmzesDU1Ksq%2Fuploads%2FFYPlHUa4uy0zXD5u0SLP%2Fimage.png?alt=media&token=fd249467-eff3-479e-8bb4-53800c38267e" alt=""><figcaption></figcaption></figure>
This diagram illustrates how different network modules interact in Mantle v2 Skadi after the upgrade to **ZK Validity Proofs**. It shows how the execution layer, ZK proving module, and Ethereum DA (blobs) collaborate to process transactions, store rollup data, generate validity proofs, and publish verified state updates to Ethereum L1.
Let's review the end-to-end transaction processing pipeline to understand how each module participates in Mantle’s architecture.
1. Users send signed transactions to Mantle through RPC nodes, which forward them to the sequencer for processing.
2. The sequencer orders incoming transactions and produces Rollup blocks. The `op-batcher` periodically collects Rollup blocks, encodes and compresses the rollup data, and submits it to Ethereum L1 using EIP-4844 blob-carrying transactions. The corresponding blob commitments are posted on-chain and serve as the canonical data reference for data availability and subsequent ZK validity proving.
3. The **`Mantle-Succinct-Proposer`** periodically submits Mantle’s **ZK validity proofs** to the `MantleSuccinctL2OutputOracle` contract on Ethereum L1.
4. Rollup transaction data is stored on Ethereum L1 and acts as the public data source for ZK proving.
{% hint style="info" %}
If you would like to learn more about on-chain and off-chain design in the Mantle Network, check out the [**on-chain system**](/network/system-information/on-chain-system) and [**off-chain system**](/network/system-information/off-chain-system) pages!
{% endhint %}
## Transaction Pool in Mantle[](https://docs-v2.mantle.xyz/devs/concepts/tx-lifecycle#transaction-pool-in-mantle) <a href="#transaction-pool-in-mantle" id="transaction-pool-in-mantle"></a>
In Mantle v2, a transaction pool structure similar to Ethereum's mempool is introduced for the temporary storage of transactions until they are included in a block. The introduction of the transaction pool in Rollup is aimed at improving transaction packing. With Mantle v2 Tectonic's support for [EIP-1559 transaction types](/network/more/glossary#eip-1559-transaction), users can control the transaction packing speed by manipulating the priority fee in transactions. The transaction pool is used to temporarily store those unpacked transactions.
However, the introduction of the transaction pool also brings certain challenges, such as the impact of Miner Extractable Value (MEV). Therefore, in Mantle v2 Tectonic, the tx pool is designed to be private. If you want to submit a transaction, you need to configure [`op-geth`](/network/system-information/off-chain-system/node-introduction#op-geth) to send the transaction to the sequencer. The sequencer will then process transactions in the transaction pool in the order of their base fee and priority fee.
# Transaction Lifecycle
## L2 -> L1 Workflow[](https://docs-v2.mantle.xyz/devs/concepts/tx-lifecycle#l2---l1-workflow) <a href="#l2---l1-workflow" id="l2---l1-workflow"></a>
### 1. The Initiation[](https://docs-v2.mantle.xyz/devs/concepts/tx-lifecycle#1-the-initiation) <a href="#id-1-the-initiation" id="id-1-the-initiation"></a>
Wallet users, dApps, or some scripts may wish to utilize a blockchain-based system to transfer funds or execute tasks.
* For users, they have connected to Mantle network by adding the sequencer node's RPC endpoint to their wallet.
* On the other hand, dApps have integrated the [Mantle SDK](https://sdk.mantle.xyz/index.html) and instantiated it to communicate with Mantle network. They are ready to send requests containing the recipient's address and the amount they want to transfer.
As with any other service, this operation requires payment. It is not just for the transfer itself, but also for maintaining a permanent, immutable public record that anyone can verify. Their wallet or dApp must ensure there is a sufficient balance to execute this operation.
* For wallets, things are simpler; as it is easier to calculate the required fee.
* dApps need to do more detailed calculations; for more information, please refer to this [section](/network/system-information/fee-mechanism).
They use the tools at hand to compose a request, sign it using their private keys, and send it to Mantle Network where a sequencer is ready to process it. This is where the transaction first enters Mantle. More details [here](/network/system-information/off-chain-system/node-introduction#sequencer).
### 2. The Handling[](https://docs-v2.mantle.xyz/devs/concepts/tx-lifecycle#2-the-handling) <a href="#id-2-the-handling" id="id-2-the-handling"></a>
The transaction triggers the standard state verification process, executed by the Ethereum Virtual Machine (EVM) software ([`op-geth`](/network/system-information/off-chain-system/node-introduction#op-geth)) running on these nodes. This is to ensure that the transaction is fundamentally valid, the necessary fees have been paid, and nothing exceptional has occurred. 
After block execution, Mantle enters the **batching → DA → proving → L1 finalization** pipeline.
{% hint style="info" %}
It's important to note that state submission doesn't need to be executed after every transaction, but can be chosen to be submitted after a tx-batch.
{% endhint %}
### 3. The Storage[](https://docs-v2.mantle.xyz/devs/concepts/tx-lifecycle#3-the-storage) <a href="#id-3-the-storage" id="id-3-the-storage"></a>
Mantle follows the standard OP Stack data availability model by publishing rollup data to Ethereum L1 using EIP-4844 blob-carrying transactions.
The `op-batcher` periodically aggregates executed Rollup blocks, encodes and compresses the rollup data, and submits it to Ethereum as blobs. The corresponding blob commitments are recorded on-chain and serve as the canonical reference for data availability.
Blobs provide temporary but sufficient data availability guarantees for rollup verification, while significantly reducing L1 data costs compared to calldata. Full nodes and provers can retrieve the blob data from the Ethereum data availability layer during the blob retention window to reconstruct Rollup state transitions. 
### 4. The Proving
After data batches are published to Ethereum L1 as blobs, Mantle’s proving system runs independently to provide cryptographic validity guarantees for Rollup state transitions.
This process is coordinated by the Mantle Succinct Proposer, which monitors Rollup block progression and determines when new validity proofs should be generated.
The proving system retrieves the required rollup data from Ethereum blobs, reconstructs the corresponding Rollup state transitions, and generates ZK validity proofs through Mantle’s proving pipeline. These proofs attest that all included Rollup blocks were executed correctly according to EVM rules.
Once a proof is ready, the Succinct Proposer submits it—together with the associated state root—to the `MantleSuccinctL2OutputOracle` contract on Ethereum. After on-chain verification, the proven block range becomes finalized without the need for a challenge period.
# On-Chain System
# Contract Introduction
Mantle Network's on-chain module contains a series of smart contracts that run on the blockchain to ensure decentralized and reliable execution. These contracts are responsible for handling the logic of various dApps interacting with the blockchain, as well as the interaction of the off-chain system with the on-chain system, including asset transfers, asset swaps, and so on.
## Contract Explained <a href="#l1crossdomainmessengerproxy" id="l1crossdomainmessengerproxy"></a>
### L1CrossDomainMessengerProxy[](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#l1crossdomainmessengerproxy) <a href="#l1crossdomainmessengerproxy" id="l1crossdomainmessengerproxy"></a>
This contract is a proxy for the L1CrossDomainMessenger contract on the L2, which can be used to the interaction with the L2 contract from L1.
The L1CrossDomainMessenger contract is a high-level interface for sending messages to and receiving messages from Mantle Network (from L1 to L2).
### L1StandardBridgeProxy[](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#l1standardbridgeproxy) <a href="#l1standardbridgeproxy" id="l1standardbridgeproxy"></a>
This contract is a proxy for the L1StandardBridge contract on the L2, which can be used to the interaction with the L2 bridge from L1.
The L1StandardBridge is a standardized contract for transferring ERC20 tokens to/from Mantle Network
### L1ERC721BridgeProxy[](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#l1erc721bridgeproxy) <a href="#l1erc721bridgeproxy" id="l1erc721bridgeproxy"></a>
The proxy contract for transferring ERC721 tokens to/from Mantle Network.
### L2OutputOracleProxy[](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#l2outputoracleproxy) <a href="#l2outputoracleproxy" id="l2outputoracleproxy"></a>
The proxy contract of stores commitments to the state of Mantle Network, which can be used by contracts on L1 to access the L2 state
### OptimismMintableERC20FactoryProxy[](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#optimismmintableerc20factoryproxy) <a href="#optimismmintableerc20factoryproxy" id="optimismmintableerc20factoryproxy"></a>
The proxy contract of factory contract for minting ERC20 tokens.
### OptimismPortalProxy[](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#optimismportalproxy) <a href="#optimismportalproxy" id="optimismportalproxy"></a>
The proxy contract of low-level message-passing interface.
### ProxyAdmin[](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#proxyadmin) <a href="#proxyadmin" id="proxyadmin"></a>
Admin contract for the contracts, is the owner of all the proxy contracts. It can be used to upgrade the most system contracts in Mantle.
### SystemConfigProxy[](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#systemconfigproxy) <a href="#systemconfigproxy" id="systemconfigproxy"></a>
This is a proxy contract of the system contract that stores the configuration values for the on-chain system.
### AddressManager[](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#addressmanager) <a href="#addressmanager" id="addressmanager"></a>
AddressManager is a legacy contract that was used in the old version of the Mantle system to manage a registry of string names to addresses.
<br>
# Key L1 Contract Address
[](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#key-l1-smart-contracts)
{% tabs %}
{% tab title="Mainnet" %}
| Contract | Address | Upgradeable | Owner Role |
| ------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ----------- | -------------------- |
| [`L1CrossDomainMessengerProxy`](/network/system-information/on-chain-system/contract-introduction#l1crossdomainmessengerproxy-1) | [0x676A795fe6E43C17c668de16730c3F690FEB7120](https://etherscan.io/address/0x676A795fe6E43C17c668de16730c3F690FEB7120) | ✅ | - |
| [`L1StandardBridgeProxy`](/network/system-information/on-chain-system/contract-introduction#l1standardbridgeproxy) | [0x95fC37A27a2f68e3A647CDc081F0A89bb47c3012](https://etherscan.io/address/0x95fC37A27a2f68e3A647CDc081F0A89bb47c3012) | ✅ | - |
| [`L1ERC721BridgeProxy`](/network/system-information/on-chain-system/contract-introduction#l1erc721bridgeproxy) | [0xCAF8938b6C4A27a96AaAfbb7228Fd613D40EA70a](https://etherscan.io/address/0xCAF8938b6C4A27a96AaAfbb7228Fd613D40EA70a) | ✅ | - |
| [`L2OutputOracleProxy`](/network/system-information/on-chain-system/contract-introduction#l2outputoracleproxy) | [0x31d543e7BE1dA6eFDc2206Ef7822879045B9f481](https://etherscan.io/address/0x31d543e7BE1dA6eFDc2206Ef7822879045B9f481) | ✅ | - |
| [`OptimismMintableERC20FactoryProxy`](/network/system-information/on-chain-system/contract-introduction#optimismmintableerc20factoryproxy) | [0x3b96c878cc334a7d9EA994Ec4B6C28BdDde00Eb2](https://etherscan.io/address/0x3b96c878cc334a7d9EA994Ec4B6C28BdDde00Eb2) | ✅ | - |
| [`OptimismPortalProxy`](/network/system-information/on-chain-system/contract-introduction#optimismportalproxy) | [0xc54cb22944F2bE476E02dECfCD7e3E7d3e15A8Fb](https://etherscan.io/address/0xc54cb22944F2bE476E02dECfCD7e3E7d3e15A8Fb) | ✅ | - |
| [`ProxyAdmin`](/network/system-information/on-chain-system/contract-introduction#proxyadmin) | [0xca35F8338054739D138884685e08b39EE2217794](https://etherscan.io/address/0xca35F8338054739D138884685e08b39EE2217794) | ✅ | Mantle Security Msig |
| [`SystemConfigProxy`](/network/system-information/on-chain-system/contract-introduction#systemconfigproxy) | [0x427Ea0710FA5252057F0D88274f7aeb308386cAf](https://etherscan.io/address/0x427Ea0710FA5252057F0D88274f7aeb308386cAf) | ✅ | - |
| [`AddressManager`](/network/system-information/on-chain-system/contract-introduction#addressmanager) | [0x6968f3F16C3e64003F02E121cf0D5CCBf5625a42](https://etherscan.io/address/0x6968f3F16C3e64003F02E121cf0D5CCBf5625a42) | ✅ | - |
| {% endtab %} | | | |
{% tab title="Testnet (Sepolia)" %}
| Contract | Address | Upgradeable | Owner Role |
| ------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ----------- | -------------------- |
| [`L1CrossDomainMessengerProxy`](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#l1crossdomainmessengerproxy) | [0x37dAC5312e31Adb8BB0802Fc72Ca84DA5cDfcb4c](https://sepolia.etherscan.io/address/0x37dAC5312e31Adb8BB0802Fc72Ca84DA5cDfcb4c) | ✅ | - |
| [`L1StandardBridgeProxy`](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#l1standardbridgeproxy) | [0x21F308067241B2028503c07bd7cB3751FFab0Fb2](https://sepolia.etherscan.io/address/0x21F308067241B2028503c07bd7cB3751FFab0Fb2) | ✅ | - |
| [`L1ERC721BridgeProxy`](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#l1erc721bridgeproxy) | [0x3938D52ba5B26c710512a75bC7907f2C01b2269f](https://sepolia.etherscan.io/address/0x3938D52ba5B26c710512a75bC7907f2C01b2269f) | ✅ | - |
| [`L2OutputOracleProxy`](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#l2outputoracleproxy) | [0x4121dc8e48Bc6196795eb4867772A5e259fecE07](https://sepolia.etherscan.io/address/0x4121dc8e48Bc6196795eb4867772A5e259fecE07) | ✅ | - |
| [`OptimismMintableERC20FactoryProxy`](https://docs-v2.mantle.xyz/intro/system-components/on-chain-system#optimismmintableerc20factoryproxy) | [0x247704aDA40aeB8aEbC3e8B17A2DC49fDb28D061](https://sepolia.etherscan.io/address/0x247704aDA40aeB8aEbC3e8B17프로젝트로 돌아가기