MegaETH

Entrypoint for state rootA cryptographic hash succinctly representing a state using a Merkle tree. proposals. Manages bonds (currently 0.00001 ETH) and tournaments for the OP Kailua state validation system, wrapping the OP stack native DisputeGameFactory.

Onchain EigenDA certificate verification inbox. Receives batch data, strips 4-byte prefix, RLP-decodes EigenDACertV3 and calls the EigenDACertVerifier to validate the certificate. Used as the batch inbox for EigenDA-based data availabilityThe property of a rollup's data being reachable by any node retrieving the data that were rolled up and executed to reach the proposed state. Data availability (DA), specifically decoupling it from the rollup nodes themselves, is one of the preeminent factors which allows a rollup to scale securely. A rollup is faced with a decision of what to use as a DA layer to guarantee that any node can retrieve this data--permissionlessly under any circumstance. For this reason, using Ethereum for DA currently provides the strongest security guarantees. If data is stored somewhere other than a permissionless L1, then the project is not a rollup, but rather a validium or an optimium..

• Roles:
  • admin: Safe

Contains configuration parameters such as the 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, gas limitThe maximum amount of gas a transaction or block may consume. on this chain and 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.

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

VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contract for RISC Zero Groth16A zk-SNARK proving system introduced by Groth in 2016 that proves arithmetic circuits and requires a separate trusted setup for each circuit. It allows extremely efficient proof verification. proofs (version 2.0.0-rc.3).

The OptimismPortal contract is the main entry point to deposit funds from L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. to 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.. It also allows to prove and finalize withdrawals. It specifies which game type can be used for withdrawals, which currently is the KailuaGame.

• Roles:
  • admin: ProxyAdmin; ultimately Safe

The dispute game factory allows the creation of dispute games, used to propose state rootsA cryptographic hash succinctly representing a state using a Merkle tree. and eventually challenge them.

• Roles:
  • admin: ProxyAdmin; ultimately Safe

Keeps track of the total stake of each 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..

• Roles:
  • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig

Keeps track of the BLS public keys of each 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. and the quorum aggregated keys.

• Roles:
  • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig

Operators register here with an AVS The coordinator has three registries 1) a StakeRegistry that keeps track of operators’ stakes, 2) a BLSApkRegistry that keeps track of operators’ BLS public keys and aggregate BLS public keys for each quorum, 3) an IndexRegistry that keeps track of an ordered list of operators for each quorum.

• Roles:
  • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
  • churnApprover: EOA 7
  • owner: EigenDAOperationsMultisig

Defines and stores pauser and unpauser roles for EigenDA contracts.

• Roles:
  • pausers: EigenLayerOperationsMultisig, EigenLayerOwningMultisig, EigenLayerPauserMultisig

Contract used for ejection of operators from the RegistryCoordinator for violating the Service Legal Agreement (SLA).

• Roles:
  • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
  • ejectors: EOA 4, EOA 6, EigenDA Multisig

• Roles:
  • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig

Registry for EigenDA disperser info such as disperser key to address mapping.

• Roles:
  • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
  • dispersers: EOA 9

BridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge. contract that accepts 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. batches data availabilityThe property of a rollup's data being reachable by any node retrieving the data that were rolled up and executed to reach the proposed state. Data availability (DA), specifically decoupling it from the rollup nodes themselves, is one of the preeminent factors which allows a rollup to scale securely. A rollup is faced with a decision of what to use as a DA layer to guarantee that any node can retrieve this data--permissionlessly under any circumstance. For this reason, using Ethereum for DA currently provides the strongest security guarantees. If data is stored somewhere other than a permissionless L1, then the project is not a rollup, but rather a validium or an optimium. attestations. Batches availability is attested by EigenDA operators signatures and relayed to the service manager contract by the EigenDA disperser.

