BTCLiveETHLiveSOLLiveXRPLiveBNBLiveDOGELiveADALiveAVAXLive
CHARTING PARTNERTradingViewAdvanced charts, indicators and market tools.OPEN CHARTS →
Start with today’s trader mapBefore you leave: see the cross-asset levels, confirmations, invalidations and catalysts NetNapz is tracking for the next session.DAILY TRADER BRIEF →STRATEGY DESK →

Ethereum Urges Glamsterdam Compatibility Checks; Hoodi Fork Remains Delayed

Updated 18 November: Ethereum’s 16 November testing call reviewed wider contract-compatibility findings around EIP-8037 and EIP-8038. Core developers left the specification decision open for the 19 November execution-layer call; Hoodi remains unscheduled.

Ethereum illustration for Glamsterdam network upgrade coverage
Photo: DrawKit Illustrations / Unsplash

Latest material update: 18 November 2026. Originally published 18 September 2026. Each dated section identifies the evidence checked for that update.

16 November update: audit review identifies broader compatibility work

Evidence checked 18 November 2026. The official All Core Devs Testing #103 thread now includes the 16 November meeting summary and next steps. ChainSecurity reported 152 findings, 76 overlapping with the Ethereum Foundation’s internal search, for roughly 200 findings in the combined review. Dedaub’s impact study reported 70 medium-to-high-risk findings, including 22 contracts not previously identified by the Foundation’s study. The Foundation’s application-team analysis reported three high-severity issues and at least 25 medium-severity issues, with outreach and fixes in progress.

Those figures describe different review methods and overlap; they are not a verified count of distinct exploitable contracts. The meeting summary also records a developer estimate that roughly 10,000–15,000 contracts out of about 90 million could be affected. NetNapz has not independently reproduced the scans, classified the contracts or confirmed the value exposed. The discussion distinguished hard-coded gas assumptions and gas-cost increases from the reservoir mechanism itself.

The call ended without a final decision on whether EIP-8037 and EIP-8038 should proceed unchanged. Published next steps ask ChainSecurity to release its public report, Dedaub and the Foundation to continue outreach, and core developers to revisit the decision on the 19 November All Core Devs Execution call. The Ethereum Foundation’s continuing notice still lists no replacement Hoodi activation date and says no decision is precommitted.

NetNapz assessment: the review materially broadens the evidence behind the postponement, but it does not establish a live mainnet exploit, confirmed losses or a final upgrade design. The next publishable milestone is a documented specification decision and any revised client or testnet schedule after the 19 November call. There is no verified basis here for attributing a current ETH price move to the review.

9 November update: four deployed-contract reports enter review

Evidence checked 11 November 2026. The Ethereum Foundation’s continuing Glamsterdam notice was materially updated on 9 November. It says the Foundation received four reports identifying deployed contracts that could break under the proposed EIP-8037 and EIP-8038 changes. The Foundation is reviewing the reports and contacting potentially affected protocols. It does not name the contracts, verify exploitation or report losses.

The update also records a wider concern about changing behaviour relied on by immutable deployed contracts. ChainSecurity and Dedaub engagements are scheduled to end, with their reports published, on 13 November. The two auditors and the Foundation are due to present findings and take questions on the All Core Devs Testing call on 16 November. Possible revisions and next steps are scheduled for discussion on the execution-layer call on 19 November.

The published timetable explicitly says no decision is precommitted. The Foundation recommends waiting for public audit findings and review time before deciding whether to revise the specifications or schedule Hoodi. It says prototype revisions are being documented against the problems they might solve and the other assumptions they could break.

NetNapz assessment: the reported count makes the compatibility issue concrete but does not establish its eventual scope. Four reports may overlap, prove non-exploitable or reveal broader dependencies; the public audits and protocol responses will determine that. The actionable checkpoint is the 13–19 November review sequence, followed by any explicit client, specification and testnet scheduling decision. There is still no verified basis for describing Glamsterdam as active on Ethereum mainnet or attributing a current ETH price move to this review.

6 November: compatibility review broadens beyond fork configuration

