Vitalik: The underlying proof system quality of Layer 2 networks is equally important and should gradually enter the second stage as development progresses

BlockBeats News, May 5th, in response to community member Daniel Wang's proposed naming tag #BattleTested for the L2 Network Stage 2, Ethereum co-founder Vitalik responded in a post on Platform X, stating: "This is a good reminder: the second stage is not the only factor influencing security; the quality of the underlying proof system is equally important. This is a simplified mathematical model showing when to enter the second stage:

Each security council member has a 10% independent "break" chance; we treat liveness failure (failure to sign or inaccessible key) and safety failure (signing something wrong or key compromised) as equally likely; goal: minimize the likelihood 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, security council members have "common mode failures": they may collude, or 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, so entering Stage 2 earlier than implied by the model is the optimal choice.

Also, note that by turning the proof system itself into a multisignature of multiple independent systems, the probability of proof system collapse can be significantly reduced (this is what I advocated in the previous proposal). I suspect that all early Stage 2 deployments in previous years would have been like this. Taking these into account, this is the chart. The X-axis is the probability of proof system failure. The Y-axis is the probability of protocol collapse. With the improvement of proof system quality, the optimal stage transitions from Stage 0 to Stage 1, and then from Stage 1 to Stage 2. Using a Stage 0 quality proof system for Stage 2 is the worst.

In short, @l2beat should ideally show proof system audit and maturity metrics (preferably proof system implementation rather than a whole aggregation for reusability) and stages."