<?xml version='1.0' encoding='utf-8'?>
<rss version="2.0"><channel><title>ChainRook / en</title><link>https://chainrook.com/en/</link><description>Reviewed public articles only. Empty until approved material is available.</description><item><title>Ethereum schedules Hoodi’s Glamsterdam rehearsal, leaving mainnet timing open</title><link>https://chainrook.com/en/articles/hoodi-glamsterdam-rehearsal-not-mainnet-rollout-en</link><guid isPermaLink="true">https://chainrook.com/en/articles/hoodi-glamsterdam-rehearsal-not-mainnet-rollout-en</guid><description>&lt;p&gt;The Ethereum Foundation’s Protocol Cluster announced on 16 October that Glamsterdam is scheduled for the Hoodi testnet on 26 October at 17:42:48 UTC. The announcement says the mainnet activation date remains undecided. For infrastructure teams, the immediate significance is a dated test environment, not confirmation that Ethereum’s production network has completed another upgrade. &lt;a rel="noreferrer" href="https://blog.ethereum.org/2026/10/16/glamsterdam-hoodi-announcement"&gt;C1&lt;/a&gt;&lt;/p&gt;&lt;p&gt;The linked Hoodi configuration pull request was merged on 9 October. It specifies activation at epoch 132,352 and a gas-limit increase to 200 million at that epoch. This repository record supports the announced schedule, but a merged configuration cannot establish that a future activation succeeded. Nor is a gas limit a measurement of transactions processed under real-world demand. &lt;a rel="noreferrer" href="https://github.com/eth-clients/hoodi/pull/31"&gt;C2&lt;/a&gt;&lt;/p&gt;&lt;p&gt;One component, block-level access lists, records state accesses and changes so clients can organise execution work more efficiently. The proposal describes support for parallel processing. That is a technical design capability; actual performance will depend on implementations and workloads. Reading the specification alongside the schedule helps distinguish what software is intended to enable from what operators have demonstrated. &lt;a rel="noreferrer" href="https://eips.ethereum.org/EIPS/eip-7928"&gt;C3&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Chainrook’s analysis is that this rehearsal should be judged by coordination quality as well as headline capacity. Different client implementations need to agree on the same rules while operators manage their own upgrade paths. Useful evidence would include successful activation, continued agreement between clients, and clearly documented application behaviour. This article has not independently measured those outcomes.&lt;/p&gt;&lt;p&gt;The Foundation also directs Hoodi operators to compatible execution and consensus clients, while stating that this announcement requires no action from mainnet users. &lt;a rel="noreferrer" href="https://blog.ethereum.org/2026/10/16/glamsterdam-hoodi-announcement"&gt;C1&lt;/a&gt; That separation is important: testnet preparation should not be mistaken for instructions to move assets or for a production launch date.&lt;/p&gt;&lt;p&gt;The announcement, configuration repository and improvement proposal belong to the same Ethereum development process. They provide traceable primary evidence, not three independent validations of scaling success. This is original infrastructure analysis, with no price forecast, investment recommendation or claim of original reporting.&lt;/p&gt;</description><pubDate>Wed, 21 Oct 2026 03:37:02 +0000</pubDate></item></channel></rss>