I asked Justin how does he see the role of rollups evolving in this lean Ethereum world? His answer reflects bullishness on the technology of native rollup. Here is what @drakefjustin had to say about the future of rollups in @ethereum: "Today's rollups have two major issues. The first one is that they're quite complex and they're probably buggy. So, potentially this could mean that the entirety of the rollup could be drained in. The second big issue has to do with the maintenance of the EVM. Most of the rollups are trying to be EVM equivalent rollups, which means that when the L1 changes, the L1 EVM changes, the L2s also have to change in unison. And in order to do that, you need to have some sort of a governance process to evolve the rollup. But unfortunately, the governance process itself, the upgrade path, is itself a security vulnerability. Wouldn't it be nice if you could have rollups that by construction are bug free and they don't need to be upgraded whenever the L1 upgrade? And this is the basic idea of native rollups where you can build a rollup where the execution state transition function is an exact copy of whatever is available at L1. By construction, because it's an exact copy of the L1, it's definitionally correct. And whenever the L1 changes, during a hard fork, all of the rollups would automatically change with it. In order to deploy this precompiled for the native rollups, it's quite convenient to first do the ZKVM EVM upgrade... ...effectively, what native rollups give us is an unbounded amount of L1 execution through these native rollups. And the only real bottleneck is the data availability layer." Listen to the full episode for more details.