Back to all reports

以太坊研究日报

Ethereum Research Daily

Another answer to Glamsterdam compatibility: the Versioned Opcodes draft has new contracts use V2 opcodes that carry the new gas schedule, while old contracts keep the old one, and V2 drops gas introspection opcodes such as GAS. The EF updated its blog post: it has received 4 reports of deployed contracts that could break, recommends that ACD wait until the audit results are public before deciding whether to change the specs or schedule Hoodi, and published a timeline from 11-12 to 11-19. Barnabé said Ethlabs supports work on post-quantum user accounts, and Ben Edgington explained PQDC.

Image for November 9, 2026

Image: GitHub, ethereum/EIPs PR #12638 Add EIP: Versioned Opcodes for Gas Repricing

Glamsterdam compatibility: two alternatives and the EF timeline

Leo Glisic's post

EIPs PR #12638: Add EIP: Versioned Opcodes for Gas Repricing, opened at 02:40. New contracts must use the V2 opcode set, charged by the new EIP-8037/8038 gas schedule; deployed contracts keep the legacy schedule; `DELEGATECALL_V2` requires the target to be V2 as well; and the gas introspection opcodes `GAS` and `GASLIMIT` are left out of V2. The discussion started from Leo Glisic's post.

https://x.com/Leo_Glisic/status/2118884109393215604

EF Blog update of 11-09: Glamsterdam gas changes and deployed contracts

Since Friday's post the EF has received 4 reports pointing to deployed contracts that could break under EIP-8037/8038, and it is reviewing each one and contacting the protocols that may be affected. It has also heard a broader concern that changes affecting immutable contracts are not getting the scrutiny they deserve. The EF recommends that ACD wait until the audit findings are public and there has been time to review them before deciding whether to revise the specs or when to schedule the Hoodi upgrade. Several possible revisions are already being prototyped, with notes on which problems each solves and which other invariants it would break, to be presented at ACDE on 11-19.

https://blog.ethereum.org/en/2026/11/06/glamsterdam-8037-8038

Post-quantum: user accounts and consensus-layer priorities

Other updates

Magicians: checking that a deployed contract still runs the audited commit

15:43. An explorer's "verified" badge only shows that some source compiles to the code at an address, not which commit it came from, and for a proxy it says nothing about the logic contract. How to do it: rebuild the audited commit with the same solc version, optimizer runs, viaIR and evmVersion, and compare the runtime bytecode.

https://ethereum-magicians.org/t/checking-that-a-deployed-contract-still-runs-the-audited-commit/30318

Community