• Roles:
  • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
  • batchConfirmers: EOA 2, EOA 3, EOA 5
  • owner: EigenDAOperationsMultisig
  • pauserRegistry: PauserRegistry; ultimately EOA 11, EOA 12, EOA 13, EOA 14, EOA 15, EOA 16, EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2, Safe
  • rewardsInitiator: EigenLayerRewardsInitiatorMultisig

Entrypoint for making reservations and on demand payments for EigenDA.

• Roles:
  • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig

A registry contract that keeps track of an ordered list of operators for each quorum.

• Roles:
  • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig

Registry for EigenDA relay keys, maps key to address.

• Roles:
  • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
  • relayers: EOA 8

Registry of EigenDA threshold (i.e, adversary and confirmation threshold percentage for a quorum)

• Roles:
  • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig

• Roles:
  • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2

The DelegationManager contract is responsible for registering EigenLayer operators and managing the EigenLayer strategies delegations. The EigenDA StakeRegistry contract reads from the DelegationManager to track the total stake of each EigenDA 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..

• Roles:
  • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2

This is NOT the shared SuperchainConfig contract of the OP stack Superchain but rather a local fork. It manages the PAUSED_SLOT, a boolean value indicating whether the local chain is paused, and GUARDIAN_SLOT, the address of the guardian which can pause and unpause the system.

• Roles:
  • admin: ProxyAdmin; ultimately Safe
  • guardian: Safe; ultimately EOA 10

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

• Roles:
  • admin: ProxyAdmin; ultimately Safe

Used to bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge. ERC-721 tokens from host chain to this chain.

• Roles:
  • admin: ProxyAdmin; ultimately Safe

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 Safe

Refund escrow designed to hold the funds extracted from the predeposit vault and send them back to the users listed in the vault.

• Roles:
  • defaultAdmin: Safe
  • executor: Safe

Predeposit Escrow, not connected to an 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.: Users can deposit USDC. The system uses off-chain permit signatures to ensure only KYC’d users can deposit. Withdrawals can only be made by Megaeth Multisig to MegaPreDepositVaultRefund.

• Roles:
  • owner: Megaeth Multisig
  • permitSigner: EOA 17

• Roles:
  • owner: Safe

The PreimageOracle contract is used to load the required data from L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. for a dispute game.

• Roles:
  • owner: EigenDAOperationsMultisig

Contract designed to hold the bonded ETH for each game. It is designed as a wrapper around WETH to allow an owner to function as a backstop if a game would incorrectly distribute funds.

• Roles:
  • admin: ProxyAdmin; ultimately Safe
  • owner: Safe

Implementation of the KailuaGame with type 1337. Based on this implementation, new KailuaGames are created with every new state rootA cryptographic hash succinctly representing a state using a Merkle tree. proposal.

A router proxy that routes to verifiers based on selectors. The mapping can be changed by a permissioned owner (0x0A383fF8387CF07315f476D1686E95b1a97adc97).

• Roles:
  • owner: EOA 10

A DA verifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contract for EigenDA V2 certificates. The verifier is used to verify the certificate against 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. signatures and stake thresholds.

Same as FaultDisputeGame, but only two permissioned addresses are designated as 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. and challenger.

Contains the latest confirmed state rootA cryptographic hash succinctly representing a state using a Merkle tree. that can be used as a starting point in a dispute game.

• Roles:
  • admin: ProxyAdmin; ultimately Safe

The MIPS contract is used to execute the final step of the dispute game which objectively determines the winner of the dispute.

A helper contract that generates OptimismMintableERC20 contracts on the networkA constellation of nodes (peers) that communicate via a peer-to-peer protocol, for example, in propagating transactions and blocks to other nodes. it’s deployed to. OptimismMintableERC20 is a standard extension of the base ERC20 token contract designed to allow the L1StandardBridge contracts to mint and burn tokens. This makes it possible to use an OptimismMintableERC20 as this chain’s representation of a token on the host chain, or vice-versa.

• Roles:
  • admin: ProxyAdmin; ultimately Safe

Multisig currently designated as the ‘Treasury’.