Risk Analysis

Show rollups only

Select type

Optimistic Rollup

Optimium

Plasma

Validium

ZK Rollup

Select stack

Arbitrum

Loopring

OP Stack

OVM

Polygon

StarkEx

Starknet

ZK Stack

zkSync Lite

No provider

Select stage

Not applicable

Stage 0

Stage 1

Stage 2

Under review

Select purpose

AMM

Bug bounty

DEX

DeFi

Exchange

Gaming

NFT

Payments

Privacy

Private payments

Universal

Active projectsActive36 Archived projectsArchived11

#	Name	State validation How is the validity of the system state checked?	Data availability Is the data needed to reconstruct the state available?	Exit window How much time do users have to exit the system in case of an unwanted upgrade?	Sequencer failure Sequencer is an entity responsible for constructing blocks and deciding on the ordering of user's transactions. What happens if it is offline or censors individual user?	Proposer failure Proposer is an entity responsible for submitting state commitments to Ethereum (optionally, along with the zkProof). What happens if it is offline?
1	Arbitrum One Fraud proof system is fully deployed but is not yet permissionless as it requires Validators to be whitelisted.	Fraud proofs (INT) Fraud proofs allow WHITELISTED actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks.	On chain All of the data needed for proof construction is published on chain.	2d The Security Council can upgrade with no delay. Upgrades are initiated on L2 and have to go first through a 3d delay. Since there is a 1d to force a tx, users have only 2d to exit. If users post a tx after that time, they would need to self propose a root with a 6d 8h delay and then wait for the 6d 8h challenge window, while the upgrade would be confirmed just after the 6d 8h challenge window and the 3d L1 timelock.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is a 1d delay on this operation.	Self propose Anyone can become a Proposer after 6d 8h of inactivity from the currently whitelisted Proposers.
2	OP Mainnet Fraud proof system is currently under development. Users need to trust block Proposer to submit correct L1 state roots.	In development Currently the system permits invalid state roots. More details in project overview.	On chain All of the data needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is a 12h delay on this operation.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
3	Manta Pacific Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	In development Currently the system permits invalid state roots. More details in project overview.	External Proof construction and state derivation fully rely on data that is posted on Celestia. Sequencer tx roots are not checked against the Blobstream bridge data roots onchain, but L2 nodes can verify data availability by running a Celestia light client.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is a 12h delay on this operation.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
4	Metis Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	In development Currently the system permits invalid state roots. More details in project overview.	Optimistic (MEMO) Transaction data is kept in MEMO decentralized storage. Validators can force Sequencer to make data available on-chain via L1 contract call if they find that Sequencer did not push tx data to MEMO. Challenge mechanizm is not yet fully implemented.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Enqueue via L1 Users can submit transactions to an L1 queue, but can't force them. The sequencer cannot selectively skip transactions but can stop processing the queue entirely. In other words, if the sequencer censors or is down, it is so for everyone.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
5	Base Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	In development Currently the system permits invalid state roots. More details in project overview.	On chain All of the data needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is a 12h delay on this operation.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
6	zkSync Era Withdrawals are delayed by 21h. The length of the delay can be arbitrarily set by a MultiSig.	ZK proofs Uses PLONK zero-knowledge proof system with KZG commitments.	On chain (SD) All of the data (SD = state diffs) needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Enqueue via L1 Users can submit transactions to an L1 queue, but can't force them. The sequencer cannot selectively skip transactions but can stop processing the queue entirely. In other words, if the sequencer censors or is down, it is so for everyone.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
7	Mantle Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	In development Currently the system permits invalid state roots. More details in project overview.	External Proof construction and state derivation rely fully on data that is NOT published on chain. MantleDA contracts are forked from EigenDA with significant modifications, most importantly removal of slashing conditions. DA fraud proof mechanism is not live yet.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Enqueue via L1 Users can submit transactions to an L1 queue, but can't force them. The sequencer cannot selectively skip transactions but can stop processing the queue entirely. In other words, if the sequencer censors or is down, it is so for everyone. The operators can also reset the batch index, effectively removing transactions from the chain from a certain point onwards.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
8	dYdX v3 This page describes dYdX v3, which is an L2 built on Ethereum. Recently deployed dYdX v4 is a separate blockchain based on Cosmos SDK, unrelated to Ethereum and is using different technology. No information on this page applies to dYdX v4.	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	On chain All of the data needed for proof construction is published on chain.	None There is no exit window. Upgrades have a 9d delay, (or 2d if shortened by the Priority Controller), but withdrawals can be censored for up to 14d.	Force via L1 Users can force the sequencer to include a trade or a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for 14d, users can use the exit hatch to withdraw their funds. Users are required to find a counterparty for the trade by out of system means.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds. Positions will be closed using the average price from the last batch state update.
9	ZKFair The forced transaction mechanism is currently disabled. The project claims to use CelestiaDA but smart contracts on L1 use DAC. Arbitrary messaging passing is removed from the bridge.	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	External (DAC) Proof construction relies fully on data that is NOT published on chain. There exists a data availability committee (DAC) that is tasked with protecting and supplying the data.	None The ZkFair Owner can upgrade with no delay. Even though there is a 1d Timelock for upgrades, forced transactions are disabled. Even if they were to be enabled, user withdrawals can be censored up to 15d.	No mechanism There is no mechanism to have transactions be included if the sequencer is down or censoring. Although the functionality exists in the code, it is currently disabled.	Self propose If the Proposer fails, users can leverage the source available prover to submit proofs to the L1 bridge. There is a 5d delay for proving and a 5d delay for finalizing state proven in this way. These delays can only be lowered except during the emergency state.
10	Linea The circuit of the program being proven is not public.	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain. Unlike most ZK rollups, transaction data is posted instead of state diffs.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	No mechanism There is no mechanism to have transactions be included if the sequencer is down or censoring.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
11	Immutable X	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	External (DAC) Proof construction relies fully on data that is NOT published on chain. There exists a data availability committee (DAC) that is tasked with protecting and supplying the data.	7d Users have 7d to exit funds in case of an unwanted upgrade. There is a 14d delay before an upgrade is applied, and withdrawals can take up to 7d to be processed.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for for more than 7d, users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds. NFTs will be minted on L1 to exit.
12	Starknet	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	On chain (SD) All of the data (SD = state diffs) needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	No mechanism There is no mechanism to have transactions be included if the sequencer is down or censoring.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
13	Loopring	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1 with a 0.02 ETH fee. If the sequencer is down for more than 15d, users can use the exit hatch to withdraw their funds. The sequencer can censor individual deposits, but in such case after 15d users can get their funds back.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds.
14	ApeX	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	External (DAC) Proof construction relies fully on data that is NOT published on chain. There exists a data availability committee (DAC) that is tasked with protecting and supplying the data.	7d Users have 7d to exit funds in case of an unwanted upgrade. There is a 14d delay before an upgrade is applied, and withdrawals can take up to 7d to be processed.	Force via L1 Users can force the sequencer to include a trade or a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for 7d, users can use the exit hatch to withdraw their funds. Users are required to find a counterparty for the trade by out of system means.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds. Positions will be closed using the average price from the last batch state update.
15	Polygon zkEVM The forced transaction mechanism is currently disabled.	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain. Unlike most ZK rollups transactions are posted instead of state diffs.	None The Security Council can upgrade with no delay. Even though there is a 10d Timelock for upgrades, forced transactions are disabled. Even if they were to be enabled, user withdrawals can be censored up to 15d.	No mechanism There is no mechanism to have transactions be included if the sequencer is down or censoring. Although the functionality exists in the code, it is currently disabled.	Self propose If the Proposer fails, users can leverage the source available prover to submit proofs to the L1 bridge. There is a 5d delay for proving and a 5d delay for finalizing state proven in this way. These delays can only be lowered except during the emergency state.
16	zkSync Lite	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	7d The Security Council can upgrade with no delay. Users have 7d to exit to exit funds in case of an unwanted upgrade. There is a 21d delay before an upgrade is applied, and withdrawals can take up to 14d to be processed.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for for more than 14d, users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a zero knowledge proof of funds.
17	Scroll	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	No mechanism There is no mechanism to have transactions be included if the sequencer is down or censoring.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
18	DeGate V1	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	30d Users have 30d to exit funds in case of an unwanted upgrade. There is a 45d delay before an upgrade is applied, and withdrawals can take up to 15d to be processed.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1 with a 0.01 ETH fee. If the sequencer is down for more than 15d, users can use the exit hatch to withdraw their funds. The sequencer can censor individual deposits, but in such case after 15d users can get their funds back.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds.
19	rhino.fi	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	External (DAC) Proof construction relies fully on data that is NOT published on chain. There exists a data availability committee (DAC) that is tasked with protecting and supplying the data.	7d Users have 7d to exit funds in case of an unwanted upgrade. There is a 14d delay before an upgrade is applied, and withdrawals can take up to 7d to be processed.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for for more than 7d, users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds.
20	Arbitrum Nova	Fraud proofs (INT) Fraud proofs allow WHITELISTED actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve.	External (DAC) Proof construction relies fully on data that is NOT published on chain. There exists a data availability committee (DAC) that is tasked with protecting and supplying the data.	2d The Security Council can upgrade with no delay. Upgrades are initiated on L2 and have to go first through a 3d delay. Since there is a 1d to force a tx, users have only 2d to exit. If users post a tx after that time, they would need to self propose a root with a 6d 8h delay and then wait for the 6d 8h challenge window, while the upgrade would be confirmed just after the 6d 8h challenge window and the 3d L1 timelock.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is a 1d delay on this operation.	Self propose Anyone can become a Proposer after 6d 8h of inactivity from the currently whitelisted Proposers.
21	Aevo Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	In development Currently the system permits invalid state roots. More details in project overview.	External Proof construction and state derivation fully rely on data that is posted on Celestia. Sequencer tx roots are not checked against the Blobstream bridge data roots onchain, but L2 nodes can verify data availability by running a Celestia light client.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is a 12h delay on this operation.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
22	Sorare	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	External (DAC) Proof construction relies fully on data that is NOT published on chain. There exists a data availability committee (DAC) that is tasked with protecting and supplying the data.	7d Users have 7d to exit funds in case of an unwanted upgrade. There is a 14d delay before an upgrade is applied, and withdrawals can take up to 7d to be processed.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for for more than 7d, users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds. NFTs will be minted on L1 to exit.
23	Boba Fraud proof system is currently under development. Users need to trust block Proposer to submit correct L1 state roots.	In development Currently the system permits invalid state roots. More details in project overview.	On chain All of the data needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Enqueue via L1 Users can submit transactions to an L1 queue, but can't force them. The sequencer cannot selectively skip transactions but can stop processing the queue entirely. In other words, if the sequencer censors or is down, it is so for everyone.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
24	Zora Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	In development Currently the system permits invalid state roots. More details in project overview.	On chain All of the data needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is a 12h delay on this operation.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
25	Lyra Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	In development Currently the system permits invalid state roots. More details in project overview.	On chain All of the data needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is a 12h delay on this operation.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
26	ZKSpace	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	5d Users have 5d to exit funds in case of an unwanted upgrade. There is a 8d delay before an upgrade is applied, and withdrawals can take up to 3d to be processed.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for for more than 3d, users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a zero knowledge proof of funds.
27	Paradex	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	On chain (SD) All of the data (SD = state diffs) needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	No mechanism There is no mechanism to have transactions be included if the sequencer is down or censoring.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
28	Kroma	Fraud proofs (INT, ZK) Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. ZK proofs are used to adjudicate the correctness of the last step. The challenge protocol can be subject to delay attacks and can fail under certain conditions. The current system doesn't use posted L2 txs batches on L1 as inputs to prove a fault, meaning that DA is not enforced.	On chain All of the data needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is a 12h delay on this operation.	Self propose Anyone can be a Proposer and propose new roots to the L1 bridge.
29	PGN Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	In development Currently the system permits invalid state roots. More details in project overview.	On chain All of the data needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is a 12h delay on this operation.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
30	tanX	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	External (DAC) Proof construction relies fully on data that is NOT published on chain. There exists a data availability committee (DAC) that is tasked with protecting and supplying the data.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for for more than 7d, users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds.
31	Myria	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	External (DAC) Proof construction relies fully on data that is NOT published on chain. There exists a data availability committee (DAC) that is tasked with protecting and supplying the data.	7d Users have 7d to exit funds in case of an unwanted upgrade. There is a 14d delay before an upgrade is applied, and withdrawals can take up to 7d to be processed.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for for more than 7d, users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds. NFTs will be minted on L1 to exit.
32	Parallel	Fraud proofs (INT) Fraud proofs allow WHITELISTED actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks.	On chain All of the data needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is a 1d delay on this operation.	Self propose Anyone can become a Proposer after 6d 8h of inactivity from the currently whitelisted Proposers.
33	Honeypot	None Currently the system permits invalid state roots. More details in project overview.	On chain All of the data needed for proof construction is published on chain.	∞ Users can exit funds at any time because contracts are not upgradeable.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. There is no delay on this operation.	Cannot withdraw Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
34	Canvas Connect Canvas Connect is currently open only to whitelisted institutional clients.	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	External (DAC) Proof construction relies fully on data that is NOT published on chain. There exists a data availability committee (DAC) that is tasked with protecting and supplying the data.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for for more than 7d, users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds. NFTs will be minted on L1 to exit.
35	ReddioEx	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	External (DAC) Proof construction relies fully on data that is NOT published on chain. There exists a data availability committee (DAC) that is tasked with protecting and supplying the data.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for for more than 7d, users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds. NFTs will be minted on L1 to exit.
36	Fuel v1	Fraud proofs (1R) Fraud proofs allow actors watching the chain to prove that the state is incorrect. Single round proofs (1R) only require a single transaction to resolve.	On chain All of the data needed for proof construction is published on chain.	∞ Users can exit funds at any time because contracts are not upgradeable.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1.	Self propose Anyone can be a Proposer and propose new roots to the L1 bridge.

