Ethereum Researchers Pitch a Native zkEVM That Scales Bandwidth, Not Just Speed

Ethereum's scaling debate usually centers on execution, meaning how many transactions per second the network can compute. A new research post by Mike Neuder, an Ethereum researcher, reframes the question around bandwidth, meaning how much data the base layer can carry and verify. That capacity is what ultimately limits the throughput of the layer-2 rollups built on top of Ethereum.

The idea is a native zkEVM, meaning the protocol itself would verify zero-knowledge proofs (cryptographic proofs that a computation was carried out correctly without re-running it) rather than leaving that work to each individual rollup. Building the proof system into the base layer, the proposal argues, would let validators confirm far more activity per unit of data and bandwidth than requiring every node to re-execute every transaction. The post presents this as a core part of Ethereum's post-Glamsterdam scaling roadmap.

The economic logic matters as much as the engineering. Today's rollups each pay to generate and post their own proofs and data, a duplicated cost that the base layer could absorb and standardize. Linking execution and bandwidth costs to base-layer ether transactions would also strengthen the connection between network usage and the value of ether itself. That connection is a recurring concern as activity moves to layer-2 networks that capture much of the fee revenue.

The proposal is research, not a scheduled upgrade. But it indicates where Ethereum's core developers are directing the next round of scaling work, toward a base layer that verifies proofs rather than re-runs computation, with throughput limited by data capacity instead of raw processing power.