Search
Search for projects by name or address
Unichain
There are impactful changes and part of the information might be outdated.
Badges
About
Unichain, a faster, cheaper L2 designed to be the home for DeFi and the home for multichain liquidity.
- Upgrades unrelated to onchain provable bugs provide less than 30d to exit.
- The Security Council's actions are not confined to onchain provable bugs.
Badges
About
Unichain, a faster, cheaper L2 designed to be the home for DeFi and the home for multichain liquidity.
The section shows the operating costs that L2s pay to Ethereum.
This section shows how much data the project publishes to its data-availability (DA) layer over time. The project currently posts data toEthereum.
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.
UNIfication proposal executed
2025 Dec 27th
Uniswap governance enabled protocol fees, burned 100M UNI, and routed Unichain fees to UNI burn.
Unichain flashblocks are live
2025 Aug 14th
Unichain hits 200ms sub-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. inside Trusted Execution Environments.
Funds can be stolen if
MEV can be extracted if
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. Interactive proofs (INT) require multiple transactions over time to resolve.
All of the data needed for proof construction is published on Ethereum 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 is no exit windowThe amount of time that users have to exit a system before an unwanted upgrade. It takes into account upgrade delays, forced transaction delays and other time factors. To be considered Stage 1, a rollup needs to have an exit window of at least 7d if upgrades are initiated by a permissioned actor less decentralized than a Security Council. For Stage 2, a rollup needs at least 30d in all cases outside of onchain provable bugs. for users to exit in case of unwanted upgrades as they are initiated by the Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups. with instant upgrade power and without proper notice.
Anyone can be a 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 propose new roots to the 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. 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..
All data required for proofs is published on chain
All the data that is used to construct the system state is published on chain in the form of cheap blobsThe 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. or calldata. This ensures that it will be available for enough time.
- Derivation: Batch submission - OP Mainnet specs
- BatchInbox - address
- OptimismPortal2.sol - source code, depositTransaction function
EthereumThe rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. nodeA software client that participates in the network. is composed of two software components: op-node, implementing consensusAn agreement on the latest and correct state of a blockchain. Unlike L1 blockchains which coordinate participating nodes with consensus rules, rollups rely on L1s for reaching consensus by checking the state of the rollup smart contract deployed thereon. related logic, and op-geth, implementing execution logic. The configuration file can be found here.
Data batches are compressed using the zlib algorithm with best compression level.
The genesis file can be found here.
The format specification of 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.’s data batches can be found here.
Updates to the system state can be proposed and challenged by anyone who has sufficient funds. If a state rootA cryptographic hash succinctly representing a state using a Merkle tree. passes the 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., it is optimistically considered correct and made actionable for withdrawals.
Proposers submit state rootsA cryptographic hash succinctly representing a state using a Merkle tree. as children of the latest confirmed state root (called anchor state), by calling the create function in the DisputeGameFactory. A state root can have multiple conflicting children. Each proposal requires a stake, currently set to 0.08 ETH, that can be slashed if the proposal is proven incorrect via a fraud proofAlso referred to as a fault proof, it is the construction of an assertion that fraud was perpetrated on an optimistic rollup. More concretely, that an invalid state transition took place according to the protocol rules. The submitter of a fraud proof would expect a reward from the optimistic rollup protocol for helping maintain the integrity of the system.. Stakes can be withdrawn only after the proposal has been confirmed. A state root gets confirmed if the 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. has passed and it is not countered.
Challenges are opened to disprove invalid state rootsA cryptographic hash succinctly representing a state using a Merkle tree. using bisection games. Each bisection move requires a stake that increases expontentially with the depth of the bisection, with a factor of 1.09493. The maximum depth is 73, and reaching it therefore requires a cumulative stake of 691.23 ETH from depth 0. Actors can participate in any challenge by calling the defend or attack functions, depending whether they agree or disagree with the latest claim and want to move the bisection game forward. Actors that disagree with the top-level claim are called challengers, and actors that agree are called defenders. Each actor might be involved in multiple (sub-)challenges at the same time, meaning that the protocol operates with full concurrency. Challengers and defenders alternate in the bisection game, and they pass each other a clock that starts with 3d 12h. If a clock expires, the claim is considered defeated if it was countered, or it gets confirmed if uncountered. Since honest parties can inherit clocks from malicious parties that play both as challengers and defenders (see freeloader claims), an inherited clock with too little time remaining is generally extended by 3h. The extension is 6h when the next claim is immediately before split depth 30, and 1d 3h (the standard extension plus the 1d oracle 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.) immediately before the last depth. Along a full-depth path, cumulative extensions can therefore add up to 10d 3h. Since unconfirmed state roots are independent of one another, users can decide to exit with a subsequent confirmed state root if the previous one is delayed. Winners get the entire losers’ stake, meaning that sybils can potentially play against each other at no cost. The final instruction found via the bisection game is then executed onchain in the MIPS one step proverAn entity that generates the cryptographic proof to convince the verifier that the statement is true. In a ZK-Rollup, the prover generates the ZK (validity) proof to submit to the verifier contract. contract who determines the winner. The protocol does not enforce valid bisections, meaning that actors can propose correct initial claims and then provide incorrect midpoints. The protocol can be subject to resource exhaustion attacks (Spearbit 5.1.3).
Program Hashes
Name | Hash | Repository | Verification | Used in | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0x033c...bb6e |     Projects used inSearch for projects used in | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Past upgrades
The metrics include upgrades on the currently used proxy contracts. Historical proxy contracts and changes of such are not included.
2026 July 06, 07:56 UTCHigh severity8changesShared SuperchainConfig upgraded 2.4.0 → 2.4.2 (diff). No behavioral change — ProxyAdminOwnedBase import moved, misleading pause-state warning removed, and 5 new unused constants added to the shared Constants library (forward-plumbing for OPCM tooling).
Shared SuperchainConfig upgraded 2.4.0 → 2.4.2 (diff). No behavioral change — ProxyAdminOwnedBase import moved, misleading pause-state warning removed, and 5 new unused constants added to the shared Constants library (forward-plumbing for OPCM tooling).
| contract SuperchainConfig (eth:0x95703e0982140D16f8ebA6d158FccEde42f04a4C) [opstack/SuperchainConfig_expiry] { | |
| +++ description: Used to manage global configuration values for multiple OP Chains within a single Superchain network. The SuperchainConfig contract manages individual 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 3 months if left untouched. | |
| sourceHashes.1: | |
| - | "0x5fb525d1572fb90d060d122143b915059cbff39e0298b345857fd4267d7f6b28" |
| + | "0x2cd597b7305a446a1df355e6909cbd75fe38aa045faf4876a8e5496eebc1734f" |
| values.$implementation: | |
| - | "eth:0xb08Cc720F511062537ca78BdB0AE691F04F5a957" |
| + | "eth:0xE4F9779ab53070a55db24dFAeFf9AF147c6ED550" |
| values.$pastUpgrades.6: | |
| + | ["2026-06-25T23:05:47.000Z","0xbfdac60c9687a2e469159bf2458e73de2915a0a5eb53c4991a7ecde2b1fb3f15",["eth:0x2476c911E6D4D9411E677D8Faf15a64ac1fDEEe8"]] |
| values.$pastUpgrades.7: | |
| + | ["2026-06-25T23:05:47.000Z","0xbfdac60c9687a2e469159bf2458e73de2915a0a5eb53c4991a7ecde2b1fb3f15",["eth:0xE4F9779ab53070a55db24dFAeFf9AF147c6ED550"]] |
| values.$upgradeCount: | |
| - | 6 |
| + | 8 |
| values.version: | |
| - | "2.4.0" |
| + | "2.4.2" |
| implementationNames.eth:0xb08Cc720F511062537ca78BdB0AE691F04F5a957: | |
| - | "SuperchainConfig" |
| implementationNames.eth:0xE4F9779ab53070a55db24dFAeFf9AF147c6ED550: | |
| + | "SuperchainConfig" |
| } | |
2026 June 02, 10:54 UTC4changesUnichain Multisig 1 and Multisig 2 each rotated one signer. New game name (aggregateVerifier) added to portal.
Unichain Multisig 1 and Multisig 2 each rotated one signer.
New game name (aggregateVerifier) added to portal.
| contract Unichain Multisig 2 (eth:0x9245d5D10AA8a842B31530De71EA86c0760Ca1b1) [GnosisSafe] { | |
| +++ description: None | |
| values.$members.0: | |
| + | "eth:0x5b5B0669De777AF0Eb7A73eD46AaEe9711ab01E4" |
| values.$members.2: | |
| - | "eth:0xFA361ece9724d75B7EdF08B9A238706EAe270d3f" |
| } | |
| contract Unichain Multisig 1 (eth:0xb0c4C487C5cf6d67807Bc2008c66fa7e2cE744EC) [GnosisSafe] { | |
| +++ description: None | |
| values.$members.0: | |
| + | "eth:0xc8C31213545f32230E0327Db76df5538c2836081" |
| values.$members.2: | |
| - | "eth:0xf89C1b6e5D65e97c69fbc792f1BcdcB56DcCde91" |
| } | |
2026 May 15, 13:08 UTC4changesScheduled signer-key rotation on shared OP Stack governance contracts (no threshold or permission changes): - DeputyPauseModule ( 0x76fC2F971FB355D0453cF9F64d3F9E4f640E1754 ): deputy rotated from 0x352f1defB49718e7Ea411687E850aA8d6299F7aC to 0x2fA150379bF32b6d79Eeb4ff9bD280E76049a87c . Executed via superchain-ops eth/052; the DeputyPauseModule spec specifies that this is a regular rotation. - OpFoundationUpgradeSafe and OpFoundationOperationsSafe: Member rotated.
Scheduled signer-key rotation on shared OP Stack governance contracts (no threshold or permission changes):
- DeputyPauseModule (
0x76fC2F971FB355D0453cF9F64d3F9E4f640E1754):deputyrotated from0x352f1defB49718e7Ea411687E850aA8d6299F7aCto0x2fA150379bF32b6d79Eeb4ff9bD280E76049a87c. Executed via superchain-ops eth/052; the DeputyPauseModule spec specifies that this is a regular rotation. - OpFoundationUpgradeSafe and OpFoundationOperationsSafe: Member rotated.
| contract DeputyPauseModule (eth:0x76fC2F971FB355D0453cF9F64d3F9E4f640E1754) [opstack/DeputyPauseModule] { | |
| +++ description: Allows eth:0x2fA150379bF32b6d79Eeb4ff9bD280E76049a87c, called the deputy pauser, to act on behalf of the eth:0x847B5c174615B1B7fDF770882256e2D3E95b9D92 if set as its Safe module. | |
| description: | |
| - | "Allows eth:0x352f1defB49718e7Ea411687E850aA8d6299F7aC, called the deputy pauser, to act on behalf of the eth:0x847B5c174615B1B7fDF770882256e2D3E95b9D92 if set as its Safe module." |
| + | "Allows eth:0x2fA150379bF32b6d79Eeb4ff9bD280E76049a87c, called the deputy pauser, to act on behalf of the eth:0x847B5c174615B1B7fDF770882256e2D3E95b9D92 if set as its Safe module." |
| values.deputy: | |
| - | "eth:0x352f1defB49718e7Ea411687E850aA8d6299F7aC" |
| + | "eth:0x2fA150379bF32b6d79Eeb4ff9bD280E76049a87c" |
| } | |
| contract OpFoundationUpgradeSafe (eth:0x847B5c174615B1B7fDF770882256e2D3E95b9D92) [GnosisSafe] { | |
| +++ description: None | |
| values.$members.6: | |
| - | "eth:0xc222ab08333109243B1f4E2a80e3D0A190714AB5" |
| + | "eth:0xa2A58E31C03C59e34ab4d996d811DA0C035BfDea" |
| } | |
| contract OpFoundationOperationsSafe (eth:0x9BA6e03D8B90dE867373Db8cF1A58d2F7F006b3A) [GnosisSafe] { | |
| +++ description: None | |
| values.$members.6: | |
| - | "eth:0xc222ab08333109243B1f4E2a80e3D0A190714AB5" |
| + | "eth:0xa2A58E31C03C59e34ab4d996d811DA0C035BfDea" |
| } | |
2026 May 05, 15:18 UTC1changeOptimism Security Council ( eth:0xc2819DC7... ) — member 12 swap: 0x92827223 → 0xcbC7dCeb . Shared multisig (referenced by multiple Superchain projects).
Optimism Security Council (eth:0xc2819DC7...) — member 12 swap: 0x92827223 → 0xcbC7dCeb. Shared multisig (referenced by multiple Superchain projects).
| contract Optimism Security Council (eth:0xc2819DC788505Aac350142A7A707BF9D03E3Bd03) { | |
| +++ description: None | |
| values.$members.12: | |
| - | "eth:0x92827223f6b397CE9F208eE352bacA710765cACb" |
| + | "eth:0xcbC7dCeb857F0b25523618cCa0A03c419a6d7eA6" |
| } | |
2026 March 25, 10:07 UTC7changesThree signers of the shared OpFoundation multisigs (OpFoundationUpgradeSafe and OpFoundationOperationsSafe) were rotated. The old signer at position 0 was a GnosisSafe (0x42d27eEA1AD6e22Af6284F609847CB3Cd56B9c64) which was replaced by a new EOA.
Three signers of the shared OpFoundation multisigs (OpFoundationUpgradeSafe and OpFoundationOperationsSafe) were rotated. The old signer at position 0 was a GnosisSafe (0x42d27eEA1AD6e22Af6284F609847CB3Cd56B9c64) which was replaced by a new EOA.
| - | Status: DELETED |
| contract GnosisSafe (eth:0x42d27eEA1AD6e22Af6284F609847CB3Cd56B9c64) | |
| +++ description: None | |
| contract OpFoundationUpgradeSafe (eth:0x847B5c174615B1B7fDF770882256e2D3E95b9D92) { | |
| +++ description: None | |
| values.$members.0: | |
| - | "eth:0x42d27eEA1AD6e22Af6284F609847CB3Cd56B9c64" |
| + | "eth:0x6419F81580343DF023E68715C6e269aFb00a2cc7" |
| values.$members.2: | |
| - | "eth:0xE7dEA1306D9F829bA469d1904c50903b46ebd02e" |
| + | "eth:0xC2Db495f5a1F91172A361AAFA6FdE47c41de6dF5" |
| values.$members.6: | |
| - | "eth:0x9bbFB9919062C29a5eE15aCD93c9D7c3b14d31aa" |
| + | "eth:0xc222ab08333109243B1f4E2a80e3D0A190714AB5" |
| } | |
| contract OpFoundationOperationsSafe (eth:0x9BA6e03D8B90dE867373Db8cF1A58d2F7F006b3A) { | |
| +++ description: None | |
| values.$members.0: | |
| - | "eth:0x42d27eEA1AD6e22Af6284F609847CB3Cd56B9c64" |
| + | "eth:0x6419F81580343DF023E68715C6e269aFb00a2cc7" |
| values.$members.2: | |
| - | "eth:0xE7dEA1306D9F829bA469d1904c50903b46ebd02e" |
| + | "eth:0xC2Db495f5a1F91172A361AAFA6FdE47c41de6dF5" |
| values.$members.6: | |
| - | "eth:0x9bbFB9919062C29a5eE15aCD93c9D7c3b14d31aa" |
| + | "eth:0xc222ab08333109243B1f4E2a80e3D0A190714AB5" |
| } | |
The system has a centralized operator
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.
Users can force any transaction
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.
Regular exits
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 7d 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 3d 12h to complete. Finally the user submits an L1 transaction to claim the funds. This transaction requires a merkle proof.
Forced messaging
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.
EVM compatible smart contracts are supported
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..
Ethereum
Actors:
A Multisig with 3/3 threshold.
- Can upgrade with no delay
- ETHLockbox ProxyAdmin
- OptimismPortal2 ProxyAdmin
- DelayedWETH ProxyAdmin
- AnchorStateRegistry ProxyAdmin
- DisputeGameFactory ProxyAdmin
- L1StandardBridge ProxyAdmin
- L1CrossDomainMessenger ProxyAdmin
- OptimismMintableERC20Factory ProxyAdmin
- SystemConfig ProxyAdmin
- L1ERC721Bridge ProxyAdmin
- DelayedWETH ProxyAdmin
- Can interact with AddressManager
- set and change address mappings ProxyAdmin
A Multisig with 3/5 threshold.
- Can interact with SystemConfig
- it can update the preconfer address, 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 and the 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. configuration of the system
A Multisig with 5/7 threshold. It uses the following modules: SaferSafes (A Gnosis Safe module combining LivenessModule and TimelockGuard. Provides livenessLiveness refers to the ability of a system to respond to requests and to process them in a timely manner. In the context of L2s, it refers to the ability of settling transactions, proofs and state roots to the base layer. checks where a fallback owner can challenge and take over if Safe owners are unresponsive, plus optional timelock delays for transaction scheduling). Member of SuperchainProxyAdminOwner, UnichainProxyAdminOwner.
- Can interact with SuperchainConfig
- Allowed to pause withdrawals. In op stack systems with a proof systemThe infrastructure that allows projects to verify their state transitions. It is composed by onchain verifiers and offchain provers. The main two flavors are optimistic and ZK proof systems, but they can be combined in a hybrid model. In general though, if a system is able to accept state roots optimistically, even if it has a ZK component, it is considered an optimistic proof system., the Guardian can also blacklist dispute games and set the respected game type (permissioned / 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.) LivenessModule if the number of Optimism Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups. members falls below 8 → Optimism Security Council → Optimism Guardian Multisig
A Gnosis Safe module combining LivenessModule and TimelockGuard. Provides livenessLiveness refers to the ability of a system to respond to requests and to process them in a timely manner. In the context of L2s, it refers to the ability of settling transactions, proofs and state roots to the base layer. checks where a fallback owner can challenge and take over if Safe owners are unresponsive, plus optional timelock delays for transaction scheduling.
- Can interact with SuperchainConfig
- Allowed to pause withdrawals. In op stack systems with a proof systemThe infrastructure that allows projects to verify their state transitions. It is composed by onchain verifiers and offchain provers. The main two flavors are optimistic and ZK proof systems, but they can be combined in a hybrid model. In general though, if a system is able to accept state roots optimistically, even if it has a ZK component, it is considered an optimistic proof system., the Guardian can also blacklist dispute games and set the respected game type (permissioned / 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.) OpFoundationUpgradeSafe → LivenessModule if the number of Optimism Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups. members falls below 8 → Optimism Security Council → Optimism Guardian Multisig
A Multisig with 10/13 threshold. It uses the following modules: LivenessModule (used to remove members inactive for 3mo 8d while making sure that the threshold remains above 75%. If the number of members falls below 8, the OpFoundationUpgradeSafe takes ownership of the multisig). Member of Optimism Guardian Multisig, SuperchainProxyAdminOwner, UnichainProxyAdminOwner.
- Can interact with SuperchainConfig
- Allowed to pause withdrawals. In op stack systems with a proof systemThe infrastructure that allows projects to verify their state transitions. It is composed by onchain verifiers and offchain provers. The main two flavors are optimistic and ZK proof systems, but they can be combined in a hybrid model. In general though, if a system is able to accept state roots optimistically, even if it has a ZK component, it is considered an optimistic proof system., the Guardian can also blacklist dispute games and set the respected game type (permissioned / 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.) Optimism Guardian Multisig
Participants (13):
0xE61F…76aE0x652B…cB5f0x5c1f…7a810x4A73…e61E0x3A53…aa940xEF9A…877c0x6323…c8650xd5b7…aC900x7ed8…9E390x0aA3…75D70x0a87…efE60xbfA0…E0d90xcbC7…7eA6Modular contract to be used together with the LivenessModule. Tracks livenessLiveness refers to the ability of a system to respond to requests and to process them in a timely manner. In the context of L2s, it refers to the ability of settling transactions, proofs and state roots to the base layer. / activity of Safe owners.
- Can interact with LivenessModule
- can remove members of Optimism Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups. inactive for 3mo 8d
- Can interact with LivenessModule
- can remove members of Unichain Multisig 1 inactive for 2mo 10d
A Multisig with 1/1 threshold. It uses the following modules: DeputyPauseModule (Allows 0x2fA150379bF32b6d79Eeb4ff9bD280E76049a87c, called the deputy pauser, to act on behalf of the OpFoundationUpgradeSafe if set as its Safe module).
Participants (1):
Optimism Security CouncilA Multisig with 5/7 threshold. It uses the following modules: SaferSafes (A Gnosis Safe module combining LivenessModule and TimelockGuard. Provides livenessLiveness refers to the ability of a system to respond to requests and to process them in a timely manner. In the context of L2s, it refers to the ability of settling transactions, proofs and state roots to the base layer. checks where a fallback owner can challenge and take over if Safe owners are unresponsive, plus optional timelock delays for transaction scheduling).
A Multisig with 3/5 threshold. It uses the following modules: LivenessModule (used to remove members inactive for 2mo 10d while making sure that the threshold remains above 60%. If the number of members falls below 1, the 0x0000000000000000000000000000000000000000 takes ownership of the multisig). Member of UnichainProxyAdminOwner.
- Can interact with SystemConfig
- Allowed to commit transactions from the current layer to the host chain
- Can interact with SuperchainConfig
- Allowed to pause withdrawals. In op stack systems with a proof systemThe infrastructure that allows projects to verify their state transitions. It is composed by onchain verifiers and offchain provers. The main two flavors are optimistic and ZK proof systems, but they can be combined in a hybrid model. In general though, if a system is able to accept state roots optimistically, even if it has a ZK component, it is considered an optimistic proof system., the Guardian can also blacklist dispute games and set the respected game type (permissioned / 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.) DeputyPauseModule though restricted to the SuperchainConfig’s
pause()function → Optimism Guardian Multisig
- Allowed to pause withdrawals. In op stack systems with a proof systemThe infrastructure that allows projects to verify their state transitions. It is composed by onchain verifiers and offchain provers. The main two flavors are optimistic and ZK proof systems, but they can be combined in a hybrid model. In general though, if a system is able to accept state roots optimistically, even if it has a ZK component, it is considered an optimistic proof system., the Guardian can also blacklist dispute games and set the respected game type (permissioned / 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.) DeputyPauseModule though restricted to the SuperchainConfig’s
A Multisig with 2/2 threshold.
- Can upgrade with no delay
- SuperchainConfig SuperchainProxyAdmin
- Can interact with AddressManager
- set and change address mappings SuperchainProxyAdmin
Unichain
Actors:
- Can upgrade with no delay
- DeployerWhitelist L2ProxyAdmin
- L2CrossDomainMessenger L2ProxyAdmin
- GasPriceOracle L2ProxyAdmin
- L2StandardBridge L2ProxyAdmin
- SequencerFeeVault L2ProxyAdmin
- OptimismMintableERC20Factory L2ProxyAdmin
- L1BlockNumber L2ProxyAdmin
- L2ERC721Bridge L2ProxyAdmin
- L1Block L2ProxyAdmin
- L2ToL1MessagePasser L2ProxyAdmin
- OptimismMintableERC721Factory L2ProxyAdmin
- L2ProxyAdmin L2ProxyAdmin
- BaseFeeVault L2ProxyAdmin
- L1FeeVault L2ProxyAdmin
- SchemaRegistry L2ProxyAdmin
- EAS L2ProxyAdmin
Ethereum
used to remove members inactive for 3mo 8d while making sure that the threshold remains above 75%. If the number of members falls below 8, the OpFoundationUpgradeSafe takes ownership of the multisig
- Roles:
- fallbackOwner: OpFoundationUpgradeSafe if the number of Optimism Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups. members falls below 8
- livenessGuard: LivenessGuard
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 UnichainProxyAdminOwner
Simple escrow that accepts tokens and allows to configure permissioned addresses that can access the tokens.
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: UnichainProxyAdminOwner
used to remove members inactive for 2mo 10d while making sure that the threshold remains above 60%. If the number of members falls below 1, the 0x0000000000000000000000000000000000000000 takes ownership of the multisig
- Roles:
- livenessGuard: LivenessGuard
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.
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.
Lido custom escrow for wstETH tokens that uses the canonical 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. for messaging but is governed externally.
Allows 0x2fA150379bF32b6d79Eeb4ff9bD280E76049a87c, called the deputy pauser, to act on behalf of the OpFoundationUpgradeSafe if set as its Safe module.
- Roles:
- deputy: Optimism EOA 1 though restricted to the SuperchainConfig’s
pause()function
- deputy: Optimism EOA 1 though restricted to the SuperchainConfig’s
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 UnichainProxyAdminOwner
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 FaultDisputeGame.
- Roles:
- admin: ProxyAdmin; ultimately UnichainProxyAdminOwner
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 UnichainProxyAdminOwner
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 UnichainProxyAdminOwner
- batcherHash: EOA 1
- owner: Unichain Multisig 2
Used to manage global configuration values for multiple OP Chains within a single Superchain networkA constellation of nodes (peers) that communicate via a peer-to-peer protocol, for example, in propagating transactions and blocks to other nodes.. The SuperchainConfig contract manages individual 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 3 months if left untouched.
- Roles:
- admin: SuperchainProxyAdmin; ultimately SuperchainProxyAdminOwner
- guardian: Optimism Guardian Multisig; ultimately OpFoundationUpgradeSafe, Optimism EOA 1, Optimism Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups., SaferSafes
The main entry point to deposit ERC20 tokens from host chain to this chain.
- Roles:
- admin: ProxyAdmin; ultimately UnichainProxyAdminOwner
All supported tokens in this escrow are included in the value secured calculation.
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 UnichainProxyAdminOwner
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 UnichainProxyAdminOwner
A simple escrow contract storing ETH for the canonical 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..
- Roles:
- admin: ProxyAdmin; ultimately UnichainProxyAdminOwner
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 FaultDisputeGame.
- Roles:
- admin: ProxyAdmin; ultimately UnichainProxyAdminOwner
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 UnichainProxyAdminOwner
Unichain
Legacy contract that was originally used to act as a whitelist of addresses allowed to the Optimism networkA constellation of nodes (peers) that communicate via a peer-to-peer protocol, for example, in propagating transactions and blocks to other nodes.. Fully unused and deprecated since the Bedrock upgrade.
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
Simple contract that returns the latest 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. 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: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
Automatically collects ETH 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. and periodically bridges it back to Ethereum Layer 1Layer 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 a specified recipient address (0xa3d596EAfaB6B13Ab18D40FaE1A962700C84ADEa).
Automatically collects ETH 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. and periodically bridges it back to Ethereum Layer 1Layer 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 a specified recipient address (0x7078c4537C04c2b2E52ddBa06074dBdACF23cA15).
The L2CrossDomainMessenger (L2xDM) contract sends messages from 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. 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., and relays messages from L1 onto L2 with a system tx. In the event that a message sent from L2 to L1 is rejected for exceeding the L1 gas limitThe maximum amount of gas a transaction or block may consume., it can be resubmitted via this contract’s replay function.
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
Provides the current gas pricePrice of one unit of gas specified in a transaction. The token used to pay for gas is usually Ether, but rollups can use other custom tokens. for 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. transactions.
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
The L2StandardBridge contract is the main entry point to deposit or withdraw ERC20 tokens from 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. 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.. This contract can store any token.
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
Collects 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. fees, which are withdrawable to the FeesCollector 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..
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
Factory contract to create 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. compliant ERC20 IOU token representations of bridged 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. ERC20 tokens.
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
The L2ERC721Bridge contract is the main entry point to deposit or withdraw ERC721 tokens from 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. 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.. This contract can store any token.
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
Contract used internally by the L2CrossDomainMessenger to send messages 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., including withdrawals. It can also be used directly as a low-level interface.
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
Factory contract to create 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. compliant ERC721 IOU token representations of bridged 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. ERC721 tokens.
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
Administration contract for other contract proxies.
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
- owner: UnichainProxyAdminOwner_L2Alias
Collects EIP-1559 base fees, which are withdrawable to the FeesCollector 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..
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
Collects the 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. portion of 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. transaction fees, which are withdrawable to the FeesCollector on L1.
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
Contracts to register schemas for the Ethereum Attestation Service (EAS).
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
Contract containing the main logic for the Ethereum Attestation Service (EAS).
- Roles:
- admin: L2ProxyAdmin; ultimately UnichainProxyAdminOwner_L2Alias
The current deployment carries some associated risks:
Funds can be stolen if a contract receives a malicious code upgrade. Both regular and emergency upgrades must be approved by both the Security Council and the Foundation. There is no delay on regular upgrades.
Program Hashes
Name | Hash | Repository | Verification | Used in | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0x033c...bb6e | Projects used inSearch for projects used in | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Unichain