Search projects, tokens and protocols by name or address
RISE is a low-latency Optimium built on the OP Stack, using the OP Succinct Lite ZK fault proof system and posting data to EigenDA. It targets real-time trading applications through its RISEx exchange.
RISE is a low-latency Optimium built on the OP Stack, using the OP Succinct Lite ZK fault proof system and posting data to EigenDA. It targets real-time trading applications through its RISEx exchange.
Consequence: projects without a sufficiently decentralized set of challengers rely on few entities to safely update the state. A small set of challengers can collude with the proposer to finalize an invalid state, which can cause loss of funds.
Learn more about the recategorisation here.
The section shows the operating costs that L2s pay to Ethereum.
This section shows how "live" the project's operators are by displaying how frequently they submit transactions of the selected type. It also highlights anomalies — significant deviations from their typical schedule.
RISE public mainnet launch
1 May 2026
RISE opens its mainnet (genesis on January 5th 2026) to the public together with the RISEx exchange.
In the event of a 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. failure, users can force transactions to be included in the project’s chain by sending them to 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.. There can be up to a 12h delay on this operation.
Fraud proofs allow actors watching the chain to prove that the state is incorrect. Single round proofs (1R) only require a single transaction to resolve. ZK proofs are used to prove the correctness of the state transition. The system currently operates with a closed set of 1 whitelisted challenger.
Proof construction and state derivation fully rely on data that is posted on EigenDA. 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. is publishing data to EigenDA v2. Sequencer transaction data roots are checked against the DACert VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. data roots, signed off by EigenDA operators.
There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.
Only the whitelisted proposers can publish state rootsA cryptographic hash succinctly representing a state using a Merkle tree. on 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., so in the event of failure the withdrawals are frozen.
Transactions roots are posted onchain and the full data is posted on EigenDA. 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. is publishing data to EigenDA v2. The DACert VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. is used to verify attestations from the 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. set that the data is indeed available. If EigenDA becomes unavailable, the sequencer falls back to Ethereum.
Funds can be lost if the sequencer posts an unavailable transaction root (CRITICAL).
Funds can be lost if the data is not available on the external provider (CRITICAL).
State rootsA cryptographic hash succinctly representing a state using a Merkle tree. are proposed by whitelisted proposers who create dispute games via the Dispute
Funds can be stolen if the validity proof cryptography is broken or implemented incorrectly.
Funds can be stolen if no whitelisted challenger disputes an invalid state root before the challenge window expires (CRITICAL).
Funds can be stolen if the proposer routes proof verification through a malicious or faulty verifier.
Funds can be frozen if the permissioned proposer fails to publish state roots to the L1.
The metrics include upgrades on the currently used proxy contracts. Historical proxy contracts and changes of such are not included.
OptimismPortal2: upgraded to an implementation with the same source, proof maturity delay 7d → 4.5d (diff).
OptimismPortal2: upgraded to an implementation with the same source, proof maturity delay 7d → 4.5d (diff).
| contract OptimismPortal2 (eth:0xad92Fa18EB74E46Db844240623124BF46589db4C) [opstack/OptimismPortal2] { | |
| +++ description: The OptimismPortal contract is the main entry point to deposit funds from L1 to L2. It also allows to prove and finalize withdrawals. It specifies which game type can be used for withdrawals, which currently is the 42. | |
| values.$implementation: | |
| - | "eth:0x7Cf803296662e8C72A6C1d6450572209aCF7f202" |
| + | "eth:0x1A8DbaFa5011E44013A8F4e18D48629bB4a13832" |
| values.$pastUpgrades.1: | |
| + | ["2026-11-04T05:57:11.000Z","0x4ea43e5d47064518569b0ecc63488f5f71c26b700ee763718debcdf0e14c1d1d",["eth:0x1A8DbaFa5011E44013A8F4e18D48629bB4a13832"]] |
| values.$upgradeCount: | |
| - | 1 |
| + | 2 |
| values.proofMaturityDelaySeconds: | |
| - | 604800 |
| + | 388800 |
| implementationNames.eth:0x7Cf803296662e8C72A6C1d6450572209aCF7f202: | |
| - | "OptimismPortal2" |
| implementationNames.eth:0x1A8DbaFa5011E44013A8F4e18D48629bB4a13832: | |
| + | "OptimismPortal2" |
| } | |
SystemConfig gasLimit raised from 1500000000 to 2250000000 (+50%).
SystemConfig gasLimit raised from 1500000000 to 2250000000 (+50%).
| contract SystemConfig (eth:0xD3CAf2A473dBB5bc2E8FB7F328e01AB9B726a24f) [opstack/SystemConfig] { | |
| +++ description: Contains configuration parameters such as the Sequencer address, gas limit on this chain and the unsafe block signer address. | |
| +++ description: Gas limit for blocks on L2. | |
| +++ severity: LOW | |
| values.gasLimit: | |
| - | 1500000000 |
| + | 2250000000 |
| } | |
SystemConfig: batcherHash rotated ( 0x499a…8A41 → 0x0aE4…67d ); new batch submitter key.
SystemConfig: batcherHash rotated (0x499a…8A41 → 0x0aE4…67d); new batch submitter key.
| contract SystemConfig (eth:0xD3CAf2A473dBB5bc2E8FB7F328e01AB9B726a24f) [opstack/SystemConfig] { | |
| +++ description: Contains configuration parameters such as the Sequencer address, gas limit on this chain and the unsafe block signer address. | |
| values.batcherHash: | |
| - | "eth:0x499a15427F46685A362Dab7886A491FEfDf68A41" |
| + | "eth:0x0aE4b35f7F5efeB4c651684e1BCa12993dcBb67d" |
| } | |
Discovery rerun on the same block number with only config-related changes.
Discovery rerun on the same block number with only config-related changes.
| + | Status: CREATED |
| contract L1ERC721Bridge (eth:0x01A6274B9607ac024e8c191E491d0b25ad14c217) [opstack/L1ERC721Bridge] | |
| +++ description: Used to bridge ERC-721 tokens from host chain to this chain. | |
| + | Status: CREATED |
| contract Rise Guardian Multisig (eth:0x03B85FAa108C10F6EFfec1d91954DE99dA32FB46) [GnosisSafe] | |
| +++ description: None | |
| + | Status: CREATED |
| contract SP1Verifier (eth:0x0459d576A6223fEeA177Fb3DF53C9c77BF84C459) [succinct/SP1Verifier] | |
| +++ description: Verifier contract for SP1 proofs (v5.0.0). | |
| + | Status: CREATED |
| contract PreimageOracle (eth:0x1fb8cdFc6831fc866Ed9C51aF8817Da5c287aDD3) [opstack/PreimageOracle] | |
| +++ description: The PreimageOracle contract is used to load the required data from L1 for a dispute game. | |
| + | Status: CREATED |
| contract PermissionedDisputeGame (eth:0x2e7758aAD2B6D3D1Fd2C937D9B322378fC644633) [opstack/PermissionedDisputeGame] | |
| +++ description: Same as FaultDisputeGame, but only two permissioned addresses are designated as proposer and challenger. | |
| + | Status: CREATED |
| contract SP1VerifierGateway (eth:0x3B6041173B80E77f038f3F2C0f9744f04837185e) [succinct/SP1VerifierGateway] | |
| +++ description: This contract is the router for zk proof verification. It stores the mapping between identifiers and the address of onchain verifier contracts, routing each identifier to the corresponding verifier contract. | |
| + | Status: CREATED |
| contract ProxyAdmin (eth:0x4ebc046b1cfc12659A19E124b0ea8a382777E542) [global/ProxyAdmin] | |
| +++ description: None | |
| + | Status: CREATED |
| contract AnchorStateRegistry (eth:0x551A672d703966D83C3EC3ea0e844f43c3373c91) [opstack/AnchorStateRegistry_post13_opsuccinct] | |
| +++ description: Contains the latest confirmed state root 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). | |
| + | Status: CREATED |
| contract L1StandardBridge (eth:0x553257678Dd11a6668a92934AAB005e420c6535A) [opstack/L1StandardBridge] | |
| +++ description: The main entry point to deposit ERC20 tokens from host chain to this chain. | |
| + | Status: CREATED |
| contract MIPS (eth:0x6463dEE3828677F6270d83d45408044fc5eDB908) [opstack/MIPS] | |
| +++ description: The MIPS contract is used to execute the final step of the dispute game which objectively determines the winner of the dispute. | |
| + | Status: CREATED |
| contract DisputeGameFactory (eth:0x6A4139810986CF13408330e14C4ac9Daf0511aA3) [opstack/DisputeGameFactory] | |
| +++ description: The dispute game factory allows the creation of dispute games, used to propose state roots and eventually challenge them. | |
| + | Status: CREATED |
| contract SP1Verifier (eth:0x8a0fd5e825D14368d90Fe68F31fceAe3E17AFc5C) [succinct/SP1Verifier] | |
| +++ description: Verifier contract for SP1 proofs (v6.0.0). | |
| + | Status: CREATED |
| contract Rise ProxyAdminOwner Multisig (eth:0x9196464e3F828A50233C20732fa6898F4317002c) [GnosisSafe] | |
| +++ description: None | |
| + | Status: CREATED |
| contract OptimismPortal2 (eth:0xad92Fa18EB74E46Db844240623124BF46589db4C) [opstack/OptimismPortal2] | |
| +++ description: The OptimismPortal contract is the main entry point to deposit funds from L1 to L2. It also allows to prove and finalize withdrawals. It specifies which game type can be used for withdrawals, which currently is the 42. | |
| + | Status: CREATED |
| contract SuperchainConfig (eth:0xB786207A1EdfC724c1d507335f403F53fd9E79d6) [opstack/SuperchainConfigFake_expiry] | |
| +++ description: 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. | |
| + | Status: CREATED |
| contract OPSuccinctFaultDisputeGame (eth:0xBf60dBc272833cD25f0426983c3175C32C8E5A7a) [succinct/OPSuccinct/OPSuccinctFaultDisputeGame] | |
| +++ description: Logic of the dispute game. When a state root is proposed, a dispute game contract is deployed. Challengers can use such contracts to challenge the proposed state root. | |
| + | Status: CREATED |
| contract L1CrossDomainMessenger (eth:0xC0de1d9B1cD2Caf782355C66a6A8e5948e63c9c6) [opstack/L1CrossDomainMessenger] | |
| +++ description: 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 limit, it can be resubmitted via this contract's replay function. | |
| + | Status: CREATED |
| contract SP1Verifier (eth:0xc3c6dDDAc8829b233Dc6536Ec024775a57b0AF2A) [shared-sp1/SP1Verifier] | |
| +++ description: None | |
| + | Status: CREATED |
| contract SP1VerifierGatewayMultisig (eth:0xCafEf00d348Adbd57c37d1B77e0619C6244C6878) [GnosisSafe] | |
| +++ description: None | |
| + | Status: CREATED |
| contract ProxyAdmin (eth:0xCf32d8c4Be30cA330c1150916A71A651bADd70d5) [global/ProxyAdmin] | |
| +++ description: None | |
| + | Status: CREATED |
| contract SystemConfig (eth:0xD3CAf2A473dBB5bc2E8FB7F328e01AB9B726a24f) [opstack/SystemConfig] | |
| +++ description: Contains configuration parameters such as the Sequencer address, gas limit on this chain and the unsafe block signer address. | |
| + | Status: CREATED |
| contract AddressManager (eth:0xdE3a0F0122f702e018e04C6D0824B724E8Be8e16) [opstack/AddressManager] | |
| +++ description: Legacy contract used to manage a mapping of string names to addresses. Modern OP stack uses a different standard proxy system instead, but this contract is still necessary for backwards compatibility with several older contracts. | |
| + | Status: CREATED |
| contract OptimismMintableERC20Factory (eth:0xE2B9526277DcD2B27222Df760D6427213AC9dbb8) [opstack/OptimismMintableERC20Factory] | |
| +++ description: A helper contract that generates OptimismMintableERC20 contracts on the network 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. | |
| + | Status: CREATED |
| contract DelayedWETH (eth:0xf758C3bf7a4E2ad513B371B40c4Bd9A0E9716CF1) [opstack/DelayedWETH] | |
| +++ description: 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. | |
| + | Status: CREATED |
| contract AccessManager (eth:0xF90a72FC295DBEf2fD27629Fda4B98Fd3E842d17) [succinct/OPSuccinct/AccessManager] | |
| +++ description: Contract managing access control for proposers and challengers in OPSuccinct. | |
The 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. is the only entity that can propose blocksAn 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.. A live and trustworthy operator is vital to the health of the system.
MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.
Because the state of the system is based on transactions submitted on the underlying host chain and anyone can submit their transactions there it allows the users to circumvent censorship by interacting with the smart contract on the host chain directly.
The user initiates the withdrawal by submitting a regular transaction on this chain. When a state rootA cryptographic hash succinctly representing a state using a Merkle tree. containing such transaction is settled, the funds become available for withdrawal on 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. after 3d 12h. Withdrawal inclusion can be proven before state root settlementThe mechanism with which the execution of rollup blocks and the resultant state is verified and possible disputes are resolved. In the context of rollups or other modular blockchains, it often refers to the proof system used--validity (ZK) or fraud proofs, or a combination thereof. Sometimes it will refer to this mechanism along with where the mechanism's outputs are ultimately published and verified, as in Ethereum being a settlement layer by verifying the proofs and allowing for withdrawals., but a 4d 12h period has to pass before it becomes actionable. The process of state root settlement takes a challenge periodIn optimistic rollups, the window of time wherein network participants can assert that some fraud was included in a prior block. Most optimistic rollups currently specify a challenge window of 7 days. By extending the period, there is more time for participants to guard against fraud (invalid state transitions), but also more time until withdrawals gets enabled. of at least 1d to complete. Finally the user submits an L1 transaction to claim the funds. This transaction requires a merkle proof.
If the user experiences censorship from the 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. with regular 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.->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. messaging they can submit their messages directly on L1. The system is then obliged to service this request or halt all messages, including forced withdrawals from L1 and regular messages initiated on L2. Once the force operation is submitted and if the request is serviced, the operation follows the flow of a regular message.
OP stack chains are pursuing the EVM EquivalenceA perfect degree of compatibility; where one system or concept is indistinguishable from another in the domain being compared. In the context of rollups, it generally refers to the proximity to the EVM and to Ethereum architecture. model. No changes to smart contracts are required regardless of the language they are written in, i.e. anything deployed on 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. can be deployed on 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..

