Risk Analysis
| # | Name | State validation | Data availability | Upgradeability | Sequencer failure | Validator failure |
|---|---|---|---|---|---|---|
| 1 |  Arbitrum One | Fraud proofs (INT) | On chain | Yes | Transact using L1 | Propose blocks |
| 2 |  Optimism | In development | On chain | Yes | Transact using L1 | No mechanism |
| 3 |  dYdX | ZK proofs (ST) | On chain | Yes | Force trade/exit to L1 | Escape hatch (MP) |
| 4 |  Metis Andromeda | In development | Optimistic (MEMO) | Yes | Transact using L1 | No mechanism |
| 5 |  Loopring | ZK proofs (SN) | On chain | Yes | Force exit to L1 | Escape hatch (MP) |
| 6 |  Immutable X | ZK proofs (ST) | External (DAC) | 14 days delay | Force exit to L1 | Escape hatch (MP) |
| 7 |  zkSync | ZK proofs (SN) | On chain | 21d or no delay | Force exit to L1 | Escape hatch (ZK) |
| 8 |  ZKSpace | ZK proofs (SN) | On chain | 8 days delay | Force exit to L1 | Escape hatch (ZK) |
| 9 |  ApeX | ZK proofs (ST) | External | Yes | Force trade/exit to L1 | Escape hatch (MP) |
| 10 |  Sorare | ZK proofs (ST) | External (DAC) | 14 days delay | Force exit to L1 | Escape hatch (MP) |
| 11 |  rhino.fi | ZK proofs (ST) | External (DAC) | 14 days delay | Force exit to L1 | Escape hatch (MP) |
| 12 |  Boba Network | In development | On chain | Yes | Transact using L1 | No mechanism |
| 13 |  Aztec Connect | ZK proofs (SN) | On chain | Yes | Propose blocks (ZK) | Propose blocks (ZK) |
| 14 |  Arbitrum Nova | Fraud proofs (INT) | External (DAC) | Yes | Transact using L1 | Propose blocks |
| 15 |  StarkNet | ZK proofs (ST) | On chain | Yes | No mechanism | No mechanism |
| 16 |  Aztec | ZK proofs (SN) | On chain | Yes | Propose blocks (ZK) | Propose blocks (ZK) |
 ZKSwap 1.0 | ZK proofs (SN) | On chain | 8 days delay | Force exit to L1 | Escape hatch (ZK) | |
| 18 |  Polygon Hermez | ZK proofs (SN) | On chain | 7 days delay | Force exit to L1 | Propose blocks (ZK) |
 ZKSwap 2.0 | ZK proofs (SN) | On chain | 8 days delay | Force exit to L1 | Escape hatch (ZK) | |
| 20 |  Layer2.Finance | Fraud proofs (1R) | On chain | No | No mechanism | No mechanism |
| 21 |  Myria | ZK proofs (ST) | External (DAC) | Yes | Force exit to L1 | Escape hatch (MP) |
| 22 |  Gluon | Fraud proofs (!) | External | Yes | Exit to L1 | Escape hatch (MP) |
 OMG Network | Exits only | External | Yes | Exit to L1 | Escape hatch (?) | |
 Layer2.Finance-zk | ZK proofs (ST) | External (DAC) | Yes | Force exit to L1 | Escape hatch (MP) | |
| 25 |  zkSync 2.0 | ZK proofs (SN) | On chain | Yes | No mechanism | No mechanism |
| 26 |  Fuel v1 | Fraud proofs (1R) | On chain | No | Propose blocks | Propose blocks |
–This project is built using StarkEx.
–This project is based on Optimism's code base.
–This project is based on zkSync's code base.
About L2BEAT
L2BEAT is an analytics and research website about Ethereum layer two (L2) scaling. We provide a comparison of the various Ethereum L2 systems available today.
An important differentiator between L2BEAT and similar sites is that L2BEAT is committed to educating users and lists only projects that match our narrow definition of L2. We define layer two as a chain that fully or partially derives its security from layer one Ethereum so that users do not have to rely on the honesty of L2 validators for the security of their funds.
Because of our commitment to education we present various non-trivial metrics aside from Total Value Locked (TVL). We have carefully examined each L2 project to determine the inner workings of their technology as well as the associated risks. To learn about any of our listed projects visit their respective page on L2BEAT.
We have also compiled a list of Frequently Asked Questions that will help explain some of the decisions we made for our site. We hope you find L2BEAT a valuable resource.