EIP-8488 proposes a versioned execution model for Ethereum’s Gas repricing: preserve existing rules for legacy contracts while requiring newly deployed contracts to use a new V2 opcode set after activation.
In its report published on November 9, 2026, at 12:23:54 UTC+8, TechFlow described the proposal as a Draft, not an activated network upgrade. The report said it had been placed on that week’s All Core Developers Execution (ACDE) meeting agenda for peer review.
The problem: repricing without breaking existing contracts
According to TechFlow, an Ethereum Foundation technical notice identified eight contract invariants at risk of being broken. The report said implementing EIP-8037 and EIP-8038 directly would disrupt existing applications with hard-coded Gas logic, while abandoning repricing would leave state growth unaddressed.
TechFlow placed EIP-8488 in the context of an All Core Developers (ACD) decision to postpone the Hoodi testnet hard fork. The proposed version split is intended to provide a path between protecting existing contracts and changing Ethereum’s underlying pricing rules.
What the proposed V2 model would change
As described in the report, EIP-8488 would introduce several boundaries:
- Legacy contracts retain their pricing rules. Contracts deployed before activation would permanently remain under the existing Gas accounting system.
- New deployments must use V2. After activation, newly deployed contracts would be required to use V2 opcodes, with a version marker recorded during bytecode validation.
- New cross-contract calls require matching versions. Under the proposed calling instructions, both caller and callee must be V2 contracts; otherwise, execution would fail.
- V2 removes GAS and GASLIMIT. The report describes removing these instructions as a way to prevent application logic from depending on exposed Gas information and hard-coded assumptions about execution costs.
The compatibility approach therefore preserves legacy execution rather than forcing every existing contract onto the revised pricing model. It also introduces a version boundary for the new cross-contract calling instructions.
Migration and the proposed scaling path
TechFlow reported that the design would not require historical contracts to undergo mandatory code rewrites. DeFi protocols using upgradeable proxies could move to V2 implementations in later iterations, while immutable contracts could remain inactive or continue operating under their original rules.
The report presents reduced state-growth pressure and a higher per-block Gas limit as potential longer-term outcomes—not changes already delivered. Its proposed sequence is for activity to migrate gradually toward the new, state-constrained contracts. If V2 execution reaches a safe share of activity and storage growth is sufficiently contained, core developers would then have a technical basis for substantially raising the network’s per-block Gas limit.
At the time of the report, EIP-8488 remained a proposal under review. Its compatibility rules and scaling rationale should not be read as deployed Ethereum behavior.
Original source: TechFlow article, published November 9, 2026, at 12:23:54 UTC+8.