BTC
ETH
HTX
SOL
BNB
View Market
简中
繁中
English
日本語
한국어
ภาษาไทย
Tiếng Việt

Vitalik: The quality of the underlying proof system of the L2 network is equally important and should gradually enter the second stage as it develops.

2025-05-05 06:16

Odaily News In response to the naming tag #BattleTested for Stage 2 of the L2 network proposed by community member Daniel Wang, Ethereum co-founder Vitalik responded on the X platform: “This is a good reminder that the second stage is not the only factor affecting security, the quality of the underlying proof system is equally important. This is a simplified mathematical model that shows when to enter the second stage:
Each Security Council member has a 10% independent chance of "breaking"; we treat activity failures (refusal to sign or inaccessible keys) and security failures (signing the wrong thing or keys being hacked) as equally likely; Goal: minimize the probability of protocol breakdown under the above assumptions.
* The Security Council is 4/7 for Phase 0 and 6/8 for Phase 1; note that these are very imperfect assumptions. In reality, the members of the Security Council have "common mode failures": they may collude, or all be coerced or hacked in the same way, etc. This makes both Phase 0 and Phase 1 less secure than the model suggests, so it is best to enter Phase 2 sooner than the model implies.
Also, note that the probability of a proving system crashing is greatly reduced by turning the proving system itself into a multisig of multiple independent systems (this is what I advocated in my previous proposal). I suspect that all Phase 2 deployments in the first few years will be like this. With that in mind, here is the chart. The X-axis is the probability of a proving system crashing. The Y-axis is the probability of a protocol crashing. As the quality of the proving system improves, the best phase moves from Phase 0 to Phase 1, and then from Phase 1 to Phase 2. Phase 2 with a Phase 0 quality proving system is the worst.
In short, @l2beat should ideally show proof system audits and maturity indicators (preferably proof system implementations rather than entire rollups so we can reuse) and phases. ”