The Ethereum core developer community has made another move: an EIP draft titled “Versioned Opcodes for Gas Repricing” has been formally posted on the forum for public comment. The core idea is to add version numbers to opcodes so that future adjustments to Gas costs won’t require hard-fork-style changes that break already-deployed contracts.
Specifically, the draft has several key points:
First, old and new versions run in parallel, with backward compatibility. Newly deployed contracts must use V2 opcodes and follow the new Gas schedule defined in EIP-8037/8038; existing contracts already deployed will continue using the old schedule, with their behavior unchanged. This effectively confines the impact of “price increases” to new contracts.
Second, the V2 opcode set deliberately removes Gas introspection opcodes such as GAS and GASLIMIT. If a new contract’s bytecode contains these opcodes, deployment will revert immediately. The developer community’s reasoning is that if a contract relies too heavily on precise checks of its remaining Gas, any future repricing could trigger cascading failures. It’s better to cut this coupling off at the source.
Third, DELEGATECALL_V2 is introduced. Its semantics are similar to those of classic DELEGATECALL, but it requires the target contract’s code_version to be at least 2; otherwise, the call fails immediately. This prevents new-version contracts from mistakenly calling old logic and relying on outdated Gas assumptions.
Overall, this is a foundational design intended to pave the way for Ethereum’s long-term upgradability: Gas pricing has never been a static parameter, and versioned opcodes give the protocol a smooth adjustment path that “affects only new contracts, without impacting old ones.” For developers, the next things to watch are when migration toolchains and auditing rules will catch up. For ordinary users, the short-term on-chain experience won’t feel any different, but this could profoundly shape how smart contracts are written over the next few years.
#以太坊 #EIP
Specifically, the draft has several key points:
First, old and new versions run in parallel, with backward compatibility. Newly deployed contracts must use V2 opcodes and follow the new Gas schedule defined in EIP-8037/8038; existing contracts already deployed will continue using the old schedule, with their behavior unchanged. This effectively confines the impact of “price increases” to new contracts.
Second, the V2 opcode set deliberately removes Gas introspection opcodes such as GAS and GASLIMIT. If a new contract’s bytecode contains these opcodes, deployment will revert immediately. The developer community’s reasoning is that if a contract relies too heavily on precise checks of its remaining Gas, any future repricing could trigger cascading failures. It’s better to cut this coupling off at the source.
Third, DELEGATECALL_V2 is introduced. Its semantics are similar to those of classic DELEGATECALL, but it requires the target contract’s code_version to be at least 2; otherwise, the call fails immediately. This prevents new-version contracts from mistakenly calling old logic and relying on outdated Gas assumptions.
Overall, this is a foundational design intended to pave the way for Ethereum’s long-term upgradability: Gas pricing has never been a static parameter, and versioned opcodes give the protocol a smooth adjustment path that “affects only new contracts, without impacting old ones.” For developers, the next things to watch are when migration toolchains and auditing rules will catch up. For ordinary users, the short-term on-chain experience won’t feel any different, but this could profoundly shape how smart contracts are written over the next few years.
#以太坊 #EIP