Ethereum developers submit draft EIP-8488: propose introduci
Ethereum developers submit EIP-8488 draft proposing parallel V2 opcodes; newly deployed contracts would adopt the gas pricing standards of EIP-8037 and EIP-8038, while existing contracts continue under the old rules, and cross-version calls would be restricted. The proposal remains at the Draft stage and has not been merged or implemented.
Event Timeline
- [11-09 02:30] Gas pricing split between new and old contracts; Ethereum community submits EIP-8488 draft (Odaily Planet Daily)
- [11-09 03:06] Ethereum developers submit EIP-8488 draft, proposing V2 opcodes to adjust gas pricing (Wu Shuo)
Background and Impact
In the early hours of November 9, 2026, two independent sources successively reported that the Ethereum community had submitted the EIP-8488 draft. Odaily Planet Daily published the news at 02:30, and Wu Shuo followed at 03:06. Both materials note that the proposal is currently at an early draft (Draft) stage and has not been formally merged or implemented.
The two materials describe the draft's content in essentially consistent terms: EIP-8488 proposes introducing a parallel set of V2 opcodes whose gas costs follow the new pricing standards of EIP-8037 and EIP-8038. According to Odaily Planet Daily, after network activation, newly deployed contracts may only contain V2 opcodes, while existing contracts continue to execute under the old gas schedule; V2 cross-contract calls require the target contract to also be a V2 version. Wu Shuo added that the new version will also restrict cross-version delegate calls and remove opcodes such as GAS and GASLIMIT.
The two sources differ in their description of who submitted the proposal: Odaily Planet Daily said "the Ethereum community submitted it recently," while Wu Shuo specified that Ethereum developer Leo Glicic submitted it. In addition, Wu Shuo mentioned that the plan aims to create conditions for adjusting gas costs and raising the network's gas limit in the future; Odaily Planet Daily's report did not cover this goal. Neither material disclosed a specific activation timetable; where they differ, the original text of each source should prevail.
In terms of design approach, the draft handles gas pricing for newly deployed contracts and existing contracts separately; Wu Shuo interpreted this arrangement as avoiding repricing that would break the compatibility of existing contracts. If the plan moves forward, new and old contracts will coexist under two sets of gas rules for a period, and restrictions on cross-version calls may also become a factor developers need to consider when deploying contracts; however, since the proposal is still at the Draft stage, these rules are not yet finalized and have not entered the implementation process. Readers following developments in the Ethereum ecosystem and gas mechanisms can track further information through the announcements and market pages of platforms such as Huobi HTX registration app download, Zhima Gate.io registration app download, Bitget registration app download, Binance registration app download, and OKX registration app download. This article is for information compilation only and does not constitute investment advice.
FAQ
### Will EIP-8488 immediately change the gas fees of existing contracts?
According to the available materials, existing contracts continue to execute under the old gas schedule; only contracts newly deployed after network activation must contain V2 opcodes and are subject to the new pricing standards of EIP-8037 and EIP-8038. Moreover, the proposal is still at the Draft stage and has not been merged or implemented.
### Can new and old contracts still call each other?
Odaily Planet Daily said V2 cross-contract calls require the target contract to also be a V2 version; Wu Shuo said the new version will restrict cross-version delegate calls. The specific boundaries have not yet been determined and are subject to the proposal's subsequent text.
### What milestones should be watched going forward?
Public information currently shows only that the proposal is at the Draft stage and has not been formally merged or implemented; neither material provided an activation timetable. Going forward, watch the proposal discussion, its merge status, and whether it enters the network upgrade schedule.