Concerns Rise Over Ethereum’s Glamsterdam Upgrade: Competing Proposals Surface

Introduction

In an effort to mitigate potential disruptions from the forthcoming Glamsterdam upgrade, Ethereum developers have proposed two differing solutions aimed at safeguarding existing smart contracts. These proposals, submitted on November 8 by developers Leo Glisic and Giulio Rebuffo, respond to rising concerns over the impact of new gas pricing regulations set to be implemented as part of the upgrade.

Need for Solutions

The necessity for these solutions arises from warnings about security vulnerabilities that led to the postponement of essential testing for Glamsterdam. Many smart contracts are currently dependent on fixed gas fees, and modifying these costs poses a risk of transaction failures or complications for applications that cannot be modified post-deployment.

Proposals Overview

Glisic's proposal, known as EIP-8488, suggests creating a distinct set of processing instructions for newly developed smart contracts. Under this plan, older contracts would continue to operate under the original gas pricing rules while newer contracts would utilize updated V2 opcodes that align with the adjusted fees outlined in EIPs 8037 and 8038. This approach seeks to facilitate the introduction of revamped fees without necessitating changes to established applications.

Conversely, Rebuffo's draft outlines an alternative strategy: a dual gas accounting system implemented in every transaction. This system would include one calculation based on the prior gas cost structure, preserving original assumptions, and another that reflects costs using the newly proposed pricing model. However, Rebuffo’s suggestion highlights the absence of a complete execution client implementation for this framework. Neither of the proposals has yet received approval for inclusion in the Glamsterdam upgrade.

Compatibility Issues

The root of these compatibility issues can be traced to the changes proposed in EIPs 8037 and 8038, which alter how Ethereum calculates fees for contract creation and state access. For instance, EIP-8037 aims to increase the basic gas requirement for creating a smart contract from 32,000 to 183,600, a substantial rise that excludes additional costs associated with execution and code storage.

Community Concerns

Critical assessments from security experts, such as those from ChainSecurity, have identified risks for existing applications, noting eight fundamental assumptions in current smart contracts that could fail under the new gas rules. Some smart contracts rely on predetermined gas amounts for external calls while others function based on specific transaction failure behaviors. There are concerns that shifts in gas consumption could disrupt these processes. Developer banteg pointed out on social media that around 200,000 contracts may be impacted, and this figure could be understated due to methodological discrepancies.

The proposed upgrade has garnered pushback from within the Ethereum community, particularly among developers and figures in the decentralized finance (DeFi) sector, who stress the necessity for resolving these compatibility issues before proceeding. Curve Finance's founder, Michael Egorov, cautioned against advancing the plan without thoroughly addressing the risks involved, suggesting it might lead to abrupt emergency responses.

While some community members, like investor Ryan Berckmans, initially supported the move towards upgrading, they later reversed their stance upon realizing the depth of compatibility concerns. Security researcher pcaversaccio has taken a decisive stand against the current form of Glamsterdam, urging that it should not be dispatched as planned given the flagged potential issues.

Previous Delays and Future Plans

The Ethereum developers had previously delayed the activation of the Hoodi upgrade on October 26 due to similar apprehensions regarding the revised gas rules. This included stopping the Amsterdam execution layer changes and a significant increase in the gas limit to 200 million. Developer Marius van der Wijden of the Ethereum Foundation confirmed in a recent statement that they are collaborating with security firms to evaluate affected contracts and engage with the developer community for insights. Plans for a subsequent private Glamsterdam testing phase were informally scheduled for mid-November, prior to the introduction of the two proposals, marking a challenging period for the Ethereum network as it navigates these implications for its operational ecosystem.