For Ethereum builders, changing Gas prices raises a compatibility question: what happens to contracts whose logic depends on today’s execution costs? In a report published on November 9, 2026, at 12:23:54 UTC+08:00, TechFlow described EIP-8488, a draft proposal that would preserve existing contracts’ pricing rules while introducing versioned V2 opcodes for newly deployed contracts.
Gas measures execution costs on Ethereum; opcodes are the individual instructions executed by the network. The proposal, as reported, would separate old and new execution rules rather than reprice every contract at once.
Why introduce two sets of rules?
According to TechFlow, an Ethereum Foundation technical notice had identified risks to eight contract invariants—conditions contracts depend on remaining true. The report said implementing EIP-8037 and EIP-8038 directly would break existing applications with hardcoded Gas assumptions, while abandoning repricing would leave concerns about growing network state unresolved.
The report placed EIP-8488 in the context of core developers’ decision to postpone the Hoodi testnet hard fork. Its proposed dividing line would be activation: contracts deployed beforehand would permanently retain their existing Gas accounting rules.
What would change for new contracts?
TechFlow described three central requirements:
- Mandatory V2 instructions: All contracts deployed after activation would have to use V2 opcodes, with a version marker recorded during bytecode validation.
- Version-restricted calls: New cross-contract call instructions would require both caller and recipient to be V2 contracts. A version mismatch would cause execution to fail.
- Removal of
GASandGASLIMIT: The V2 instruction set would omit these instructions. The stated aim is to prevent application logic from hardcoding assumptions about changing system costs and to reduce its dependence on underlying pricing rules.
These are proposed execution constraints, not instructions builders can assume are already active.
Migration and the proposed scaling rationale
The report said the design would not force existing contracts into risky rewrites. Decentralized finance protocols using upgradeable proxies could move to V2 implementations through later upgrades, while immutable contracts could remain inactive or continue operating under their original rules.
TechFlow presented the longer-term rationale as conditional: if activity gradually moved toward the new contracts, state-growth pressure could ease. If V2 execution reached a safe share of activity and storage growth were sufficiently contained, developers would have more room to raise the per-block Gas limit. The article supplied no numerical threshold or implementation timetable.
At the time of the report, EIP-8488 remained a Draft. TechFlow said it had been placed on that week’s All Core Developers Execution meeting agenda for peer review. That status describes a proposal under discussion, not an adopted network change or a demonstrated scaling result.