OPEN INTEREST

LEAD: Ethereum postponed Hoodi’s Glamsterdam activation. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] The Ethereum Foundation withdrew the activation scheduled for 26 October 2026. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] Its notice gives no replacement date. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] Core developers delayed the testnet upgrade to investigate interactions between EIP-8037 and mainnet smart contracts, according to the Foundation’s notice. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] The change removes both the Amsterdam execution upgrade and the Gloas consensus upgrade from Hoodi’s scheduled activation. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] The postponement also removes a planned increase in Hoodi’s gas limit to 200 million at the activation epoch. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] The Foundation describes a configuration change for a future upgrade; Hoodi’s chain history remains intact. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] The operational distinction matters in the Foundation’s instructions: the earlier announcement’s client tables do not establish compatibility with the postponement. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] The notice directs operators to release notes explicitly confirming removal of the scheduled activation. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] Both execution and consensus clients fall within that guidance, alongside validator software and external block-building infrastructure. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] The Foundation also withdraws the earlier activation instructions, making the postponement notice the controlling announcement for Hoodi testing. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] The announcement sets no Glamsterdam mainnet activation date and requires no action from mainnet users or ETH holders. [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] ALSO TODAY: [STAKING] Lido contributors request 0.5 ETH for proof reporting. [https://research.lido.fi/t/csm-prover-bot-funding/8378/12] The 7 October 2026 proposal budgets approximately 500 balance-proof transactions as CSM 0x02 fills its stake allocation. [https://research.lido.fi/t/csm-prover-bot-funding/8378/12] Its estimate assigns approximately 0.27 ETH to those transactions at 2 gwei, with additional funding covering slashing and withdrawal proofs. [https://research.lido.fi/t/csm-prover-bot-funding/8378/12] [SECURITY] Ethereum researchers propose checks on transaction outcomes. [https://blog.ethereum.org/2026/10/05/transaction-assertions] The Foundation’s 5 October 2026 post describes assertions that inspect final state changes and revert actions that violate signed rules. [https://blog.ethereum.org/2026/10/05/transaction-assertions] It identifies EIP-7906 as a possible approach, while stating that inclusion in Hegotá remains unconfirmed. [https://blog.ethereum.org/2026/10/05/transaction-assertions] [PRIVACY] zkAPI separates usage payments from billing identity. [https://blog.ethereum.org/2026/10/01/introducing-zkapi] The development team’s 1 October 2026 post describes Ethereum deposits and zero-knowledge proofs authorizing metered API usage. [https://blog.ethereum.org/2026/10/01/introducing-zkapi] Its stated limits include correlation through network metadata and identifying prompt contents. [https://blog.ethereum.org/2026/10/01/introducing-zkapi] READING LIST: [https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay] The primary notice distinguishes withdrawn activation settings from client release requirements. [https://research.lido.fi/t/csm-prover-bot-funding/8378/12] The funding request exposes its transaction counts and gas-price assumption. [https://blog.ethereum.org/2026/10/05/transaction-assertions] The research explains why an assertion’s source matters alongside its enforcement. [https://blog.ethereum.org/2026/10/01/introducing-zkapi] The implementation account states the remaining privacy limits. METHOD: The sweep searched Ethereum research and Foundation blogs, Flashbots discussions, and Lido governance, targeting 25–27 October 2026, a 48-hour window. Verified coverage extends to dated October material; this edition does not establish a complete account of that window. Lido’s index showed 26 October 2026 activity, but inaccessible replies were cut from substantive reporting. [https://research.lido.fi/] Claims about a replacement Hoodi date were cut for failed verification. Included technical claims rest on primary project publications; no claims rest on secondary reporting. The house guide governed drafting. [https://raw.githubusercontent.com/openinterest-ai/paper/main/style-guide.html]