Five Potential Designs to Optimize Ethereum's Block Size for the Rollup-Centric Roadmap

Ethereum co-founder, Vitalik Buterin, and the Ethereum Foundation have recently delved into the discussion of reducing Ethereum's maximum block size. Their aim is to optimize the blockchain for the "rollup-centric roadmap." In this article, we will explore the five proposed designs and their potential effects on the Ethereum network.

The Need for Optimization

As the focus on rollups intensifies in the medium and long term, it becomes evident that the current utilization of block space is far from optimal. Over the past 12 months, the effective block size has doubled. Buterin and Wahrstätter speculate that this increase could be attributed to the growing usage of Ethereum for data availability^[1].

While this growth is remarkable, it raises concerns about the scalability and performance of the Ethereum network. To address these issues, the Ethereum Foundation is exploring various solutions to decrease the maximum block size and make room for more data blobs in the future^[1].

The Proposed Solutions

The blog post highlights five different solutions, ranging in complexity, to tackle the issue. These solutions aim to increase block gas limits and disincentivize the use of calldata, ultimately reducing the maximum block size and variance^[1]. Let's explore some of the proposed designs:

1. Adjusting Calldata Cost

One simple solution involves increasing the cost of calldata from 16 to 42 gas. This adjustment would effectively decrease the maximum block size from 1.78 megabytes to 0.68 megabytes, making room to increase the block gas limit^[1]. However, this approach may hinder applications like StarkNet, which heavily rely on large calldata for on-chain proofs.

2. Modifying Opcode Costs

Another suggestion is to increase the calldata cost while decreasing other opcode costs. By doing so, the Ethereum Virtual Machine (EVM) can maintain a balance between calldata price and gas limit^[1]. This approach offers more flexibility and provides incentives for utilizing calldata within the EVM.

3. Introducing a Calldata Fee Market

Creating a separate fee market for calldata, similar to data blobs, could potentially increase gas limits. The price for calldata usage would automatically adjust based on demand. However, implementing this approach comes with increased complexity in analysis and implementation^[1].

4. Capping Calldata per Block

EIP-4488 proposes capping calldata per block as an alternative solution. However, this approach may also discourage the use of calldata for data availability and negatively affect calldata-dependent applications^[1].

5. EVM Loyalty Bonus

Lastly, as a compensatory measure, the idea of offering an "EVM loyalty bonus" to calldata-heavy apps arises. This bonus could incentivize the use of calldata and mitigate the potential impact on those applications^[1].

Conclusion

While finding the perfect solution remains a challenge, striking a balance between calldata cost and gas limit is crucial for optimizing Ethereum's block size. The Ethereum Foundation and Buterin continue to evaluate these proposals and search for the most effective way to enhance the network's scalability and performance^[1]. As Ethereum's ecosystem evolves, strategies like these will play a crucial role in ensuring its long-term success.