Mantle

Contains configuration parameters such as the batch submitter (SequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs.) address, the L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups. gas limitThe maximum amount of gas a transaction or block may consume., the unsafe blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. signer address and the Arsia fee/gasA virtual fuel used to execute smart contracts on a rollup. The EVM (or other VM within the rollup) uses an accounting mechanism to correspond the consumption of gas to the consumption of computing resources, and to limit the consumption of computing resources. mechanics (base/blobThe data that a rollup publishes to its L1/data availability (DA) layer. They consist of the L2 transactions that are rolled up, along with some metadata. Blobs are introduced as a new transaction type within Ethereum with EIP-4844, and has rollup scaling specifically in mind. Blobs persist on Ethereum’s Beacon Chain ephemerally. scalars, EIP-1559 params, minimum base fee, DA footprint gas scalar and EIP-7706-style operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. fee).

• Roles:
  • admin: ProxyAdmin; ultimately MantleSecurityMultisig
  • batcherHash: EOA 1
  • owner: MantleSecurityMultisig

The main entry point to deposit funds from host chain to this chain. It also allows to prove and finalize withdrawals.

• Roles:
  • admin: ProxyAdmin; ultimately MantleSecurityMultisig
  • guardian: MantleEngineeringMultisig

Sends messages from host chain to this chain, and relays messages back onto host chain. In the event that a message sent from host chain to this chain is rejected for exceeding this chain’s epoch gas limitThe maximum amount of gas a transaction or block may consume., it can be resubmitted via this contract’s replay function.

• Roles:
  • admin: ProxyAdmin; ultimately MantleSecurityMultisig

The main entry point to deposit ERC20 tokens from host chain to this chain.

• Roles:
  • admin: ProxyAdmin; ultimately MantleSecurityMultisig

• Roles:
  • owner: TimelockController

Contains a list of proposed state rootsA cryptographic hash succinctly representing a state using a Merkle tree. which Proposers assert to be a result of blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. execution. The SuccinctL2OutputOracle modifies the L2OutputOracle to support whenNotOptimistic mode, in which a validity proofThe output of a cryptographic proving system attesting to correct computation. ZK-Rollups use succinct validity proofs (also called zero-knowledge proofs) to prove a batch of rollup transactions and blocks were properly executed. Validity proofs are submitted to a verifier, such as an Ethereum smart contract, which accepts them if properly constructed. can be passed as input argument to the proposeL2Output function.

• Roles:
  • admin: ProxyAdmin; ultimately MantleSecurityMultisig
  • challenger: MantleEngineeringMultisig
  • initialProposer: EOA 2
  • owner: MantleSecurityMultisig

MNT token contract: Mantle uses Mantle (MNT) as the designated gasA virtual fuel used to execute smart contracts on a rollup. The EVM (or other VM within the rollup) uses an accounting mechanism to correspond the consumption of gas to the consumption of computing resources, and to limit the consumption of computing resources. token, allowing users pay for gas in MNT.

• Roles:
  • admin: MantleTokenProxyAdmin; ultimately MantleSecurityMultisig
  • owner: MantleSecurityMultisig

A timelock with access control. The current minimum delay is 1d.

• Roles:
  • canceller: MantleSecurityMultisig
  • defaultAdmin: MantleSecurityMultisig, TimelockController; ultimately MantleSecurityMultisig
  • executor: MantleSecurityMultisig
  • proposerIn the context of L2s, the actor that proposes a claimed state root on L1. The term is also used in the context of Ethereum to refer to the actor that proposes a new block.: MantleSecurityMultisig

• Roles:
  • owner: MantleSecurityMultisig

VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contract for SP1 proofs (v5.0.0).

This contract is the router for zk proof verification. It stores the mapping between identifiers and the address of onchain verifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contracts, routing each identifier to the corresponding verifier contract.

• Roles:
  • owner: SP1VerifierGatewayMultisig

VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contract for SP1 proofs (v6.0.0).

VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contract for SP1 proofs (v6.1.0).