A Multisig with 3/6 threshold.
A Multisig with 3/5 threshold.
A Multisig with 9/13 threshold.
Member of Eigen
A Multisig with 2/4 threshold.
A Multisig with 3/5 threshold.
A Multisig with 3/5 threshold.
A Multisig with 3/4 threshold.
A Multisig with 3/8 threshold.
Participants (8):
0x9308…a125,0x5262…0aDA,0x9951…683F,0xA383…350A,0x44aC…B904,0x3C20…63e9,0xA4f7…dD31,0x542a…Bd7EA Multisig with 2/8 threshold.
Member of Eigen
Participants (8):
0xDe64…3370,0x55b0…44E8,0x4719…331A,0xa9f9…3d28,0x5CCF…d060,0xA756…8445,0xd757…B553,0xe2eB…26D2A Multisig with 2/3 threshold.
A Multisig with 3/5 threshold.
A Multisig with 1/2 threshold.
A Multisig with 1/1 threshold.
Member of Eigen
Participants (1):
0x5e6a…d3B5A Multisig with 1/2 threshold.
Member of Eigen
The current deployment carries some associated risks:
Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).

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.
Can be upgraded by: Rise ProxyAdminOwner Multisig with no delay
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.

Can be upgraded by: Rise ProxyAdminOwner Multisig with no delay
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.
Can be upgraded by: Rise ProxyAdminOwner Multisig with no delay
This is NOT the shared Superchain
Can be upgraded by: Rise ProxyAdminOwner Multisig with no delay
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..
Can be upgraded by: EigenDAOperationsMultisig with no delay
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.
Can be upgraded by: EigenDAOperationsMultisig with no delay
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.
Can be upgraded by: EigenDAOperationsMultisig with no delay
Defines and stores pauser and unpauser roles for EigenDA contracts.
Contract used for ejection of operators from the Registry
Can be upgraded by: EigenDAOperationsMultisig with no delay
Can be upgraded by: EigenDAOperationsMultisig with no delay
Registry for EigenDA disperser info such as disperser key to address mapping.
Can be upgraded by: EigenDAOperationsMultisig with no delay
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.
Can be upgraded by: EigenDAOperationsMultisig with no delay
Entrypoint for making reservations and on demand payments for EigenDA.
Can be upgraded by: EigenDAOperationsMultisig with no delay
A registry contract that keeps track of an ordered list of operators for each quorum.
Can be upgraded by: EigenDAOperationsMultisig with no delay
Registry for EigenDA relay keys, maps key to address.
Can be upgraded by: EigenDAOperationsMultisig with no delay
Registry of EigenDA threshold (i.e, adversary and confirmation threshold percentage for a quorum)
Can be upgraded by: EigenDAOperationsMultisig with no delay
Read-only view contract that exposes query functions for the Allocation
Upgradeable
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
Contract that enables AVSs and operators to delegate the ability to call certain core contract functions to other addresses.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
The Delegation
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
Upgradeable
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A timelock that allows scheduling calls and executing or cancelling them with a delay.
Member of Eigen
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
The token backing EIGEN and used for intersubjective staking.
Can be upgraded by: EigenLayerOperationsMultisig2 with 24d delay, EigenLayerOperationsMultisig with 24d delay, EigenLayerCommunityMultisig with no delay
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
A strategy implementation allowing to deposit a specific token as a restakable asset.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
Defines and stores pauser and unpauser roles for EigenLayer contracts.
A timelock that allows scheduling calls and executing or cancelling them with a delay.
Member of Eigen
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
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.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
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.
Can be upgraded by: Rise ProxyAdminOwner Multisig with no delay
The main entry point to deposit ERC20 tokens from host chain to this chain.
All supported tokens in this escrow are included in the value secured calculation.
Can be upgraded by: Rise ProxyAdminOwner Multisig with no delay
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.
Can be upgraded by: Rise ProxyAdminOwner Multisig with no delay
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 Fault
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 OPSuccinct
Can be upgraded by: Rise ProxyAdminOwner Multisig with no delay
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 Optimism
Can be upgraded by: Rise ProxyAdminOwner Multisig with no delay
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.
Can be upgraded by: Rise ProxyAdminOwner Multisig with no delay
Contract managing access control for proposers and challengers in OPSuccinct.
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.
Can be upgraded by: EigenDAOperationsMultisig with no delay
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.
A beacon with an upgradeable implementation currently set as Duration
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
Manages the distribution of rewards (arbitrary tokens, EIGEN) to restakers and commission to operators.
Can be upgraded by: EigenLayerOperationsMultisig2 with 10d delay, EigenLayerOperationsMultisig with 10d delay, EigenLayerCommunityMultisig with no delay
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.
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).