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

Vitalik Buterin stated that he is "clearly more inclined to support native rollups" compared to the past. Vitalik recalled that an important 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, which involved "fast withdrawals but self-proving 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 bridges and other solutions.

Vitalik pointed out that the situation is changing: the timeline for Ethereum to fully embrace 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. Furthermore, Vitalik emphasized that the implementation of native rollup precompile designs should not be rushed. He expressed a hope that in the future, there would be a property such that if developers build a rollup that is "EVM plus a small amount of extended functionality," they could directly reuse the EVM portion of the native rollup precompiles and only introduce custom proof systems for the new features, connecting the two in a standardized way.