The Ethereum Foundation’s 6 November developer notice says testnet work identified projects that could become vulnerable under Glamsterdam because they rely on assumptions changed by EIP-8037 and EIP-8038. Those proposals change operation pricing and state-gas accounting. The notice says AllCoreDevs decided not to fork Hoodi until the issues are resolved, while Hegota work continues separately.

The Foundation is working with ChainSecurity and Dedaub and conducting internal reviews, but says that effort cannot cover every project’s onchain and offchain code. It asks developers and auditors to check eight listed invariants. The notice supplies no replacement Hoodi activation date and does not establish an affected-project count, a live mainnet exploit or a loss total.

What the published checklist adds

The linked official compatibility repository distinguishes changed prices from changed gas-accounting assumptions. It flags hard-coded gas limits, reserves around external calls, calculations based on differences in gasleft(), handling of failed calls and assumptions about EIP-7702 delegation. Offchain receipt-processing assumptions can also matter. Its examples are testing aids for the proposed rules, not proof that every contract using those patterns is vulnerable.

The repository says most findings so far relate to fixed gas amounts and gas reserves or stipends. It asks teams to examine their own code and report reproducible problems privately to the Foundation. NetNapz has reviewed the published checklist and the linked ChainSecurity technical explainer; it has not audited contracts or reproduced the examples.

NetNapz assessment: this adds a concrete compatibility-review dependency to the postponed testnet schedule. Developers should evaluate application logic, configuration and supporting services together rather than treat a client release as a complete readiness check. Potential specification changes and application fixes still need decisions and testing. The warning alone supplies no basis for claiming an active Ethereum outage, a mainnet exploit or a predictable ETH price response.

Sources checked 6 November 2026. Original publication remains 18 September. Earlier client deadlines and evidence below retain their original dates; the former 26 October activation time has passed and is not an upcoming catalyst.

26 October update — Geth confirms execution-client schedule removal

Checked 26 October 2026. Geth v1.17.10, published 23 October, removes the Amsterdam execution-layer activation previously set for Hoodi on 26 October at 17:42:48 UTC. Its release notes instruct Hoodi operators running v1.17.9 to upgrade before that former activation time. A replacement date will be set in a future release; other networks are unaffected by this scheduling change.

This supplies the execution-client confirmation missing from the earlier Lighthouse-focused update. Operators should follow the release instructions for their own execution and consensus clients rather than assume a consensus-client update changes both layers. NetNapz checked the published Geth release notes, not installed binaries or network-wide adoption.

NetNapz assessment: The remaining deadline concerns removal of obsolete client configuration, not a fork proceeding today. This release does not reverse the postponement or establish a mainnet activation date. No current price, flow or deployment figures were checked.

23 October update — Hoodi activation postponed

Checked 23 October 2026. In its 22 October postponement notice, the Ethereum Foundation says Hoodi’s planned 26 October Glamsterdam activation has been removed, with no replacement date set. Developers want more time to investigate EIP-8037’s interactions with existing mainnet smart contracts.

The change removes both the Amsterdam execution-layer and Gloas consensus-layer schedules, together with the planned increase to a 200 million gas limit. It changes future configuration without reversing Hoodi’s chain history. The earlier activation announcement is superseded. Mainnet users and ETH holders have no action to take because of this notice, and no Glamsterdam mainnet date is established.

Lighthouse release changes the operator deadline’s meaning

Lighthouse v8.3.2, published 23 October, disables Hoodi’s scheduled Gloas fork. Its developers instruct Hoodi users to upgrade before the former activation time, 26 October at 17:42:48 UTC. Staking operators must update the beacon node, validator client and execution client. The release supersedes v8.3.0 and v8.3.1’s Hoodi fork instructions; it requires no mainnet upgrade.

For both client layers, the Foundation directs operators to releases explicitly confirming removal of the old activation. Earlier compatibility tables alone are insufficient. Lighthouse’s release verifies its consensus-client change; it does not establish that every execution client or deployed node has adopted revised settings.

NetNapz assessment: The immediate catalyst is correct client configuration and investigation of contract compatibility, followed by a replacement test schedule. A tagged binary is evidence of a software change, while network-wide adoption and successful future activation require separate checks. The Arbitrum payload review remains a distinct dependency and cannot supply an Ethereum activation date. No live price, flow or deployment measurement was checked for this update.

