RISE

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 Rise ProxyAdminOwner Multisig
  • owner: Rise ProxyAdminOwner Multisig

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 42.

• Roles:
  • admin: ProxyAdmin; ultimately Rise ProxyAdminOwner Multisig

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 Rise ProxyAdminOwner Multisig
  • batcherHash: EOA 1
  • owner: Rise Guardian Multisig

This is NOT the shared SuperchainConfig contract of the OP stack Superchain but rather a local fork. It manages pause states for each chain connected to it, as well as a global pause state for all chains. The guardian role can pause either separately, but each pause expires after 3mo 1d if left untouched.

• Roles:
  • admin: ProxyAdmin; ultimately Rise ProxyAdminOwner Multisig
  • guardian: Rise Guardian Multisig

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 10, EOA 11, EOA 12, EOA 13, EOA 14, EOA 15, 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
  • owner: EigenDAOperationsMultisig

Read-only view contract that exposes query functions for the AllocationManager, allowing external callers to look up 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. stake allocations, magnitudes, operator sets, and slashable/redistributable status.

UpgradeableBeacon managing the single implementation for all strategies deployed via StrategyFactory.

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

Task lifecycle manager where users create tasks with fee payments directed at specific executor 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. sets, and executors submit results verified via BN254 or ECDSA certificate verification, with fee distribution on successful verification and refunds on task expiration.

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

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

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

Contract that enables AVSs and operators to delegate the ability to call certain core contract functions to other addresses.

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

Admin-controlled on-chain registry that tracks all EigenLayer protocol contract deployments (addresses, names, configs, and versioning) and provides a pauseAll function to pause every registered pausable contract in the protocol.

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

A strategy implementation allowing to deposit a specific token as a restakable asset.

• 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

Verifies BLS (BN254 curve) certificates for EigenLayer 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. sets by computing the aggregate public key of signers, performing pairing-based signature verification, and returning signed-stake weights for quorum threshold validation.

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

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

Manages the registration and deregistration of 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. cryptographic keys (ECDSA or BN254/BLS) for specific operator sets, enforcing signature-based proof of key ownership and global uniqueness of keys across the protocol.

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

Central coordinator for EigenLayer’s 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. table system: accepts BN254-certified global Merkle table roots from a designated generator operator set, then allows Merkle proof submissions to push per-operator-set tables into the certificate verifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contracts.

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

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

UpgradeableBeacon managing the single implementation for all strategies deployed via StrategyFactory.

Factory contract for permissionlessAnyone willing should be able to join and leave the network at any time, without causing significant disturbance to the network or being detrimental to the party in question. No single entity should have the power to allowlist or blocklist participants. strategy creation via beacon proxies.

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

A timelock that allows scheduling calls and executing or cancelling them with a delay. Member of EigenLayerBeigenOwningMultisig.

• Roles:
  • cancellers: EigenLayerOperationsMultisig
  • executors: EigenLayerOperationsMultisig2
  • proposers: EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

The token backing EIGEN and used for intersubjective staking.

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

The StrategyManager contract is responsible for managing the EigenLayer token strategies. Each EigenDA quorum has at least one strategy that defines the operators quorum stake.

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

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

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

Allows AVSs to create generation reservations that configure and schedule the transport of 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. tables (stake weight 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. to whitelisted 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. chains, managing per-operator-set configs such as staleness periods and operator table calculators.

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

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

Contract used to create 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. Sets, and used by Operators to register to them. The Allocation Manager tracks allocation of stake to a Operator Set, and enables AVSs to slash that stake.

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

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

A strategy implementation allowing to deposit a specific token as a restakable asset.

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

Defines and stores pauser and unpauser roles for EigenLayer contracts.

• Roles:
  • pausers: EigenLayerOperationsMultisig, EigenLayerOwningMultisig, EigenLayerPauserMultisig, ProtocolRegistry

A timelock that allows scheduling calls and executing or cancelling them with a delay. Member of EigenLayerOwningMultisig.

• Roles:
  • cancellers: EigenLayerOperationsMultisig
  • executors: EigenLayerOperationsMultisig2
  • proposers: EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2

Verifies ECDSA-based certificates for EigenLayer 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. sets by recovering signer addresses from concatenated signatures, confirming each signer is a registered operator, and tallying their stake weights against quorum thresholds.

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

The EIGEN token can be socially forked to slash operators for data withholding attacks (and other intersubjectively attributable faults). EIGEN is a wrapper over a second token, bEIGEN, which will be used solely for intersubjective staking. Forking EIGEN means changing the canonical implementation of the bEIGEN token in the EIGEN token contract.

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

Manages software release lifecycle for EigenLayer 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. sets, allowing AVS owners to publish versioned releases (containing artifact digests, registry URLs, and upgrade-by deadlines) and metadata URIs that operators can query for required software versions.

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

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 Rise ProxyAdminOwner Multisig

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

• Roles:
  • admin: ProxyAdmin; ultimately Rise ProxyAdminOwner Multisig

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 Rise ProxyAdminOwner Multisig

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.

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.

• Roles:
  • owner: Rise ProxyAdminOwner Multisig

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. It specifies which game type can be used for withdrawals, which currently is the OPSuccinctFaultDisputeGame. Variant for chains using OPSuccinct (SP1) games instead of Cannon, which omits Cannon-specific cross-contract fields (vm, oracle, weth, challengePeriod, absolutePrestate from game).

• Roles:
  • admin: ProxyAdmin; ultimately Rise ProxyAdminOwner Multisig

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

Logic of the dispute game. When a state rootA cryptographic hash succinctly representing a state using a Merkle tree. is proposed, a dispute game contract is deployed. Challengers can use such contracts to challenge the proposed state root.

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 Rise ProxyAdminOwner Multisig

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 Rise ProxyAdminOwner Multisig

Contract managing access control for proposers and challengers in OPSuccinct.

• Roles:
  • challengers: EOA 17
  • owner: Rise ProxyAdminOwner Multisig
  • proposers: EOA 16

A router contract for DA Certificate verifiers. VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. routing depends on the certificate reference 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. number.

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

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.

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.

• Roles:
  • owner: EigenDAOperationsMultisig

A beacon with an upgradeable implementation currently set as DurationVaultStrategy. Beacon proxy contracts pointing to this beacon will all use its implementation.

• Roles:
  • owner: EigenLayerOwningMultisig; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2

• Roles:
  • owner: EigenLayerBeigenOwningMultisig

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

Manages the distribution of rewards (arbitrary tokens, EIGEN) to restakers and commission to operators.

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

• Roles:
  • owner: EigenLayerOwningMultisig

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.1.0).