#	Name	State validation How is the validity of the system state checked?	Data availability Is the data needed to reconstruct the state available?	Exit window How much time do users have to exit the system in case of an unwanted upgrade?	Sequencer failure Sequencer is an entity responsible for constructing blocks and deciding on the ordering of user's transactions. What happens if it is offline or censors individual user?	Proposer failure Proposer is an entity responsible for submitting state commitments to Ethereum (optionally, along with the zkProof). What happens if it is offline?
1	Zk.Money v2 (Aztec Connect) EOL: Aztec team announced they are going to shut down the rollup infrastructure on March 21st, 2024. The escape hatch delay has been recently increased to ~136 years, meaning that users will not be able to exit when the operator will be shut down.	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. Proposing new blocks requires creating ZK proofs.	Cannot withdraw Only the whitelisted proposers can publish L2 state roots on L1 within ~136 years from the last posted root, so in the event of failure the withdrawals are frozen.
2	Zk.Money v1 (Aztec v1) EOL: Aztec team announced the intent to shut down the infrastructure for this rollup on Mar 13, 2023. On Jan 14, 2024 TurboVerifier contract has been replaced with AlwaysReverting contract effectively halting verification process.	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	None 1/2 MSig can change Validator.	Self sequence In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1. Proposing new blocks requires creating ZK proofs.	Self propose If the Proposer fails, users can leverage the source available prover to submit proofs to the L1 bridge.
3	ZKSwap 1.0 This project contains unverified contracts. Version 3 of the protocol called ZkSpace is available and users are encouraged to move their assets there.	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	Unknown Some contracts are not verified, so there is no way to assess the exit window.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for , users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a zero knowledge proof of funds.
4	ZKSwap 2.0 This project contains unverified contracts. Version 3 of the protocol called ZkSpace is available and users are encouraged to move their assets there.	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	Unknown Some contracts are not verified, so there is no way to assess the exit window.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for , users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a zero knowledge proof of funds.
5	Polygon Hermez Hermez and Polygon have recently merged. Hermez and Polygon Hermez are two names for the same rollup.	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	7d Users have 7d to exit funds in case of an unwanted upgrade. There is a 7d delay before an upgrade is applied, and withdrawals can take up to 0s to be processed.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for , users can use the exit hatch to withdraw their funds.	Self propose If the Proposer fails, users can leverage the source available prover to submit proofs to the L1 bridge.
6	Layer2.Finance This project is under review. Currently the TVL is calculated incorrectly, because it does not take assets locked in DeFi into account.	In review	In review	In review	In review	In review
7	OMG Network This project contains unverified contracts.	Exits only Exits from the network are subject to a period when they can be challenged. The internal network state is left unchecked.	External Proof construction and state derivation rely fully on data that is NOT published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for , users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds. The details are unknown.
8	Gluon LeverJ trading platform appears to be in a maintenance mode as the team moved to build NFT trading platform. Social medias associated with the project are silent since mid 2021.	Fraud proofs (!) Fraud proofs allow actors watching the chain to prove that the state is incorrect. Because the data is not present on chain the security of fraud proofs is severely weakened.	External Proof construction and state derivation rely fully on data that is NOT published on chain.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for , users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds.
9	DeGate V1 Legacy	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	∞ Users can exit funds at any time because contracts are not upgradeable.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1 with a 0.01 ETH fee. If the sequencer is down for more than 15d, users can use the exit hatch to withdraw their funds. The sequencer can censor individual deposits, but in such case after 15d users can get their funds back.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds.
10	L2.Finance-zk This project contains unverified contracts. Layer2.finance-ZK has been shut down, users are encouraged to use optimistic rollup version.	ZK proofs (ST) zkSTARKS are zero knowledge proofs that ensure state correctness.	External (DAC) Proof construction relies fully on data that is NOT published on chain. There exists a data availability committee (DAC) that is tasked with protecting and supplying the data.	None There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1. If the sequencer censors or is down for , users can use the exit hatch to withdraw their funds.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds.
11	DeGate Legacy	ZK proofs (SN) zkSNARKS are zero knowledge proofs that ensure state correctness, but require trusted setup.	On chain All of the data needed for proof construction is published on chain.	∞ Users can exit funds at any time because contracts are not upgradeable.	Force via L1 Users can force the sequencer to include a withdrawal transaction by submitting a request through L1 with a 0.01 ETH fee. If the sequencer is down for more than 15d, users can use the exit hatch to withdraw their funds. The sequencer can censor individual deposits, but in such case after 15d users can get their funds back.	Use escape hatch Users are able to trustlessly exit by submitting a Merkle proof of funds.

Want to learn more about the different approaches to upgradeability?Check our report

About L2BEAT

L2BEAT is a public goods company dedicated to providing on-chain transparency.

What sets L2BEAT apart is our unwavering commitment to delivering accurate and reliable information. We strive to be an impartial and independent watchdog that acts in the best interest of users and the broader ecosystem while always remaining credibly neutral and faithful to reality and facts. We deliver data and tools that allow our community to educate themselves, transact securely, and make well-informed decisions.

This approach has earned us recognition and a solid reputation in the industry, garnering praise from the global Ethereum community and making our voice highly valued by numerous organizations and institutions. We are unafraid of being vocal and opinionated when our values are at stake.

Our work spans a wide range of areas, including:

Research and analysis of public protocols, including L2s and bridges,
Participation in protocol governance and security councils,
Development of transparency solutions like explorers,
Monitoring of smart contract upgrades,
Operation of nodes, and validators,
Publication of research reports,
Organization of conferences.

We receive generous funding from various public goods organizations, such as Gitcoin and the Ethereum Foundation, as well as from various private donors and investors. Additionally, we collaborate closely with leading companies in the space by accepting grants for specific projects.

You most likely have a lot of questions. We have created the Frequently Asked Questions page just for you.