Earlier dated reporting — October 26 activation instructions superseded

Historical context: The following preserves earlier source checks. References to a scheduled 26 October Hoodi activation, its gas-limit increase and the next fork checkpoint are superseded by the 22 October Foundation notice and the latest update above. The earlier certificate-security advice and Arbitrum analysis address separate issues.

23 October update — Arbitrum payload review and refunder dependency

Checked 23 October 2026. Offchain said on 21 October that its Glamsterdam fee payload was finalized, tested and audited. The linked Trail of Bits summary, dated 19 October, reports a two-consultant review on 8–9 October, totalling four engineer-days. It covered the fork gate, parameter-update action and generated payload at governance commit 0b5d89306bb07f4d9f03ad645e67b840ff0f28e2.

The reviewers identified no security issues within that scope. Their report cautions that a time-limited assessment is not an exhaustive guarantee. It does not establish governance approval, execution or live parameter values.

In the proposal discussion on 22 October, L2BEAT reiterated that the proposed batch charge assumes Arbitrum One’s gas refunder has been removed through a separate configuration change outside this proposal. Nova already operates without one. Delegate statements of support do not establish a final onchain result.

NetNapz assessment: The review adds implementation evidence, while the refunder setting remains a separate operational dependency. Final approval, execution and deployment state were not verified in this pass. The 19 October section below preserves the earlier evidence state.

22 October afternoon update — experimental builder bid streaming

Checked 22 October 2026 at 15:25 UTC / 16:25 BST. Lighthouse v8.4.0-rc.0, published 22 October, adds experimental builder bid streaming for Gloas. Sigma Prime explicitly warns against running this release with mainnet validators. The feature is off by default and applies only after Gloas.

With streaming enabled, the beacon node opens a connection to selected builders roughly one second before a slot, allowing improved bids to replace earlier ones before block production. The release describes fallback to HTTP when a connection fails or a bid is invalid. A connected stream that delivers no bid does not trigger that fallback. These are developer-described behaviours; NetNapz has not tested them.

The linked implementation pull request #10418 was merged on 22 October. It documents limits on message size, message count and bytes received.

NetNapz assessment: This offers a concrete testing path for builder communication and fallback behaviour. It supplies no measured evidence of higher validator income, stronger censorship resistance or mainnet readiness. The stable certificate-security update described below remains a separate maintenance issue.

22 October update — Lighthouse certificate fix and Hoodi client readiness

Checked 22 October 2026 at 11:18 UTC / 12:18 BST. This update adds client releases published on 21–22 October; the article was originally published on 18 September.

Sigma Prime’s Lighthouse v8.3.1 release, published 22 October, updates trusted certificates to mitigate what its developers describe as a compromised eMudhra certificate authority. The team urges Lighthouse users on every network to update as soon as practical, highlighting HTTPS connections such as checkpoint sync, Web3Signer and validator-client-to-beacon-node links. Its priority table rates both beacon-node and validator-client updates high for staking users.

This certificate change has a broader scope than the testnet fork. The same release reminds Hoodi operators to use Lighthouse v8.3.x before 26 October. It does not establish that an Ethereum validator was compromised, and NetNapz has not independently investigated the certificate-authority incident.

Geth v1.17.9, published 21 October, configures Hoodi’s Amsterdam execution fork for timestamp 1,793,036,568, matching 26 October at 17:42:48 UTC. Its notes also report fixes involving power-failure database corruption, concurrent state reading and an RPC/block-processing path that could corrupt a block-level access list. These are developer-reported fixes; NetNapz has not reproduced the defects or benchmarked the release.

The Foundation’s Hoodi announcement, dated 16 October and rechecked today, lists both versions among compatible clients. Operators need compatible execution and consensus software; installing only one layer is insufficient. Mainnet remains unscheduled in that announcement.

NetNapz assessment: Available binaries make the rehearsal more actionable, while the certificate update is an immediate software-maintenance issue for Lighthouse operators. Neither proves successful Hoodi activation or changes Ethereum mainnet’s timetable. The next evidence is operation through the scheduled fork, rather than a release tag alone.

