Vitalik Buterin: Shifts to Support Native Rollups, ZK Timeline Gradually Maturing

According to Odaily, Vitalik Buterin stated in a post that he is now "clearly more inclined to support native rollups" compared to the past. Vitalik recalled that a major reason for previously opposing native rollups was that their precompile schemes had to choose between ZK mode or Optimistic mode. At that time, ZK-EVM was still immature, and L2s often chose the latter option—"relying on Ethereum security but requiring a 2–7 day withdrawal period"—over "fast withdrawals but bearing proof risks themselves." This weakened Ethereum's composability and promoted the popularity of solutions such as multisig bridges.

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

In addition, Vitalik emphasized that the design of native rollup precompiles should not be hastily advanced in terms of specific implementation. He proposed that, in the future, there should be a property such that if developers are building a rollup that is "EVM with a small number of extended features," they can directly reuse the EVM part of the native rollup precompile and only introduce a custom proof system for the new features, connecting the two in a standardized way.