Vitalik Buterin: Shifting towards support for native Rollups; ZK timeline maturing.

Vitalik Buterin stated that he is now "significantly more inclined to support native rollups" compared to the past. He recalled that a key reason for his previous opposition to native rollups was that their pre-compiled solutions required a choice between ZK mode and Optimistic mode. At the time, ZK-EVM was still immature, and L2 often opted for the latter—"faster withdrawals but with self-provided risk"—rather than "relying on Ethereum's security but waiting 2-7 days for withdrawals," thus weakening Ethereum's composability and promoting the adoption of multi-signature bridges and other solutions. Vitalik points out that the situation is changing: Ethereum's timeline for fully adopting ZK at the L1 level is gradually aligning with the actual progress of introducing native rollup pre-compilation, potentially eliminating the aforementioned core obstacles. He also mentioned that the community is increasingly valuing "synchronous composability" as one of the core values ​​of L2 and exploring combining rollup-based solutions with low-latency pre-confirmation mechanisms. Furthermore, Vitalik emphasized that the design of native rollup pre-compilation should not be hastily implemented. He proposed that in the future, the following attribute should be available: if developers build a Rollup with "EVM plus a few extended features", they can directly reuse the EVM part in the native Rollup pre-compilation and introduce a custom proof system only for the new features, thus connecting the two in a standardized way.