Risk Analysis

Others are L2s that either lack a working proof system or don't provide sufficient external DA guarantees (i.e. at least 5 independent attesters, a high enough threshold, or a proper DA bridge). To be listed in this category, the L2 must enshrine deposits from L1.

Columns

name

State Validation

Data Availability

Exit Window

Sequencer Failure

Proposer Failure

name

State Validation

Data Availability

Exit Window

Sequencer Failure

Proposer Failure

#	name	State Validation	Data Availability	Sequencer Failure	Proposer Failure

1	Hyperliquid Hyperliquid	Currently the system permits invalid state roots. More details in project overview.	Proof construction and state derivation rely fully on data that is ultimately NOT published on Ethereum.	There is no mechanism to have transactions be included if the sequencer is down or censoring.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
2	Polygon PoS Polygon PoS	Currently the system permits invalid state roots. More details in project overview.	Data is guaranteed to be available by an external proof of stake network of validators. On Ethereum, DA is attested via signed block headers.	There is a sequencer set of 104 (called validators), capped at 105. Validator entry is permissioned. A minimum of 100,000 POL stake is required to obtain block production rights. There is no specific censorship resistance mechanism against selective censorship by parts of the active validator set nor a way to force transactions from Ethereum L1. The canonical bridge between Polygon PoS and Ethereum allows for queuing transactions from the Ethereum and Polygon PoS sides, which cannot be skipped, except for halting the queue entirely.	The PoS network is composed of 104 validators. Blocks are included in the chain only if signed by 2/3+1 of the network stake. It's currently not possible to join the set if the validator cap is reached. The current validator cap is set to 105. In the event of a failure in reaching consensus, withdrawals are frozen.
3	Robinhood Chain Robinhood Chain	Fraud proofs only allow 2 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. There is a 6d 8h challenge period.	All of the data needed for proof construction is published on Ethereum L1.	There is no guaranteed mechanism to have transactions included if the sequencer is down or censoring. Although users can enqueue messages in the L1 delayed inbox and call forceInclusion on the SequencerInbox, the chain runs ArbOS 61 transaction filtering: an authorized filterer can register any transaction hash in the ArbFilteredTransactionsManager precompile (0x00…0074), after which the state transition function forcibly fails that transaction, including force-included ones, without delay.	Anyone can become a Proposer after 28d of inactivity from the currently whitelisted Proposers.
4	World Chain World Chain	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
5	Gnosis Chain Gnosis Chain	Ethereum contracts do not validate Gnosis Chain state transitions. Bridge messages are accepted after threshold signatures from dedicated bridge validators.	Data is made available by an external proof of stake network of validators. Since there is no DA bridge, Ethereum cannot verify whether any data was made available on Gnosis Chain or whether incoming messages originate from state that was attested to by the PoS network.	Users can permissionlessly become a sequencer (validator) by staking a minimum of 1 GNO to join the queue and wait to obtain block production rights. There is no specific censorship resistance mechanism against selective censorship by parts of the active validator set nor a way to force transactions from Ethereum L1.	The Gnosis Chain bridge is not validated by its PoS validator set. Withdrawals through the xDAI bridge require 4/7 validator signatures, while AMB and Omnibridge withdrawals require 4/7 validator signatures. The bridge validators can freeze bridge transactions and/or steal bridge-locked and minted assets. Transactions on Gnosis Chain itself cannot be forced from Ethereum. If the chain has a liveness failure due to blanket censorship or operator walkaway the only recourse are new validators joining the open validator set.
6	Ronin Ronin	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	Proof construction and state derivation fully rely on data that is posted on EigenDA. The sequencer is publishing data to EigenDA v2. Sequencer transaction data roots are not checked against the DACert Verifier onchain.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
7	X Layer X Layer	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Single round proofs (1R) only require a single transaction to resolve. ZK proofs are used to prove the correctness of the state transition. Challenges are currently restricted to 1 whitelisted challenger and proposals are restricted to 1 whitelisted proposer.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only whitelisted proposers can publish state roots. Permissionless proposing becomes available only after 1000y of proposer inactivity, which is not a practical recovery path.
8	Fraxtal Fraxtal	Currently the system permits invalid state roots. More details in project overview.	Proof construction and state derivation rely fully on data that is NOT published on chain. Fraxtal uses a separate data availability module developed by the Frax Core Team, and data availability attestations are not published on chain.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
9	Lighter on RH Lighter on RH	Fraud proofs only allow 2 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. There is a 6d 8h challenge period.	All of the data needed for proof construction is published on the base chain, which ultimately gets published on Ethereum.	There is no guaranteed mechanism to have transactions included if the sequencer is down or censoring. Although users can enqueue messages in the L1 delayed inbox and call forceInclusion on the SequencerInbox, the chain runs ArbOS 61 transaction filtering: an authorized filterer can register any transaction hash in the ArbFilteredTransactionsManager precompile (0x00…0074), after which the state transition function forcibly fails that transaction, including force-included ones, without delay.	Users are able to trustlessly exit by submitting a zero knowledge proof of funds.
10	Manta Pacific Manta Pacific	Currently the system permits invalid state roots. More details in project overview.	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.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
11	Plume Network Plume Network	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 5d 14h challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 1/1 that is tasked with protecting and supplying the data.	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 can be up to a 1d delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
12	MegaETH MegaETH	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Single round proofs (1R) prove the validity of a state proposal, only requiring a single transaction to resolve. A fault proof eliminates a state proposal by proving that any intermediate state transition in the proposal results in a different state root. For either, a ZK proof is used. Since the node source is not available, challengers cannot watch the chain independently. `vanguardAdvantage` applies to every proposal and is set to 36558901084y 8mo, so only the Vanguard can submit state proposals; faulty proposals can be flagged but not replaced, halting the chain until the Vanguard proposes a correct state root.	Proof construction and state derivation fully rely on data that is posted on EigenDA. The sequencer is publishing data to EigenDA v2. Sequencer transaction data roots are not checked against the DACert Verifier onchain.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
13	BOB BOB	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
14	Blast Blast	Currently the system permits invalid state roots. More details in project overview.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
15	Metis Metis	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve.Anyone can submit challenge requests. However, permissioned actors are needed to create the challenge and to delete successfully disputed state roots. Additionally, the current permissioned actors (GameCreator and Security Council minority) can collude and finalize malicious state roots.	All of the data needed for proof construction is published on Ethereum L1.	There is no mechanism to have transactions be included if the sequencer is down or censoring. The single address acting as a sequencer on L1 is not trustlessly linkable to the claim of multiple decentralized sequencers being used.	Only the whitelisted proposer can update state roots on L1, so in the event of failure the withdrawals are frozen. The Security Council minority can be alerted to enforce censorship resistance because they own the proposer registry, controlling the active whitelisted proposer.
16	Paradex Paradex	STARKs are zero knowledge proofs that ensure state correctness.	Encrypted data is posted on Ethereum as blobs, and a privacy council of 3 members holds the decryption keys. Users are not able to independetly reconstruct the L2 state without relying on the council members.	There is no mechanism to have transactions be included if the sequencer is down or censoring.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
17	ApeX Omni ApeX Omni	Zero knowledge cryptography is used to ensure state correctness. Proofs are first verified on Arbitrum One and finally on Ethereum.	All of the data needed for proof construction is published on the base chain, which ultimately gets published on Ethereum.	There is no mechanism to have transactions be included if the sequencer is down or censoring.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
18	Immutable zkEVM Immutable zkEVM	Currently the system permits invalid state roots. More details in project overview.	Proof construction and state derivation rely fully on data that is NOT published onchain.	There is no mechanism to have transactions be included if the sequencer is down or censoring.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
19	RISE RISE	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Single round proofs (1R) only require a single transaction to resolve. ZK proofs are used to prove the correctness of the state transition. The system currently operates with a closed set of 1 whitelisted challenger.	Proof construction and state derivation fully rely on data that is posted on EigenDA. The sequencer is publishing data to EigenDA v2. Sequencer transaction data roots are checked against the DACert Verifier data roots, signed off by EigenDA operators.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
20	Cronos zkEVM Cronos zkEVM	STARKs and SNARKs are zero knowledge proofs that ensure state correctness. STARKs proofs are wrapped in SNARKs proofs for efficiency. SNARKs require a trusted setup.	Proof construction and state derivation rely fully on data that is NOT published onchain.	Users can submit transactions to an L1 queue, but can't force them. The sequencers cannot selectively skip transactions but can stop processing the queue entirely. In other words, if the sequencers censor or are down, they are so for everyone.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen. There is a decentralized Governance system that can attempt changing Proposers with an upgrade.
21	SX Network SX Network	Fraud proofs allow 6 WHITELISTED actors watching the chain to prove that the state is incorrect. There are fewer than 5 Challengers external to the Operator among these. Interactive proofs (INT) require multiple transactions over time to resolve. There is a 6d 8h challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 1/1 that is tasked with protecting and supplying the data.	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 can be up to a 4d delay on this operation.	Anyone can become a Proposer after 12d 17h of inactivity from the currently whitelisted Proposers.
22	Soneium Soneium	State roots are proposed as super roots by a permissioned proposer. The respected game type exposes no challenger, VM or challenge clock, so proposals cannot be disputed by execution. Validity is governed by the AnchorStateRegistry, and the Guardian can blacklist games and change the respected game type.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
23	ApeChain ApeChain	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 6d 8h challenge period.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 4d delay on this operation.	Anyone can become a Proposer after 12d 17h of inactivity from the currently whitelisted Proposers.
24	Fuel Ignition Fuel Ignition	Currently the system permits invalid state roots. More details in project overview.	Proof construction and state derivation fully rely on data that is posted on EigenDA. The sequencer is publishing data to EigenDA v2. Sequencer transaction data roots are not checked against the DACert Verifier onchain.	In the event of a sequencer failure, users can force transactions to be included in the project's chain by sending them to L1.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
25	Aevo Aevo	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	Proof construction and state derivation fully rely on data that is posted on EigenDA. The sequencer is publishing data to EigenDA v2. Sequencer transaction data roots are not checked against the DACert Verifier onchain.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
26	Lumia Prism Lumia Prism	Currently the system permits invalid state roots. 'Pessimistic' proofs only validate the bridge accounting.	Proof construction and state derivation rely fully on data that is NOT published onchain.	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.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
27	Zircuit Zircuit	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
28	Orderly Orderly	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	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.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
29	Haust Network Haust Network	Currently the system permits invalid state roots. 'Pessimistic' proofs only validate the bridge accounting.	Proof construction and state derivation rely fully on data that is NOT published onchain.	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.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
30	Gravity Gravity	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 5d 14h challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 1/1 that is tasked with protecting and supplying the data.	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 can be up to a 2y 9mo delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
31	Silicon Silicon	Currently the system permits invalid state roots. 'Pessimistic' proofs only validate the bridge accounting.	Proof construction and state derivation rely fully on data that is NOT published onchain.	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.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
32	Polygon zkEVM Polygon zkEVM	Currently the system permits invalid state roots. 'Pessimistic' proofs only validate the bridge accounting.	Proof construction and state derivation rely fully on data that is NOT published onchain.	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.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
33	Mode Mode	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
34	HashKey Chain HashKey Chain	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
35	Boba Boba	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
36	Lisk Lisk	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
37	Zora Zora	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
38	Eclipse Eclipse	Currently the system permits invalid state roots. More details in project overview.	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.	There is no mechanism to have transactions be included if the sequencer is down or censoring.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
39	zkLink Nova zkLink Nova	Zero knowledge cryptography is used to ensure state correctness. Proofs are first verified on Linea and finally on Ethereum.	Proof construction and state derivation rely fully on data that is ultimately NOT published on Ethereum.	There is no mechanism to have transactions be included if the sequencer is down or censoring.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
40	Cyber Cyber	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	Proof construction and state derivation rely fully on data that is NOT published onchain. A custom data availability (DA) provider without attestations is used, but data unavailability can be challenged.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
41	Reya Reya	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 6d 8h challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 1/1 that is tasked with protecting and supplying the data.	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 can be up to a 1d delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
42	Edge Chain Edge Chain	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 7d challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 2/5 that is tasked with protecting and supplying the data.	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 can be up to a 5d delay on this operation.	Anyone can become a Proposer after 28d of inactivity from the currently whitelisted Proposers.
43	Pentagon Chain Pentagon Chain	Currently the system permits invalid state roots. 'Pessimistic' proofs only validate the bridge accounting.	Proof construction and state derivation rely fully on data that is NOT published onchain.	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.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
44	Ethereal Ethereal	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 5d 14h challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 1/1 that is tasked with protecting and supplying the data.	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 can be up to a 2d delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
45	EDU Chain EDU Chain	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 6d 8h challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 1/1 that is tasked with protecting and supplying the data.	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 can be up to a 5d delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
46	Fluent Fluent	State roots are accepted on the basis of an AWS Nitro Enclave preconfirmation and a 2d time delay; the SP1 ZK proof system exists in the contracts but is currently unreachable because CHALLENGER_ROLE has no holders. Effective security reduces to trust the TEE and wait the delay. See the State Validation section below for details.	All of the data needed for proof construction is published on Ethereum L1.	There is no mechanism to have transactions be included if the sequencer is down or censoring.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
47	Shape Shape	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
48	Hemi Hemi	Currently the system permits invalid state roots. More details in project overview.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
49	DeBank Chain DeBank Chain	Currently the system permits invalid state roots. More details in project overview.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
50	Lasernet Lasernet	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 5d 14h challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 1/1 that is tasked with protecting and supplying the data.	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 can be up to a 1d delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
51	Shibarium Shibarium	Currently the system permits invalid state roots. More details in project overview.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 8/11 that is tasked with protecting and supplying the data.	Users can submit transactions to an L1 queue, but can't force them. The sequencers cannot selectively skip transactions but can stop processing the queue entirely. In other words, if the sequencers censor or are down, they are so for everyone.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
52	Nillion Nillion	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	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.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
53	LightLink LightLink	Currently the system permits invalid state roots. More details in project overview.	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.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
54	Xai Xai	Fraud proofs only allow 2 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. There is a 6d 8h challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 3/5 that is tasked with protecting and supplying the data.	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 can be up to a 2d delay on this operation.	Anyone can become a Proposer after 12d 17h of inactivity from the currently whitelisted Proposers.
55	Phala Phala	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
56	Soon Soon	Currently the system permits invalid state roots. More details in project overview.	Proof construction and state derivation fully rely on data that is posted on EigenDA. The sequencer is publishing data to EigenDA v2. Sequencer transaction data roots are not checked against the DACert Verifier onchain.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
57	Metal Metal	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
58	AlienX AlienX	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 6d 8h challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 1/1 that is tasked with protecting and supplying the data.	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 can be up to a 1d delay on this operation.	Anyone can become a Proposer after 12d 17h of inactivity from the currently whitelisted Proposers.
59	Ancient8 Ancient8	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	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.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
60	Pepe Unchained Pepe Unchained	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 5d 14h challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 1/1 that is tasked with protecting and supplying the data.	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 can be up to a 1d delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
61	Swan Chain Swan Chain	Currently the system permits invalid state roots. More details in project overview.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
62	Funki Funki	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	Proof construction and state derivation rely fully on data that is NOT published onchain. A custom data availability (DA) provider without attestations is used, but data unavailability can be challenged.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
63	ZKFair ZKFair	Currently the system permits invalid state roots. More details in project overview.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 3/5 that is tasked with protecting and supplying the data.	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.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
64	Appchain Appchain	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 6d 8h challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 1/1 that is tasked with protecting and supplying the data.	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 can be up to a 3d delay on this operation.	Anyone can become a Proposer after 12d 17h of inactivity from the currently whitelisted Proposers.
65	Towns Towns	Currently the system permits invalid state roots. More details in project overview.	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.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
66	Deri Deri	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 1d challenge period.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 2d delay on this operation.	Anyone can become a Proposer after 7d 8h of inactivity from the currently whitelisted Proposers.
67	Settlus Settlus	Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. Only one entity is currently allowed to propose and submit challenges, as only permissioned games are currently allowed.	All of the data needed for proof construction is published on Ethereum L1.	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 can be up to a 12h delay on this operation.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
68	Payy Payy	SNARKs are succinct zero knowledge proofs that ensure state correctness, but require trusted setup.	Proof construction and state derivation rely fully on data that is NOT published onchain.	There is no mechanism to have transactions be included if the sequencer is down or censoring.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
69	Earnm Earnm	No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 7d challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 2/3 that is tasked with protecting and supplying the data.	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 can be up to a 5d delay on this operation.	Anyone can become a Proposer after 28d of inactivity from the currently whitelisted Proposers.
70	GRVT GRVT	STARKs and SNARKs are zero knowledge proofs that ensure state correctness. STARKs proofs are wrapped in SNARKs proofs for efficiency. SNARKs require a trusted setup.	Proof construction and state derivation rely fully on data that is NOT published onchain.	There is no mechanism to have transactions be included if the sequencer is down or censoring. The Operator actively uses a TransactionFilterer contract, which requires accounts that enqueue or force transactions from L1 to be whitelisted.	Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen. There is a decentralized Governance system that can attempt changing Proposers with an upgrade.
71	PlayBlock PlayBlock	Fraud proofs only allow 2 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. There is a 30m challenge period.	Proof construction relies fully on data that is NOT published onchain. There exists a Data Availability Committee (DAC) with a threshold of 1/1 that is tasked with protecting and supplying the data.	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 can be up to a 11d delay on this operation.	Anyone can become a Proposer after 1mo 4d of inactivity from the currently whitelisted Proposers.

Search