Ethereum has quietly released a draft EIP that could affect the lifecycle of contracts over the next decade: it lays the groundwork for repricing Gas with “versioned opcodes.”
The core logic has three layers:
1. Newly deployed contracts must use V2 opcodes and follow the new Gas schedule in EIP-8037/8038. Already-deployed contracts continue using the old schedule, preserving their behavior.
2. The V2 opcode set directly removes Gas introspection instructions such as GAS and GASLIMIT. If bytecode contains these opcodes, deployment will revert.
3. A new DELEGATECALL_V2 is introduced. Its semantics are similar to DELEGATECALL, but it requires the target contract’s code_version to be ≥ 2; otherwise, the call fails immediately.
Why should developers care? In the past, Ethereum’s biggest concern when adjusting Gas costs was that “repricing would change the behavior of existing contracts.” Protocols relying on hard-coded Gas assumptions have been burned more than once. With versioning, old contracts stay under the old rules while new logic follows the new ones—upgrades and compatibility finally have a clear boundary.
The trade-offs are just as clear: Gas introspection is being deliberately removed, so designs that rely on reading the remaining Gas on-chain in real time will need to be reworked in advance. The version requirement for DELEGATECALL_V2 will also force proxy contracts, multisigs, and smart wallets to review their entire call chain.
This is still a draft at the PR stage, with reviews, testing, and a hard fork still standing between it and mainnet. But the direction is clear: Ethereum is turning the “upgradable EVM” from a slogan into a mechanism. Holders of $ETH don’t need to take any action in the short term; developers are advised to read the original proposal soon and assess migration costs.
#以太坊 #EIP #Gas
The core logic has three layers:
1. Newly deployed contracts must use V2 opcodes and follow the new Gas schedule in EIP-8037/8038. Already-deployed contracts continue using the old schedule, preserving their behavior.
2. The V2 opcode set directly removes Gas introspection instructions such as GAS and GASLIMIT. If bytecode contains these opcodes, deployment will revert.
3. A new DELEGATECALL_V2 is introduced. Its semantics are similar to DELEGATECALL, but it requires the target contract’s code_version to be ≥ 2; otherwise, the call fails immediately.
Why should developers care? In the past, Ethereum’s biggest concern when adjusting Gas costs was that “repricing would change the behavior of existing contracts.” Protocols relying on hard-coded Gas assumptions have been burned more than once. With versioning, old contracts stay under the old rules while new logic follows the new ones—upgrades and compatibility finally have a clear boundary.
The trade-offs are just as clear: Gas introspection is being deliberately removed, so designs that rely on reading the remaining Gas on-chain in real time will need to be reworked in advance. The version requirement for DELEGATECALL_V2 will also force proxy contracts, multisigs, and smart wallets to review their entire call chain.
This is still a draft at the PR stage, with reviews, testing, and a hard fork still standing between it and mainnet. But the direction is clear: Ethereum is turning the “upgradable EVM” from a slogan into a mechanism. Holders of $ETH don’t need to take any action in the short term; developers are advised to read the original proposal soon and assess migration costs.
#以太坊 #EIP #Gas