Opposition to Vitalik Buterin’s Gas Limit Increase Proposal by Ethereum Developers due to Blockchain State

Ethereum Developers Concerned About Vitalik Buterin’s Gas Limit Increase Proposal

Ethereum developers have raised concerns regarding the recent proposal by Vitalik Buterin, co-founder of the Ethereum network, to increase the gas limit on the blockchain.

Opposition to Vitalik Buterin’s Proposal

In a blog post on January 11th, Ethereum developer Marius van der Wijden expressed his concerns about the difficulty of increasing the gas fee and highlighted the potential consequences for the blockchain state. He also provided possible solutions to address these concerns.

The current size of the blockchain state, which includes contract data, is 267 gigabytes. The total size of the blockchain history is around 900 gigabytes. Increasing gas sizes could lead to further growth in these sizes.

History and Sync Challenges

Another challenge highlighted by developers is the growth of history size as transaction count continues to increase. The implementation of layer 2 networks has made history even more important.

Raising the gas limit can also make it more difficult to build new clients for the mainnet, as existing clients like Geth already have years of experience. Additionally, increasing the gas limit can slow down full sync and affect snap healing, history, and catching up speeds.

Hot Take: Ethereum Developers Oppose Vitalik Buterin’s Gas Limit Increase Proposal

Ethereum developers are expressing their concerns about Vitalik Buterin’s proposal to increase the gas limit on the blockchain. They argue that raising the gas limit could lead to risks such as increased state size, missed block rate, synchronization times, and client diversity. Developers suggest that implementing solutions to address these concerns should be a priority before proceeding with any changes. They also highlight challenges related to history size and the difficulty of building new clients. While increasing the gas limit may have potential benefits, developers emphasize the need for careful monitoring and metrics to evaluate the impact of such changes.