以太坊研究日报
A daily record of what changed in Ethereum protocol work, research and the ecosystem.
Page 4 of 15 · October 15, 2026 to October 21, 2026
pcaversaccio pointed to a new ChainSecurity article: EIP-8037 and EIP-8038 can force some contracts to upgrade just to restore their intended behavior, even with no bytecode changes. That set the stage for the next day's ACDE decision to postpone Hoodi. On the spec side, EIP-8141 prices frame and signature entries at the floor, EIP-8279 checks the floor against the execution gas budget, and the post-quantum validator key registry was merged as a draft.
A Pre-ERC on Magicians about EOAs adopting code via SETCODEFROM drew 27 posts in a day. It points out that EIP-8298 plus EIP-8151 can retire a secp256k1 key without moving assets, but adoption is one-way, and it lists seven failure modes, most of them irreversible. ERC-7902 now uses frame transactions as the onchain transport for wallet AA capabilities. EIP-8198 (quick slots) now targets 10-second slots. 0xbow's Privacy Pools v2 went live, letting funds move, swap and earn yield inside a shielded pool. Frame Transaction Breakout #7 met today.
Pierre and winderica ported Tornado Cash to Flock, a post-quantum binary-field SNARK, proving a depth-32 withdrawal over SHA-256 in under 30 ms, and described a recovery protocol that lets existing pools survive a discrete log break. Vitalik argued that precompiles and the EVM are the wrong place for most cryptography support, because their data has to go into blocks as calldata. EIP-8288 proposes moving the recursive STARK into the execution payload, and tcoratger submitted a post-quantum validator key registry.
A Sunday. nero_eth and Barnabé both ran the numbers on Glamsterdam's capacity: the gas limit goes from 60M to 200M, about 3.3x, and 300M looks realistic as a next step, with more blob space too. EIP-8151 (account-code-restricted ecRecover) aligned with EIP-8038 access gas. In Starknet's non-binding vote, 99.95% of the voting power supports exploring a move to an independent post-quantum L1.
Alex Stokes and Trent promoted the Hoodi upgrade: a 200M gas limit, larger contract size, ETH transfers emitting logs and gas repricing. Account and transaction specs kept getting refined. EIP-8141 explains that storage refunds only lower what the payer pays, while the block still counts execution gas before refunds; EIP-8266 redefines its expiring-nonce mode under EIP-8250's nonce_keys/nonce_seq; and the POST_TX to ASSERT rename was merged.
The EF announced that Glamsterdam will activate on Hoodi at 17:42:48 UTC on October 26, with the gas limit raised to 200M at the same time. lightclient proposed two EIP-7906 changes: the POST_TX frame mode becomes ASSERT, and TXDIFF is removed with some of its functionality folded into TXTRACE. Vitalik combined zkAPI, Tor, cover traffic and local LLM prompt rewriting into a "paranoid mode" for his agent.
pcaversaccio compared the gas to deploy an ERC-20 under Osaka and Amsterdam: EIP-8037 adds 97,920 state gas for 64 SSTOREs, and he questioned why EIP-7997 is in Glamsterdam. Two EIPs from rakita (net gas metering for account changes, and persisting warm access sets across reverts) were merged as drafts. Frame transactions tightened further: checking signer key authority, default code in SENDER mode, and a single price for every data byte. Vitalik considers the zkEVM speed race won and says the focus should shift fully to security.