Vitalik: Now more optimistic about native rollup than before According to a report by Golden Finance, Vitalik Buterin posted on X platform that he is now more inclined towards native rollup than before. One important reason I opposed before was that the precompile of native rollup must choose either "zk mode" or "optimistic mode". However, ZK-EVM is not yet mature enough in ZK mode, so if we provide L2 with two options: "Use proof of Ethereum full trust endorsement, withdrawal needs to wait for 2-7 days" or "Instant withdrawal, but you have to handle the proof yourself", L2 usually chooses the former. This is very detrimental to the composability of Ethereum, as it will lead to the adoption of more multisig bridges and so on. But now it seems that Ethereum fully accepts ZK's timeline on L1, which actually matches the actual timeline of adding native rollup precompilation, so this problem has been solved. In addition, I see an increasing number of works incorporating synchronous composability as one of the core value propositions of 'why do L2'. I have also proposed a method: https://ethresear.ch/t/combining-preconfirmations-with-based-rollups-for-synchronous-composability/23863 , used to convert based on Rollup (based rollups) is combined with L2 low latency pre confirmation (preconf) to achieve synchronous composability. So I feel like this is the right direction for development. I think we should not be lazy and need to spend more effort finding the best way to implement this precompilation. One key attribute I want is that if you create a "EVM+some new features" rollup, you should be able to precompile the EVM using native rollup and use your own prover to handle the newly added features. You can consider using a lookup table to standardize the connection between the two.