Search for projects by name or address
Automata Network is an OP stack based Layer 2 Optimium acting as a modular attestation layer that extends machine-level trust to Ethereum with TEE Coprocessors and an EigenLayer AVS.
Automata Network is an OP stack based Layer 2 Optimium acting as a modular attestation layer that extends machine-level trust to Ethereum with TEE Coprocessors and an EigenLayer AVS.
Consequence: projects without a proper proof system fully rely on single entities to safely update the state. A malicious proposer can finalize an invalid state, which can cause loss of funds.
Consequence: projects without a data availability bridge fully rely on single entities (the sequencer) to honestly rely available data roots on Ethereum. A malicious sequencer can collude with the proposer to finalize an unavailable 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.
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.
Currently the system permits invalid state rootsA cryptographic hash succinctly representing a state using a Merkle tree.. More details in project overview.
Proof construction and state derivation rely fully on data that is NOT published onchain. A custom 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. (DA) provider without attestations is used, but data unavailability can be challenged.
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.
Automata DA is a 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. solution using data availability challenges (DA Challenges).
There are no onchain assets at risk of being slashed in case of a data withholding attack. However, there is a mechanism that allows users to challenge unavailability of data. The system is not secure if the malicious 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 able to outspend the altruistic challengers, and there is no pool of funds onchain to incentivize challengers.
There is no fraud detection mechanism in place. A data withholding attack can only be detected by nodes downloading the full data from the DA layerAn infrastructure that is used to make publish data so that it's available to the public. They take the form of Data Availability Committees (DACs) or blockchains. Not to confuse with the layer responsible with ordering, since ordering and DA can be separated..
The committee does not meet basic security standards, either due to insufficient size, lack of member diversity, or poorly defined threshold parameters. The system lacks an effective DA bridgeSystem that verifies that data has been made available. It takes the form of a smart contract verifying a consensus or, if the data is verified directly by either downloading the full data or sampling, of an enshrined bridge. and it is reliant on the assumption of an honest 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., creating significant risks to data integrity and availability.
There is no delay in the upgradeabilityThe ability for rollup smart contracts and parameters used in a rollup to be updated by holders of an admin key. Upgradeability represents a vector of risk for users, and should be decentralized and combined with time delays for greater security guarantees. of the 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.. Users have no time to exit the system before the bridge implementation update is completed.
The relayer role is permissioned, and the DA bridgeSystem that verifies that data has been made available. It takes the form of a smart contract verifying a consensus or, if the data is verified directly by either downloading the full data or sampling, of an enshrined bridge. does not have a 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. or a governance mechanism to propose new relayers. In case of relayer failure, the DA bridge will halt and be unable to recover without the intervention of a centralized entity.