Hoodi scheduled for 26 October; mainnet still undated

The Ethereum Foundation’s announcement published 16 October says Glamsterdam activated on Sepolia on 6 October. Hoodi is scheduled for 26 October 2026 at 17:42:48 UTC, epoch 132,352 and slot 4,235,264. Hoodi’s gas limit is scheduled to rise to 200 million at that epoch. No mainnet activation date has been decided.

Hoodi operators must install compatible execution and consensus clients before activation; validators must update both beacon-node and validator software. The Foundation is adding confirmed versions to its release tables. This announcement requires no mainnet action.

The upgrade brings proposer-builder separation into the protocol and introduces block-level access lists for parallel validation. Developers should test contracts and gas estimates against the changed accounting, especially fixed gas limits and stipends.

NetNapz assessment — 16 October

A dated Hoodi rehearsal moves the next checkpoint beyond Sepolia, but does not demonstrate production readiness or lower mainnet fees. Watch client readiness, finality and payload delivery through the test before treating capacity ambitions as delivered. This is a technical milestone, not evidence of ETH buying, ETF inflows or a price forecast.

Source check: the Foundation announcement’s indexed text and activation table were retrieved; direct page opening was unavailable. No new market prices or flows are asserted.

19 October update — Arbitrum fee proposal adds a downstream dependency

Arbitrum’s 19 October governance roundup lists a temperature check ending 22 October on preparing One and Nova for Glamsterdam. This is not final onchain approval or execution.

The 7 October proposal would raise parentGasFloorPerToken from 10 to 16 and perBatchGasCharge from 210,000 to 480,000. These govern Ethereum posting-cost estimates, not an ArbOS upgrade. An 18 October delegate response asks for clearer evidence separating fork-related costs from a gas-refunder assumption.

The linked Foundation repository pull request #384, still open when checked, describes a gate intended to reject execution before Ethereum’s fork is active. Its implementation notes explicitly assume posting without a gas refunder and say Arbitrum One’s refunder must be removed before execution. NetNapz inspected the public proposal and implementation description, but did not run tests or verify deployed state.

NetNapz assessment: Ethereum readiness and downstream fee calibration are separate operational checks. Larger parameter values do not establish an equivalent percentage increase in a user’s total transaction bill: that also depends on batch composition and other fee components. A temperature check, a reviewed payload and a successfully executed change should not be treated as interchangeable milestones.

Scoped proposal and repository check: 19 October 2026. Original publication remains 18 September; the Ethereum schedule above retains its 16 October source date. No new live prices or activation result are asserted.

Historical reporting and assessment — 18 September, with 3 October update

Archive: The following preserves the earlier article, including its then-current schedule and market assessment. These are historical observations, not current guidance; the 16 October update above supersedes its pending Sepolia/Hoodi references.

Ethereum developers have fixed October 6 as the public Sepolia test date for Glamsterdam, the network's next major upgrade, after a private rehearsal successfully continued finalizing blocks under the new block-building rules. The upgrade is designed to expand how much activity Ethereum can process while bringing the relationship between validators and specialized block builders more directly into the protocol.

Update checked 3 October 2026: The Ethereum Foundation’s announcement, dated 28 September, confirms Sepolia activation for 6 October 2026 at 13:53:36 UTC, epoch 353,024 and slot 11,296,768. Hoodi and mainnet dates remain undecided; the earlier tentative October 27 Hoodi date is superseded. Sepolia operators must update both execution and consensus clients to compatible releases before activation. This is a testnet milestone, not a mainnet launch.

The technical change investors should understand

Glamsterdam is testing block-level access lists and a much larger block gas ceiling. In the latest rehearsal, Nethermind's execution client completed 2,302 performance tests while developers experimented with a 200 million gas limit. The aim is to let nodes identify the accounts and storage a block will touch before execution, making more parallel processing possible and giving Ethereum more room to absorb payments, swaps and application activity before fee pressure rises.

That 200 million figure is a test setting, not a promise for mainnet. Larger blocks increase capacity but also make validation more demanding. Ethereum's challenge is therefore to gain throughput without pushing hardware requirements so high that smaller validators are squeezed out.

