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.

Odaily Planet Daily News In response to the naming tag #BattleTested for the L2 network Stage 2 proposed by community member Daniel Wang, Ethereum co-founder Vitalik responded on the X platform: "This is a good reminder: 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 member of the Security Council has a 10% independent "break" chance; we treat activity failure (refusal to sign or key inaccessibility) and security failure (signing the wrong thing or key hacking) as equally likely; goal: minimize the possibility of protocol collapse under the above assumptions. *Stage 0 Security Council is 4/7, stage 1 is 6/8; please note that these assumptions are very imperfect. In reality, members of the Security Council have "common mode failures": they may collude, or they may all be coerced or hacked in the same way, etc. This makes both stage 0 and stage 1 less secure than shown in the model, and therefore enters stage 2 earlier than the model implies. Phases are optimal. Also, note that the probability of a proving system crashing can be 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 optimal 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 proving system audits and maturity metrics (preferably of proving system implementations rather than entire rollups so we can reuse) as well as phases. ”