Automata relies on DA challenges for data availability. The DA Provider submits an input commitment on Ethereum, and users can request the data behind the commitment off-chain from the DA Provider. If a DA challenger finds that the data behind a tx data commitment is not available, they can submit a challenge which requires locking a bond within 12h. A challenge can be resolved by publishing the preimage data within an additional 12h. In such case, a portion of the challenger bond is burned, with the exact amount estimated as the cost incurred by the resolver to publish the full data, meaning that the resolver and challenger will approximately lose the same amount of funds. The system is not secure if the malicious 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 able to outspend the altruistic challengers. If instead, after a challenge, the preimage data is not published, the chain reorgs to the last fully derivable state.
Only hashes of data batches are posted as DA commitments to an EOA on Ethereum. However, there is a mechanism that allows users to challenge unavailability of data.
Funds can be lost if the sequencer posts an invalid data availability certificate and there are no challengers.
Funds can be lost if the sequencer posts an invalid data availability certificate, and he is able to outspend the challengers.
OP Stack projects can use the OP fault 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., already being deployed on some. This project though is not using fault proofs yet and is relying on the honesty of the permissioned 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 Challengers to ensure state correctness. The smart contract system permits invalid state rootsA cryptographic hash succinctly representing a state using a Merkle tree..
Funds can be stolen if an invalid state root is submitted to the system (CRITICAL).
The metrics include upgrades on the currently used proxy contracts. Historical proxy contracts and changes of such are not included.
Automata paused on 2026-07-13; reason unknown. The guardian EOA ( 0xa5822fb7…41F4 ) called pause("shutdown") on the SuperchainConfigFake (tx); OptimismPortal, L1CrossDomainMessenger, L1StandardBridge, and L1ERC721Bridge all read paused: true through it.
Automata paused on 2026-07-13; reason unknown. The guardian EOA (0xa5822fb7…41F4) called pause("shutdown") on the SuperchainConfigFake (tx); OptimismPortal, L1CrossDomainMessenger, L1StandardBridge, and L1ERC721Bridge all read paused: true through it.
| contract L1ERC721Bridge (eth:0x00bd00c5C7F60e222D9CB8040270Ba929241A280) [opstack/L1ERC721Bridge] { | |
| +++ description: Used to bridge ERC-721 tokens from host chain to this chain. | |
| values.paused: | |
| - | false |
| + | true |
| } | |
| contract L1CrossDomainMessenger (eth:0x825C858149F1E775a0f4Aeb172037B970bE7B736) [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. | |
| values.paused: | |
| - | false |
| + | true |
| } | |
| contract OptimismPortal (eth:0xD52ba64CBE1e3B44167f810622fBef36bE24d95c) [opstack/OptimismPortal] { | |
| +++ description: The main entry point to deposit funds from host chain to this chain. It also allows to prove and finalize withdrawals. | |
| values.paused: | |
| - | false |
| + | true |
| } | |
| contract SuperchainConfig (eth:0xDf87154Ed6cF332931b70014bA3d9dF423074FfF) [opstack/SuperchainConfigFake] { | |
| +++ description: This is NOT the shared SuperchainConfig contract of the OP stack Superchain but rather a local fork. It manages the `PAUSED_SLOT`, a boolean value indicating whether the local chain is paused, and `GUARDIAN_SLOT`, the address of the guardian which can pause and unpause the system. | |
| values.paused: | |
| - | false |
| + | true |
| } | |
| contract L1StandardBridge (eth:0xE639919b92AB6DD238aEACc6F2A8d6e355D17bd5) [opstack/L1StandardBridge] { | |
| +++ description: The main entry point to deposit ERC20 tokens from host chain to this chain. | |
| values.paused: | |
| - | false |
| + | true |
| } | |
All four operator roles rotated: SystemConfig batcherHash + unsafeBlockSigner , L2OutputOracle proposer + challenger . Impl upgraded to AltL2OutputOracle ( 0xA9D7…BDF08 ) — a one-function extension that exposes updateProposerAndChallenger(address,address) gated by msg.sender == proposer , the only writable path for those slots in that impl — then reverted to standard L2OutputOracle ( 0xf315…9e3A ).
All four operator roles rotated: SystemConfig batcherHash + unsafeBlockSigner, L2OutputOracle proposer + challenger. Impl upgraded to AltL2OutputOracle (0xA9D7…BDF08) — a one-function extension that exposes updateProposerAndChallenger(address,address) gated by msg.sender == proposer, the only writable path for those slots in that impl — then reverted to standard L2OutputOracle (0xf315…9e3A).
| contract SystemConfig (eth:0x72934D7AEDC1A2d889ca89Aaf064CD9455E64d00) [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:0x12a593227Efb69EA634e2169E2c0A8246BB0B1B3" |
| + | "eth:0x5a5C3c981AE9299e080EF1647a781b1F3FbBdf63" |
| values.unsafeBlockSigner: | |
| - | "eth:0x373771221e39e1Ca16e981179CEcF1bE38ac70d9" |
| + | "eth:0xB08d817CfC56c76e6c09425602f04De68D63b993" |
| } | |
| contract L2OutputOracle (eth:0xdbf381984c4515Fe3285D3C55fDfb3054C52c261) [opstack/L2OutputOracle] { | |
| +++ description: Contains a list of proposed state roots which Proposers assert to be a result of block execution. Currently only the PROPOSER address can submit new state roots. | |
| values.$pastUpgrades.3: | |
| + | ["2026-06-08T03:16:11.000Z","0xa003ca066fdb6598a79aa97e782de066ec62723c27f34bca0664528f25e39b43",["eth:0xA9D78F579f1B30194F3c2Ca1987A9B91A33BDF08"]] |
| values.$pastUpgrades.4: | |
| + | ["2026-06-08T03:30:23.000Z","0x7c21d591fa80314fa93e0ae49c7af1d899267c941acc19a2a682723f09312305",["eth:0xf31575705C047eC4D3Eb05F0917B9aA404179e3A"]] |
| values.$upgradeCount: | |
| - | 3 |
| + | 5 |
| +++ severity: HIGH | |
| values.challenger: | |
| - | "eth:0xC3515A4bb0028E7548819df04160e2248d86eDE8" |
| + | "eth:0xa1237f7a46d407000ED5Fa07A5f17eE42Cc3392c" |
| values.CHALLENGER: | |
| - | "eth:0xC3515A4bb0028E7548819df04160e2248d86eDE8" |
| + | "eth:0xa1237f7a46d407000ED5Fa07A5f17eE42Cc3392c" |
| +++ severity: HIGH | |
| values.proposer: | |
| - | "eth:0x5B08eCA5C0cc5Ea1EBF03881c30EbF800f76F5a6" |
| + | "eth:0x1f8F34d0A3e8D721f8a05980Af19a7ba2E9Ec510" |
| values.PROPOSER: | |
| - | "eth:0x5B08eCA5C0cc5Ea1EBF03881c30EbF800f76F5a6" |
| + | "eth:0x1f8F34d0A3e8D721f8a05980Af19a7ba2E9Ec510" |
| } | |
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 (0x00bd00c5C7F60e222D9CB8040270Ba929241A280) | |
| +++ description: Used to bridge ERC-721 tokens from host chain to this chain. | |
| + | Status: CREATED |
| contract Automata Multisig 1 (0x03eC1C43434E2f910A2fb984906cd2470fdb39c8) | |
| +++ description: None | |
| + | Status: CREATED |
| contract DataAvailabilityChallenge (0x08c5DCDD5e46d31CC1591ee15b084663507597f3) | |
| +++ description: The DataAvailabilityChallenge contract is used to challenge the full availability of data behind commimted transaction data hashes. See the technology section for more details. | |
| + | Status: CREATED |
| contract Automata Multisig 2 (0x5E2FC552288857cfE709C398Ecac448314dE1320) | |
| +++ description: None | |
| + | Status: CREATED |
| contract SystemConfig (0x72934D7AEDC1A2d889ca89Aaf064CD9455E64d00) | |
| +++ description: Contains configuration parameters such as the Sequencer address, gas limit on this chain and the unsafe block signer address. | |
| + | Status: CREATED |
| contract ProxyAdmin (0x7617f4a55d62b9EE49578D9C90593e58E607415F) | |
| +++ description: None | |
| + | Status: CREATED |
| contract L1CrossDomainMessenger (0x825C858149F1E775a0f4Aeb172037B970bE7B736) | |
| +++ 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 OptimismMintableERC20Factory (0xa74b7baF04867E62B7824268e96144E503A23666) | |
| +++ 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 OptimismPortal (0xD52ba64CBE1e3B44167f810622fBef36bE24d95c) | |
| +++ description: The main entry point to deposit funds from host chain to this chain. It also allows to prove and finalize withdrawals. | |
| + | Status: CREATED |
| contract L2OutputOracle (0xdbf381984c4515Fe3285D3C55fDfb3054C52c261) | |
| +++ description: Contains a list of proposed state roots which Proposers assert to be a result of block execution. Currently only the PROPOSER address can submit new state roots. | |
| + | Status: CREATED |
| contract SuperchainConfig (0xDf87154Ed6cF332931b70014bA3d9dF423074FfF) | |
| +++ description: This is NOT the shared SuperchainConfig contract of the OP stack Superchain but rather a local fork. It manages the `PAUSED_SLOT`, a boolean value indicating whether the local chain is paused, and `GUARDIAN_SLOT`, the address of the guardian which can pause and unpause the system. | |
| + | Status: CREATED |
| contract L1StandardBridge (0xE639919b92AB6DD238aEACc6F2A8d6e355D17bd5) | |
| +++ description: The main entry point to deposit ERC20 tokens from host chain to this chain. | |
| + | Status: CREATED |
| contract AddressManager (0xF1C911e0c1E6dd08c8a7C80c9890e2037e0504c6) | |
| +++ 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. | |
Operators change, no change to implementations.
Operators change, no change to implementations.
| contract undefined (0x49eC5Bd8C9cC35Ce26b87E534d2E36980621dDD2) { | |
| +++ description: None | |
| receivedPermissions.1: | |
| - | {"permission":"interact","from":"0x08c5DCDD5e46d31CC1591ee15b084663507597f3","description":"can upgrade the parameters of DA challenges like the bond size or refund percentages, potentially making challenges infeasable or insecure."} |
| receivedPermissions.0.from: | |
| - | "0x72934D7AEDC1A2d889ca89Aaf064CD9455E64d00" |
| + | "0x08c5DCDD5e46d31CC1591ee15b084663507597f3" |
| receivedPermissions.0.description: | |
| - | "it can update the preconfer address, the batch submitter (Sequencer) address and the gas configuration of the system." |
| + | "can upgrade the parameters of DA challenges like the bond size or refund percentages, potentially making challenges infeasable or insecure." |
| receivedPermissions.0.via: | |
| - | [{"address":"0x5E2FC552288857cfE709C398Ecac448314dE1320"}] |
| } | |
| contract Automata Multisig 2 (0x5E2FC552288857cfE709C398Ecac448314dE1320) { | |
| +++ description: None | |
| directlyReceivedPermissions: | |
| - | [{"permission":"interact","from":"0x72934D7AEDC1A2d889ca89Aaf064CD9455E64d00","description":"it can update the preconfer address, the batch submitter (Sequencer) address and the gas configuration of the system."}] |
| values.$members.3: | |
| + | "0xB5b01E638CEF6AE50462A487d70005D6fe85eCf2" |
| values.$members.2: | |
| + | "0xa8AC7D03BEb92Fa3E6030AEB21629D00Ffb66dD7" |
| values.$members.1: | |
| + | "0x49eC5Bd8C9cC35Ce26b87E534d2E36980621dDD2" |
| values.$members.0: | |
| - | "0x49eC5Bd8C9cC35Ce26b87E534d2E36980621dDD2" |
| + | "0xaC79765A73eB9dcBd3c427181E6819902AE25b48" |
| values.$threshold: | |
| - | 1 |
| + | 3 |
| values.multisigThreshold: | |
| - | "1 of 1 (100%)" |
| + | "3 of 4 (75%)" |
| receivedPermissions: | |
| + | [{"permission":"interact","from":"0x72934D7AEDC1A2d889ca89Aaf064CD9455E64d00","description":"it can update the preconfer address, the batch submitter (Sequencer) address and the gas configuration of the system."}] |
| } | |
| contract SystemConfig (0x72934D7AEDC1A2d889ca89Aaf064CD9455E64d00) { | |
| +++ description: Contains configuration parameters such as the Sequencer address, gas limit on this chain and the unsafe block signer address. | |
| issuedPermissions.1.to: | |
| - | "0x49eC5Bd8C9cC35Ce26b87E534d2E36980621dDD2" |
| + | "0x5E2FC552288857cfE709C398Ecac448314dE1320" |
| issuedPermissions.1.via.0: | |
| - | {"address":"0x5E2FC552288857cfE709C398Ecac448314dE1320"} |
| issuedPermissions.0.to: | |
| - | "0x5BEF09f138921eF7985d83AAB97da1dB6E4dd190" |
| + | "0x12a593227Efb69EA634e2169E2c0A8246BB0B1B3" |
| values.batcherHash: | |
| - | "0x5BEF09f138921eF7985d83AAB97da1dB6E4dd190" |
| + | "0x12a593227Efb69EA634e2169E2c0A8246BB0B1B3" |
| values.unsafeBlockSigner: | |
| - | "0xA940a669DAe672111FD02Df597Cf7De7Cf758fAD" |
| + | "0x373771221e39e1Ca16e981179CEcF1bE38ac70d9" |
| } | |
| contract L2OutputOracle (0xdbf381984c4515Fe3285D3C55fDfb3054C52c261) { | |
| +++ description: Contains a list of proposed state roots which Proposers assert to be a result of block execution. Currently only the PROPOSER address can submit new state roots. | |
| issuedPermissions.1.to: | |
| - | "0x34Faa77b4D1686E399c96deF0de31D30572eaa9F" |
| + | "0xC3515A4bb0028E7548819df04160e2248d86eDE8" |
| issuedPermissions.0.to: | |
| - | "0x8c6F6580C846634C5DA08c40AE308DE23006a679" |
| + | "0x5B08eCA5C0cc5Ea1EBF03881c30EbF800f76F5a6" |
| values.$pastUpgrades.2: | |
| + | ["2025-04-05T09:19:11.000Z","0xbd8864ebf2f77f87a58470897b837b3003f982efa5d088b49a1373038e3da0df",["0xf31575705C047eC4D3Eb05F0917B9aA404179e3A"]] |
| values.$pastUpgrades.1: | |
| + | ["2025-04-05T09:01:59.000Z","0x92cdc220f2e504336fecf2a06ac21865e046c90315e6902d04597397628505b8",["0xA9D78F579f1B30194F3c2Ca1987A9B91A33BDF08"]] |
| values.$upgradeCount: | |
| - | 1 |
| + | 3 |
| +++ severity: HIGH | |
| values.challenger: | |
| - | "0x34Faa77b4D1686E399c96deF0de31D30572eaa9F" |
| + | "0xC3515A4bb0028E7548819df04160e2248d86eDE8" |
| values.CHALLENGER: | |
| - | "0x34Faa77b4D1686E399c96deF0de31D30572eaa9F" |
| + | "0xC3515A4bb0028E7548819df04160e2248d86eDE8" |
| +++ severity: HIGH | |
| values.proposer: | |
| - | "0x8c6F6580C846634C5DA08c40AE308DE23006a679" |
| + | "0x5B08eCA5C0cc5Ea1EBF03881c30EbF800f76F5a6" |
| values.PROPOSER: | |
| - | "0x8c6F6580C846634C5DA08c40AE308DE23006a679" |
| + | "0x5B08eCA5C0cc5Ea1EBF03881c30EbF800f76F5a6" |
| } | |
Automata adds an EOA as SystemConfig owner.
Automata adds an EOA as SystemConfig owner.
| contract SystemConfig (0x72934D7AEDC1A2d889ca89Aaf064CD9455E64d00) { | |
| +++ description: Contains configuration parameters such as the Sequencer address, gas limit on this chain and the unsafe block signer address. | |
| issuedPermissions.0.via.0: | |
| + | {"address":"0x5E2FC552288857cfE709C398Ecac448314dE1320"} |
| values.owner: | |
| - | "0x49eC5Bd8C9cC35Ce26b87E534d2E36980621dDD2" |
| + | "0x5E2FC552288857cfE709C398Ecac448314dE1320" |
| } | |
| + | Status: CREATED |
| contract AutomataOpsMultisig (0x5E2FC552288857cfE709C398Ecac448314dE1320) | |
| +++ description: None | |
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 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. messages by submitting a regular transaction on this chain. When the 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. containing that transaction is settled, the message becomes available for processing on L1. The process of block finalization 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 7d to complete.
Funds can be frozen if the centralized validator goes down. Users cannot produce blocks themselves and exiting the system requires new block production (CRITICAL).
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/4 threshold.
A Multisig with 3/4 threshold.
Member of Automata Multisig 2.


The DataAvailabilityChallenge contract is used to challenge the full availability of data behind commimted transaction data hashes. See the technology section for more details.
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.
The main entry point to deposit funds from host chain to this chain. It also allows to prove and finalize withdrawals.

Contains a list of proposed state rootsA cryptographic hash succinctly representing a state using a Merkle tree. which Proposers assert to be a result of blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. execution. Currently only the 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. address can submit new state roots.
This is NOT the shared SuperchainConfig contract of the OP stack Superchain but rather a local fork. It manages the PAUSED_SLOT, a boolean value indicating whether the local chain is paused, and GUARDIAN_SLOT, the address of the guardian which can pause and unpause the system.
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.
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.
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.
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.
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).