The builder risk

The immediate risk is specific to the test environment. Developers warned that a malicious operator could create disposable builder identities, submit unrealistically high bids using free test ether, win repeated block auctions and then withhold the promised transaction payloads. That could stall Sepolia traffic and make the dress rehearsal less useful.

The scenario does not imply that mainnet ETH funds are at risk. Sepolia ether has no meaningful economic value. The concern is whether the public test can produce reliable evidence about Glamsterdam under realistic conditions and whether clients can identify and reject builders that repeatedly fail to deliver payloads.

Historical market context — 18 September 2026

The following market observations describe the original publication date. They have not been revalidated as current prices or flows.

ETH is trading into the upgrade story during a broader crypto rebound. CoinDesk reported ether around $2,553 on September 18, up roughly 3.8% on the day, while bitcoin approached $80,000 and SOL showed stronger gains. At the same time, U.S. spot ether ETFs recorded roughly $39 million of net outflows on Thursday, following heavier withdrawals earlier in the week. That creates a mixed backdrop: improving spot price action, but less convincing institutional flow in the very short term.

Macro conditions remain restrictive. Reuters reported the U.S. 10-year Treasury yield above 5% on Friday and crude oil still above $100. Higher yields can pressure high-duration risk assets, so Ethereum's protocol catalyst is competing with a difficult rates environment.

Bullish case

The bullish case is that Sepolia runs cleanly, clients handle malicious or non-performing builders, and the Hoodi test follows without a material delay. Successful testing would reduce execution risk around an upgrade intended to expand capacity. If ETH simultaneously gains relative strength against BTC and ETF flows stabilize, the market could begin pricing Glamsterdam as a credible network-efficiency catalyst rather than simply a future roadmap item.

Another constructive signal would be stronger activity across Ethereum and its layer-2 ecosystem. Layer-2 and DeFi tokens were among Friday's leaders, with Arbitrum and Starknet both posting double-digit gains. Sustained breadth would suggest the market is rewarding the broader Ethereum scaling stack rather than only trading ETH beta.

Bearish case

The bearish case is not that one Sepolia disruption breaks Ethereum. It is that repeated builder problems delay the test sequence, expose implementation gaps or push mainnet activation further out. A failed or noisy test could weaken confidence just as high Treasury yields and ETF outflows are already limiting the macro case for ETH.

Investors should also avoid treating the 200 million test gas limit as guaranteed production capacity. If developers conclude that the hardware or propagation burden is too high, the final configuration could be more conservative.

NetNapz assessment

Bias: cautiously bullish, but confirmation required. Glamsterdam is a meaningful fundamental catalyst because it targets capacity and block-building infrastructure, and the successful private rehearsal is constructive. The public Sepolia test is now the decision point. The strongest setup would combine a clean October 6 test, no material schedule slippage, ETH holding its recent recovery and improving ETF flows.

Invalidation: repeated test failures, a significant delay to Hoodi or mainnet, ETH losing relative strength while Treasury yields continue climbing, or sustained institutional outflows would weaken the bullish thesis.

Buy, sell or wait?

NetNapz stance: WAIT / WATCH FOR CONFIRMATION. This is an editorial market stance, not a personalized instruction. For a market participant using the upgrade as a catalyst, the evidence is constructive but incomplete. A successful Sepolia test plus improving ETH/BTC relative strength would provide stronger confirmation; a test disruption or renewed market-wide risk-off move would argue for patience.

What to watch next

Watch the October 6 Sepolia activation, compatible client releases, builder rejection and fallback behavior, and subsequent official Hoodi and mainnet announcements. ETH/BTC relative strength, ETF flows and Treasury yields remain separate market confirmation signals; the September 18 market figures above are historical context, not current quotes.

Sources

CoinDesk — Glamsterdam dates and builder-risk warning

CoinDesk — Glamsterdam rehearsal and capacity testing

CoinDesk — Ether ETF flows and crypto market performance

Reuters — September 18 cross-asset market backdrop

NetNapz market monitoring and editorial analysis only. Not personalized financial advice.

Scroll to Top