Vitalik: Shift in attitude towards supporting native Rollups, ZK timeline gradually matures

Vitalik Buterin stated that he is "significantly more inclined to support native rollups" compared to the past. Vitalik reflected that a key reason for opposing native rollups previously was that their precompiled solutions had to choose between ZK mode or Optimistic mode, and at that time, ZK-EVM was not mature. L2 often chose the latter option, which involved "fast withdrawals but self-bear proof risks" versus "relying on Ethereum's security but needing to wait 2-7 days for withdrawals," thereby weakening Ethereum's composability and promoting the proliferation of multi-signature bridge solutions.

Vitalik pointed out that the situation is changing: Ethereum's timeline for fully adopting ZK at the L1 level is gradually aligning with the realistic progress of introducing native rollup precompiles, and the aforementioned core obstacles are expected to be eliminated. He also mentioned that the community is increasingly viewing "synchronous composability" as one of the core values of L2 and is exploring the combination of rollup-based solutions with low-latency pre-confirmation mechanisms.

Additionally, Vitalik emphasized that the design of native rollup precompiles should not be rushed in its specific implementation. He expressed a hope that in the future, there would be a property such that if developers build a rollup that is "EVM with a small amount of extended functionality," they can directly reuse the EVM part of the native rollup precompiles and only introduce a custom proof system for the new features, connecting the two in a standardized way.