According to ChainCatcher, Vitalik Buterin stated that he is now "significantly more inclined to support native rollups" compared to the past. Vitalik 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 servers often chose the latter—"faster withdrawals but with self-provided risk"—over "relying on Ethereum's security but requiring a 2-7 day wait for withdrawals," thus weakening Ethereum's composability and promoting the adoption of multi-signature bridges and other similar 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 actual progress of introducing native Rollup pre-compilation, and the aforementioned core obstacles are expected to be eliminated. He also mentioned that the community is increasingly regarding "synchronous composability" as one of the core values of L2 and is exploring combining Rollup-based solutions with low-latency pre-acknowledgment mechanisms.
Furthermore, Vitalik emphasized that the design of native Rollup pre-compilation should not be rushed in its implementation. He proposed that in the future, Rollup should have the following property: if developers build a Rollup with "EVM plus a few extended functions", they can directly reuse the EVM part of the native Rollup pre-compilation and only introduce a custom proof system for the new functions, thus connecting the two in a standardized way.
