Liveness

Please note, the values on the page do not reflect the time to finality (the time it would take for your L2 transaction to be finalized on the L1 after it has been submitted).

Type

Optimistic Rollup

ZK Rollup

Type

Optimistic Rollup

ZK Rollup

Stack

Arbitrum

Loopring

OP Stack

Polygon

StarkEx

Starknet

ZK Stack

zkSync Lite

No provider

Stack

Arbitrum

Loopring

OP Stack

Polygon

StarkEx

Starknet

ZK Stack

zkSync Lite

No provider

Stage

Stage 0

Stage 1

Stage 2

Stage

Stage 0

Stage 1

Stage 2

Purpose

AMM

Bug bounty

DeFi

Exchange

Information

NFT

Payments

Universal

Purpose

AMM

Bug bounty

DeFi

Exchange

Information

NFT

Payments

Universal

30D90DMAX

		30-day average intervals 90-day average intervals all-time average intervals
#	Name	Tx data submissions How often transaction batches are submitted to the L1	Proof submissions How often validity proofs are submitted to the L1	State updates How often state roots are submitted to the L1	TypeType Type of this project. Determines data availability and proof system used. ZK Rollups = Validity Proofs + onchain data Optimistic Rollups = Fraud Proofs + onchain data	30-day anomalies Anomalies are based on a Z-score. It measures how far away a data point is from a 30-day rolling average. We consider as anomalies the data points with Z-score > 15.
1	Arbitrum One Fraud proof system is fully deployed but is not yet permissionless as it requires Validators to be whitelisted.	4 minutes 30-day intervals: Minimum: 12 seconds Average: 4 minutes Maximum: 16 minutes 3 minutes 90-day intervals: Minimum: 12 seconds Average: 3 minutes Maximum: 26 minutes 2 minutes All-time intervals: Minimum: 12 seconds Average: 2 minutes Maximum: 1 hour	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	1 hour 30-day intervals: Minimum: 33 minutes Average: 1 hour Maximum: 1 hour Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 1 hour 90-day intervals: Minimum: 33 minutes Average: 1 hour Maximum: 2 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 1 hour All-time intervals: Minimum: 12 seconds Average: 1 hour Maximum: 3 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes.	Optimistic Rollup This project is based on Arbitrum's code base.	Anomalies from last 30 days: 2024 April 20, 07:08 (UTC) STATE UPDATEDuration: 1 hour 2024 April 13, 20:38 (UTC) STATE UPDATEDuration: 1 hour	Arbitrum One is an Optimistic rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted on L1. Forced txs can be delayed up to 1d. The state root gets finalized 6d 8h after it has been posted.
2	OP Mainnet Fraud proof system is currently under development. Users need to trust block Proposer to submit correct L1 state roots.	4 minutes 30-day intervals: Minimum: 12 seconds Average: 4 minutes Maximum: 44 minutes 2 minutes 90-day intervals: Minimum: 12 seconds Average: 2 minutes Maximum: 44 minutes 2 minutes All-time intervals: Minimum: 12 seconds Average: 2 minutes Maximum: 44 minutes	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	1 hour 30-day intervals: Minimum: 38 minutes Average: 1 hour Maximum: 1 hour Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 1 hour 90-day intervals: Minimum: 38 minutes Average: 1 hour Maximum: 1 hour Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 1 hour All-time intervals: Minimum: 19 minutes Average: 1 hour Maximum: 1 hour Please note, for Optimistic rollups the state is not finalized until the challenge period passes.	Optimistic Rollup This project is based on OP Stack's code base.	Anomalies from last 30 days: 2024 April 11, 21:36 (UTC) TX DATA SUBMISSIONDuration: 44 minutes	OP Mainnet is an Optimistic rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted within a tx batch on L1 that links to a previous finalized batch. If the previous batch is missing, transaction finalization can be delayed up to 12h or until it gets published. The state root gets finalized 7d after it has been posted.
3	Base Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	2 minutes 30-day intervals: Minimum: 12 seconds Average: 2 minutes Maximum: 47 minutes 1 minute 90-day intervals: Minimum: 12 seconds Average: 1 minute Maximum: 47 minutes 1 minute All-time intervals: Minimum: 12 seconds Average: 1 minute Maximum: 47 minutes	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	1 hour 30-day intervals: Minimum: 12 minutes Average: 1 hour Maximum: 1 hour Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 1 hour 90-day intervals: Minimum: 12 minutes Average: 1 hour Maximum: 1 hour Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 59 minutes All-time intervals: Minimum: 1 minute Average: 59 minutes Maximum: 2 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes.	Optimistic Rollup This project is based on OP Stack's code base.	Anomalies from last 30 days: 2024 April 04, 20:07 (UTC) TX DATA SUBMISSIONDuration: 47 minutes	Base is an Optimistic rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted within a tx batch on L1 that links to a previous finalized batch. If the previous batch is missing, transaction finalization can be delayed up to 12h or until it gets published. The state root gets finalized 7d after it has been posted.
4	Blast Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	1 minute 30-day intervals: Minimum: 12 seconds Average: 1 minute Maximum: 11 minutes 2 minutes 90-day intervals: Minimum: 12 seconds Average: 2 minutes Maximum: 1 hour 2 minutes All-time intervals: Minimum: 12 seconds Average: 2 minutes Maximum: 1 hour	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	1 hour 30-day intervals: Minimum: 43 minutes Average: 1 hour Maximum: 1 hour Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 59 minutes 90-day intervals: Minimum: 2 minutes Average: 59 minutes Maximum: 1 hour Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 59 minutes All-time intervals: Minimum: 2 minutes Average: 59 minutes Maximum: 1 hour Please note, for Optimistic rollups the state is not finalized until the challenge period passes.	Optimistic Rollup This project is based on OP Stack's code base.	No anomalies detected in the last 30 days	Blast is an Optimistic rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted within a tx batch on L1 that links to a previous finalized batch. If the previous batch is missing, transaction finalization can be delayed up to 12h or until it gets published. The state root gets finalized 12d after it has been posted.
5	Starknet	n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1.	8 hours 30-day intervals: Minimum: 2 hours Average: 8 hours Maximum: 10 hours 2 hours 90-day intervals: Minimum: 8 minutes Average: 2 hours Maximum: 10 hours 1 hour All-time intervals: Minimum: 8 minutes Average: 1 hour Maximum: 11 hours	5 minutes 30-day intervals: Minimum: 12 seconds Average: 5 minutes Maximum: 9 hours 3 minutes 90-day intervals: Minimum: 12 seconds Average: 3 minutes Maximum: 10 hours 1 minute All-time intervals: Minimum: 12 seconds Average: 1 minute Maximum: 13 hours	ZK Rollup This project is based on Starknet's code base.	Coming soon	Starknet is a ZK rollup that posts state diffs to the L1. For a transaction to be considered final, the state diffs have to be submitted and validity proof should be generated, submitted, and verified. Proofs are aggregated with other projects using SHARP and state updates have to refer to proved claims.
6	zkSync Era Withdrawals are delayed by 21h. The length of the delay can be arbitrarily set by a MultiSig.	n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1.	11 minutes 30-day intervals: Minimum: 12 seconds Average: 11 minutes Maximum: 7 hours 7 minutes 90-day intervals: Minimum: 12 seconds Average: 7 minutes Maximum: 13 hours 4 minutes All-time intervals: Minimum: 12 seconds Average: 4 minutes Maximum: 14 hours	2 hours 30-day intervals: Minimum: 12 seconds Average: 2 hours Maximum: 8 hours 47 minutes 90-day intervals: Minimum: 12 seconds Average: 47 minutes Maximum: 8 hours 43 minutes All-time intervals: Minimum: 12 seconds Average: 43 minutes Maximum: 13 hours	ZK Rollup This project is based on ZK Stack's code base.	No anomalies detected in the last 30 days	zkSync Era is a ZK rollup that posts state diffs to the L1. Transactions within a state diff can be considered final when proven on L1 using a ZK proof, except that an operator can revert them if not executed yet. Currently, there is at least a 21h delay between state diffs verification and the execution of the corresponding state actions.
7	Linea The circuit of the program being proven is not public.	2 minutes 30-day intervals: Minimum: 12 seconds Average: 2 minutes Maximum: 25 hours 4 minutes 90-day intervals: Minimum: 12 seconds Average: 4 minutes Maximum: 25 hours 4 minutes All-time intervals: Minimum: 12 seconds Average: 4 minutes Maximum: 25 hours	32 minutes 30-day intervals: Minimum: 12 seconds Average: 32 minutes Maximum: 24 hours 10 minutes 90-day intervals: Minimum: 12 seconds Average: 10 minutes Maximum: 27 hours 2 minutes All-time intervals: Minimum: 12 seconds Average: 2 minutes Maximum: 2 days	32 minutes 30-day intervals: Minimum: 12 seconds Average: 32 minutes Maximum: 24 hours 10 minutes 90-day intervals: Minimum: 12 seconds Average: 10 minutes Maximum: 27 hours 2 minutes All-time intervals: Minimum: 12 seconds Average: 2 minutes Maximum: 2 days	ZK Rollup	Coming soon	Linea is a ZK rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted on L1. Tx data, proofs and state roots are currently posted in the same transaction. Blocks can also be finalized by the operator without the need to provide a proof.
8	Mode Network Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	55 minutes 30-day intervals: Minimum: 12 seconds Average: 55 minutes Maximum: 2 hours 14 minutes 90-day intervals: Minimum: 12 seconds Average: 14 minutes Maximum: 3 hours 12 minutes All-time intervals: Minimum: 12 seconds Average: 12 minutes Maximum: 3 hours	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	1 hour 30-day intervals: Minimum: 24 seconds Average: 1 hour Maximum: 2 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 1 hour 90-day intervals: Minimum: 24 seconds Average: 1 hour Maximum: 3 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 1 hour All-time intervals: Minimum: 24 seconds Average: 1 hour Maximum: 3 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes.	Optimistic Rollup This project is based on OP Stack's code base.	No anomalies detected in the last 30 days	Mode Network is an Optimistic rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted within a tx batch on L1 that links to a previous finalized batch. If the previous batch is missing, transaction finalization can be delayed up to 12h or until it gets published. The state root gets finalized 7d after it has been posted.
9	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.	n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1.	2 hours 30-day intervals: Minimum: 12 seconds Average: 2 hours Maximum: 7 hours 2 hours 90-day intervals: Minimum: 12 seconds Average: 2 hours Maximum: 7 hours 1 hour All-time intervals: Minimum: 12 seconds Average: 1 hour Maximum: 7 hours	2 hours 30-day intervals: Minimum: 12 seconds Average: 2 hours Maximum: 7 hours 2 hours 90-day intervals: Minimum: 12 seconds Average: 2 hours Maximum: 7 hours 1 hour All-time intervals: Minimum: 12 seconds Average: 1 hour Maximum: 7 hours	ZK Rollup This project is built using StarkEx.	No anomalies detected in the last 30 days	dYdX is a ZK rollup that posts state diffs to the L1. For a transaction to be considered final, the state diffs have to be submitted and validity proof should be generated, submitted, and verified. The verification is done as part of the state update.
10	Scroll	1 minute 30-day intervals: Minimum: 12 seconds Average: 1 minute Maximum: 28 minutes Transaction data batches that have not yet been proven can be reverted. 1 minute 90-day intervals: Minimum: 12 seconds Average: 1 minute Maximum: 28 minutes Transaction data batches that have not yet been proven can be reverted. 1 minute All-time intervals: Minimum: 12 seconds Average: 1 minute Maximum: 49 minutes Transaction data batches that have not yet been proven can be reverted.	1 minute 30-day intervals: Minimum: 12 seconds Average: 1 minute Maximum: 4 hours 1 minute 90-day intervals: Minimum: 12 seconds Average: 1 minute Maximum: 4 hours 1 minute All-time intervals: Minimum: 12 seconds Average: 1 minute Maximum: 4 hours	1 minute 30-day intervals: Minimum: 12 seconds Average: 1 minute Maximum: 4 hours 1 minute 90-day intervals: Minimum: 12 seconds Average: 1 minute Maximum: 4 hours 1 minute All-time intervals: Minimum: 12 seconds Average: 1 minute Maximum: 4 hours	ZK Rollup	Anomalies from last 30 days: 2024 April 24, 03:55 (UTC) STATE UPDATEDuration: 55 minutes 2024 April 23, 10:37 (UTC) STATE UPDATEDuration: 1 hour 2024 April 23, 03:45 (UTC) STATE UPDATEDuration: 52 minutes 2024 April 15, 21:07 (UTC) STATE UPDATEDuration: 56 minutes And 7 more	Scroll is a ZK rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted on L1, but the owner can revert them if the corresponding root has not yet be confirmed.
11	Polygon zkEVM The forced transaction mechanism is currently disabled.	23 minutes 30-day intervals: Minimum: 24 seconds Average: 23 minutes Maximum: 1 hour 20 minutes 90-day intervals: Minimum: 24 seconds Average: 20 minutes Maximum: 13 hours 9 minutes All-time intervals: Minimum: 12 seconds Average: 9 minutes Maximum: 13 hours	18 minutes 30-day intervals: Minimum: 12 seconds Average: 18 minutes Maximum: 2 hours 30 minutes 90-day intervals: Minimum: 12 seconds Average: 30 minutes Maximum: 3 hours 31 minutes All-time intervals: Minimum: 12 seconds Average: 31 minutes Maximum: 4 hours	18 minutes 30-day intervals: Minimum: 12 seconds Average: 18 minutes Maximum: 2 hours 30 minutes 90-day intervals: Minimum: 12 seconds Average: 30 minutes Maximum: 3 hours 31 minutes All-time intervals: Minimum: 12 seconds Average: 31 minutes Maximum: 4 hours	ZK Rollup This project is based on Polygon's code base.	No anomalies detected in the last 30 days	Polygon zkEVM is a ZK rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted on L1. State updates are a three step process: first blocks are committed to L1, then they are proved, and then it is possible to execute them.
12	Loopring	n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1.	50 minutes 30-day intervals: Minimum: 12 seconds Average: 50 minutes Maximum: 8 hours 51 minutes 90-day intervals: Minimum: 12 seconds Average: 51 minutes Maximum: 8 hours 49 minutes All-time intervals: Minimum: 12 seconds Average: 49 minutes Maximum: 8 hours	50 minutes 30-day intervals: Minimum: 12 seconds Average: 50 minutes Maximum: 8 hours 51 minutes 90-day intervals: Minimum: 12 seconds Average: 51 minutes Maximum: 8 hours 49 minutes All-time intervals: Minimum: 12 seconds Average: 49 minutes Maximum: 8 hours	ZK Rollup This project is based on Loopring's code base.	No anomalies detected in the last 30 days	Loopring is a ZK rollup that posts state diffs to the L1. For a transaction to be considered final, the state diffs have to be submitted and validity proof should be generated, submitted, and verified.
13	zkSync Lite	n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1.	1 hour 30-day intervals: Minimum: 3 minutes Average: 1 hour Maximum: 5 hours 49 minutes 90-day intervals: Minimum: 12 seconds Average: 49 minutes Maximum: 5 hours 21 minutes All-time intervals: Minimum: 12 seconds Average: 21 minutes Maximum: 6 hours	2 hours 30-day intervals: Minimum: 4 minutes Average: 2 hours Maximum: 5 hours 1 hour 90-day intervals: Minimum: 48 seconds Average: 1 hour Maximum: 5 hours 26 minutes All-time intervals: Minimum: 12 seconds Average: 26 minutes Maximum: 6 hours	ZK Rollup This project is based on zkSync Lite's code base.	No anomalies detected in the last 30 days	zkSync Lite is a ZK rollup that posts state diffs to the L1. Transactions within a state diff can be considered final when proven on L1 using a ZK proof, except that an operator can revert them if not executed yet.
14	DeGate V1	n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1.	1 hour 30-day intervals: Minimum: 4 minutes Average: 1 hour Maximum: 7 hours 1 hour 90-day intervals: Minimum: 12 seconds Average: 1 hour Maximum: 7 hours 1 hour All-time intervals: Minimum: 12 seconds Average: 1 hour Maximum: 12 hours	1 hour 30-day intervals: Minimum: 4 minutes Average: 1 hour Maximum: 7 hours 1 hour 90-day intervals: Minimum: 12 seconds Average: 1 hour Maximum: 7 hours 1 hour All-time intervals: Minimum: 12 seconds Average: 1 hour Maximum: 12 hours	ZK Rollup This project is based on Loopring's code base.	No anomalies detected in the last 30 days	DeGate is a ZK rollup based on Loopring’s code base that posts state diffs to the L1. For a transaction to be considered final, the state diffs have to be submitted and validity proof should be generated, submitted, and verified.
15	Zora Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	26 minutes 30-day intervals: Minimum: 12 seconds Average: 26 minutes Maximum: 2 hours 13 minutes 90-day intervals: Minimum: 12 seconds Average: 13 minutes Maximum: 3 hours 10 minutes All-time intervals: Minimum: 12 seconds Average: 10 minutes Maximum: 3 hours	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	1 hour 30-day intervals: Minimum: 12 seconds Average: 1 hour Maximum: 2 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 1 hour 90-day intervals: Minimum: 12 seconds Average: 1 hour Maximum: 4 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 58 minutes All-time intervals: Minimum: 12 seconds Average: 58 minutes Maximum: 4 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes.	Optimistic Rollup This project is based on OP Stack's code base.	No anomalies detected in the last 30 days	Zora is an Optimistic rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted within a tx batch on L1 that links to a previous finalized batch. If the previous batch is missing, transaction finalization can be delayed up to 12h or until it gets published. The state root gets finalized 7d after it has been posted.
16	RSS3 Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	10 minutes 30-day intervals: Minimum: 7 minutes Average: 10 minutes Maximum: 3 hours 10 minutes 90-day intervals: Minimum: 1 minute Average: 10 minutes Maximum: 3 hours 10 minutes All-time intervals: Minimum: 1 minute Average: 10 minutes Maximum: 3 hours	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	1 hour 30-day intervals: Minimum: 2 minutes Average: 1 hour Maximum: 3 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 59 minutes 90-day intervals: Minimum: 2 minutes Average: 59 minutes Maximum: 3 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 59 minutes All-time intervals: Minimum: 2 minutes Average: 59 minutes Maximum: 3 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes.	Optimistic Rollup This project is based on OP Stack's code base.	No anomalies detected in the last 30 days	RSS3 Value Sublayer is an Optimistic rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted within a tx batch on L1 that links to a previous finalized batch. If the previous batch is missing, transaction finalization can be delayed up to 12h or until it gets published. The state root gets finalized 7d after it has been posted.
17	Boba Fraud proof system is currently under development. Users need to trust the block proposer to submit correct L1 state roots.	42 minutes 30-day intervals: Minimum: 10 minutes Average: 42 minutes Maximum: 3 hours 52 minutes 90-day intervals: Minimum: 10 minutes Average: 52 minutes Maximum: 3 hours 57 minutes All-time intervals: Minimum: 10 minutes Average: 57 minutes Maximum: 4 hours	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	56 minutes 30-day intervals: Minimum: 1 minute Average: 56 minutes Maximum: 4 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 59 minutes 90-day intervals: Minimum: 1 minute Average: 59 minutes Maximum: 4 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 1 hour All-time intervals: Minimum: 1 minute Average: 1 hour Maximum: 4 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes.	Optimistic Rollup This project is based on OP Stack's code base.	No anomalies detected in the last 30 days	Boba Network is an Optimistic rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted within a tx batch on L1 that links to a previous finalized batch. If the previous batch is missing, transaction finalization can be delayed up to 12h or until it gets published. The state root gets finalized 7d after it has been posted.
18	Kroma	10 minutes 30-day intervals: Minimum: 4 minutes Average: 10 minutes Maximum: 1 hour 11 minutes 90-day intervals: Minimum: 1 minute Average: 11 minutes Maximum: 7 hours 11 minutes All-time intervals: Minimum: 12 seconds Average: 11 minutes Maximum: 7 hours	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	1 hour 30-day intervals: Minimum: 2 minutes Average: 1 hour Maximum: 2 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 1 hour 90-day intervals: Minimum: 12 seconds Average: 1 hour Maximum: 8 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 1 hour All-time intervals: Minimum: 12 seconds Average: 1 hour Maximum: 8 hours Please note, for Optimistic rollups the state is not finalized until the challenge period passes.	Optimistic Rollup This project is based on OP Stack's code base.	Anomalies from last 30 days: 2024 April 01, 05:45 (UTC) TX DATA SUBMISSIONDuration: 1 hour	Kroma is an Optimistic rollup that posts transaction data to the L1. For a transaction to be considered final, it has to be posted within a tx batch on L1 that links to a previous finalized batch. If the previous batch is missing, transaction finalization can be delayed up to 12h or until it gets published. The state root gets finalized 7d after it has been posted.
19	Kinto Fraud proof system is fully deployed but is not yet permissionless as it requires Validators to be whitelisted.	1 hour 30-day intervals: Minimum: 35 minutes Average: 1 hour Maximum: 7 hours 1 hour 90-day intervals: Minimum: 1 minute Average: 1 hour Maximum: 13 hours 1 hour All-time intervals: Minimum: 1 minute Average: 1 hour Maximum: 5 days	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	5 hours 30-day intervals: Minimum: 59 minutes Average: 5 hours Maximum: 7 hours 1 hour 90-day intervals: Minimum: 12 seconds Average: 1 hour Maximum: 22 hours 2 hours All-time intervals: Minimum: 12 seconds Average: 2 hours Maximum: 5 days	Optimistic Rollup This project is based on Arbitrum's code base.	Anomalies from last 30 days: 2024 April 13, 23:20 (UTC) TX DATA SUBMISSIONDuration: 7 hours
20	Paradex	n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1.	8 hours 30-day intervals: Minimum: 2 hours Average: 8 hours Maximum: 10 hours 2 hours 90-day intervals: Minimum: 8 minutes Average: 2 hours Maximum: 10 hours 1 hour All-time intervals: Minimum: 5 minutes Average: 1 hour Maximum: 10 hours	8 minutes 30-day intervals: Minimum: 12 seconds Average: 8 minutes Maximum: 9 hours 11 minutes 90-day intervals: Minimum: 12 seconds Average: 11 minutes Maximum: 10 hours 15 minutes All-time intervals: Minimum: 12 seconds Average: 15 minutes Maximum: 10 days	ZK Rollup This project is based on Starknet's code base.	No anomalies detected in the last 30 days	Paradex is a ZK rollup that posts state diffs to the L1. For a transaction to be considered final, the state diffs have to be submitted and validity proof should be generated, submitted, and verified. Proofs are aggregated with other projects using SHARP and state updates have to refer to proved claims.
21	ZKSpace	n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1. n/a State diff rollups do not post batches of transactions to the L1.	2 days 30-day intervals: Minimum: 10 hours Average: 2 days Maximum: 7 days 28 hours 90-day intervals: Minimum: 6 hours Average: 28 hours Maximum: 7 days 2 hours All-time intervals: Minimum: 12 seconds Average: 2 hours Maximum: 7 days	2 days 30-day intervals: Minimum: 10 hours Average: 2 days Maximum: 7 days 28 hours 90-day intervals: Minimum: 6 hours Average: 28 hours Maximum: 7 days 2 hours All-time intervals: Minimum: 12 seconds Average: 2 hours Maximum: 7 days	ZK Rollup This project is based on zkSync Lite's code base.	No anomalies detected in the last 30 days	ZK Space is a ZK rollup based on zkSync Lite’s code base that posts state diffs to the L1. For a transaction to be considered final, the state diffs have to be submitted and validity proof should be generated, submitted, and verified.
22	Parallel Fraud proof system is fully deployed but is not yet permissionless as it requires Validators to be whitelisted.	6 hours 30-day intervals: Minimum: 52 minutes Average: 6 hours Maximum: 36 hours 2 hours 90-day intervals: Minimum: 26 minutes Average: 2 hours Maximum: 36 hours 3 hours All-time intervals: Minimum: 26 minutes Average: 3 hours Maximum: 4 days	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	3 hours 30-day intervals: Minimum: 55 minutes Average: 3 hours Maximum: 36 hours 2 hours 90-day intervals: Minimum: 22 minutes Average: 2 hours Maximum: 2 days 2 hours All-time intervals: Minimum: 22 minutes Average: 2 hours Maximum: 4 days	Optimistic Rollup This project is based on Arbitrum's code base.	Anomalies from last 30 days: 2024 April 08, 03:32 (UTC) STATE UPDATEDuration: 36 hours 2024 April 02, 02:18 (UTC) TX DATA SUBMISSIONDuration: 36 hours
23	Honeypot	n/a n/a n/a	n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1. n/a Optimistic rollups do not post validity proofs to the L1.	7 days 30-day intervals: Minimum: 6 days Average: 7 days Maximum: 7 days Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 6 days 90-day intervals: Minimum: 4 days Average: 6 days Maximum: 9 days Please note, for Optimistic rollups the state is not finalized until the challenge period passes. 7 days All-time intervals: Minimum: 4 days Average: 7 days Maximum: 13 days Please note, for Optimistic rollups the state is not finalized until the challenge period passes.	Optimistic Rollup	No anomalies detected in the last 30 days

–This project is built using StarkEx.

–This project is based on OP Stack's code base.

–This project is based on old OVM's code base.

–This project is based on zkSync Lite's code base.

–This project is based on ZK Stack's code base.

–This project is based on Loopring's code base.

–This project is based on Arbitrum's code base.

–This project is based on Polygon's code base.

–This project is based on Starknet's code base.

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.