Glamsterdam has no mainnet date yet
Ethereum's next hard fork: builders bid for blocks inside the protocol (ePBS), blocks list what they touch (BALs) and many gas prices change. Live on Sepolia since 6 Oct 2026; Hoodi postponed on 22 Oct while the gas changes (EIP-8037/8038) are audited; no mainnet date.
Client teams set the mainnet date only after Hoodi forks cleanly. Hoodi was postponed on 22 Oct 2026 and has no new date. Forkcast planning assumption, not an announced date. Source: EF: Glamsterdam on Hoodi postponed (22 Oct 2026) (checked 12 Nov 2026).
What do I have to do?
Holders
Nothing to do
ETH in your own wallet stays as it is. No token swap, no claim. Anyone asking you to "migrate" ETH for Glamsterdam is a scam.
Source: EF: Glamsterdam on Hoodi postponed (22 Oct 2026) (checked 12 Nov 2026)
Exchange users
Nothing to do
Expect ETH and ERC-20 deposits/withdrawals to pause for a short window around the mainnet fork (Binance did this for Fusaka). Trading usually continues.
Source: Cryptorank: Binance ETH pause for Fusaka (Dec 2025) (checked 12 Nov 2026)
Stakers
Nothing yet
No mainnet release exists yet. When the mainnet date is set you must update both the beacon node and the validator client, and review ePBS duties and your gas-limit setting. Liquid stakers and pooled stakers: nothing to do.
Source: EF: Glamsterdam Hoodi announcement (16 Oct 2026) (checked 12 Nov 2026)
Node operators
No mainnet release yet
Mainnet-ready versions are not out. Keep execution and consensus clients on current releases; the last Hoodi-ready set (after the postponement) is listed below for reference.
Source: EF: Glamsterdam on Hoodi postponed (22 Oct 2026) (checked 12 Nov 2026)
Developers
Your gas assumptions may break
Hard-coded gas limits and stipends can fail: EIP-8037 raises the cost of creating state, EIP-2780 changes intrinsic gas, EIP-7976/7981 raise calldata and access-list cost, EIP-7708 adds a log to every ETH transfer. Check your contracts against the eight invariants in ethereum/glamsterdam-gas-invariants; the EF asks affected projects to write to [email protected].
Source: EF: EIP-8037/EIP-8038 Glamsterdam (6 Nov 2026) (checked 12 Nov 2026)
Your transactions after Glamsterdam
Paste an address to see how much gas your recent transactions would use under the new gas rules.
We read up to 40 transactions you sent (Blockscout) and re-price their gas with the Glamsterdam schedule. Your address is not stored or logged. Same gas price as you paid, so only the gas amount changes.
Assumptions and limits
Rules from the Last Call specs as of 12 Nov 2026. The EF said on 6 Nov that ACD may still revise EIP-8037/8038, so these numbers can change.
- EIP-2780: a call without ETH value pays TX_BASE_COST 12,000 + cold recipient 3,000
- EIP-2780: a transfer with ETH value adds TX_VALUE_COST 6,000 (unchanged 21,000 total)
- EIP-2780/8037: sending ETH to an address that has never existed adds 120 bytes × 1,530 state gas
- EIP-8038: changing an existing storage slot (cold) 2,100 + 2,900 to 2,100 + 10,000
- EIP-8037/8038: writing a storage slot that was empty 2,100 + 20,000 to 2,100 + 10,000 + 64 × 1,530
- EIP-8038: first touch of another contract 2,600 to 3,000
- EIP-7976: calldata floor 10 gas per token (40/byte non-zero) to 64 gas per byte
Without an execution trace we cannot see every storage write. Plain ETH transfers and the base cost are exact. Token transfers and approvals infer "new slot or not" from the gas you used. Swaps and other calls use typical profiles and show a range. Gas refunds, warm/cold details inside contracts, EIP-7702 authorizations and deployments are not modelled. Block-level changes (ePBS, BALs) do not change what you pay per gas.
Client versions for node operators
Hoodi-ready releases listed by the EF after the postponement (22 Oct 2026). Mainnet versions: not released yet.
| Client | Hoodi release (reference) | Latest stable (live) | |
|---|---|---|---|
| Geth Execution | v1.17.10 | v1.17.10 23 Oct 2026 | Hoodi-ready (mainnet release pending) |
| Nethermind Execution | 2.2.1 | 2.2.2 26 Oct 2026 | Hoodi-ready (mainnet release pending) |
| Besu Execution | 26.10.1 | 26.11.0 13 Nov 2026 | Hoodi-ready (mainnet release pending) |
| Erigon Execution | v3.8.1 | v3.8.1 23 Oct 2026 | Hoodi-ready (mainnet release pending) |
| Reth Execution | v2.8.1 | v2.11.0 11 Nov 2026 | Hoodi-ready (mainnet release pending) |
| Ethrex Execution | v30.0.1 | v31.0.0 2 Nov 2026 | Hoodi-ready (mainnet release pending) |
| Prysm Consensus | v7.3.1 | v7.3.1 22 Oct 2026 | Hoodi-ready (mainnet release pending) |
| Lighthouse Consensus | v8.3.2 | v8.3.3 9 Nov 2026 | Hoodi-ready (mainnet release pending) |
| Teku Consensus | 26.10.2 | 26.10.3 27 Oct 2026 | Hoodi-ready (mainnet release pending) |
| Nimbus Consensus | v26.10.2 | v26.10.2 24 Oct 2026 | Hoodi-ready (mainnet release pending) |
| Lodestar Consensus | v1.50.1 | v1.50.1 22 Oct 2026 | Hoodi-ready (mainnet release pending) |
| Grandine Consensus | v3.0.0-rc.2 | 2.0.6 3 Aug 2026 | Latest stable is older than the Hoodi release |
Versions: EF: Glamsterdam on Hoodi postponed (22 Oct 2026) (checked 12 Nov 2026). Latest stable is read from each project's GitHub releases feed. All clients on the Patch Radar
Readiness
Client mix (not version readiness) is tracked by clientdiversity.org and ethernodes.org.
Exchange pause board
Right now
| Network | Binance | KuCoin | Kraken | Coinbase | Gate | Bitget |
|---|---|---|---|---|---|---|
| ETH Ethereum mainnet | Open | Open | Open | Open | Open | Open |
Last check 5 min ago. Coinbase's status page does not split deposits from withdrawals. "—" means the exchange does not list that network or does not report it.
Pauses around this fork
No pauses yet. We record every change in the 3 days before and 10 days after the fork.
Exchange notices
- Binance Wallet Maintenance for Ethereum Network (ETH) - 2026-10-28 27 Oct 2026
- Binance Wallet Maintenance for Ethereum Network (ETH) - 2026-10-15 14 Oct 2026
Timeline and date slips
- 24 Apr 2026 First combined Glamsterdam devnet (glamsterdam-devnet-0) Forkcast devnet data
- 17 Aug 2026 Platåberget community testnet launched with Glamsterdam rules EF blog
- 24 Aug 2026 EF: Glamsterdam Repricing Impact for Smart Contract Developers EF blog
- 14 Sep 2026 glamsterdam-devnet-11 (final happy-path devnet for L2s) Forkcast devnet spec
- 6 Oct 2026 Sepolia forked (epoch 353,024) EF: Glamsterdam testnet announcement (Sepolia)
- 16 Oct 2026 Hoodi scheduled for 26 Oct (epoch 132,352) EF: Glamsterdam Hoodi announcement (16 Oct 2026)
- 22 Oct 2026 Hoodi postponed over EIP-8037 contract risks (ACDE #248) EF: Glamsterdam on Hoodi postponed (22 Oct 2026)
- 6 Nov 2026 EF: 8037/8038 may be revised; contract audits by Dedaub and ChainSecurity under way EF: EIP-8037/EIP-8038 Glamsterdam (6 Nov 2026)
- 16 Nov 2026 ACDT: audit findings presented EF: EIP-8037/EIP-8038 Glamsterdam (6 Nov 2026)
- 19 Nov 2026 ACDE: findings and next steps (no decision pre-committed) EF: EIP-8037/EIP-8038 Glamsterdam (6 Nov 2026)
- Pending New Hoodi date
- Pending Mainnet date and mainnet client releases
The target moved 3 times
| When | Was | Became | Source |
|---|---|---|---|
| 4 May 2026 | Mainnet targeted for H1 2026 | Pushed to the second half of 2026 | OneKey, 4 May 2026 |
| 3 Sep 2026 | Sepolia 25 Aug (earlier plan) | Sepolia 6 Oct (ACDC #186) | 24/7 Wall St, 11 Sep 2026 |
| 22 Oct 2026 | Hoodi 26 Oct 2026 | Hoodi postponed, no date | EF: Glamsterdam on Hoodi postponed (22 Oct 2026) |
What changes, EIP by EIP
EIP-2780 Resource-Based Intrinsic Transaction Gas EL ScheduledChanges base tx cost for more efficiency in cold/hot state management and improving ETH monetary functions. Lowering basic ETH tranfers to 6,000 gas and charging extra 25,000 for new account creation. Alternative to increasing block gas limit.
- Users: Lower fees means it's easier to use ETH for payments.
- App developers: Changes how fee is managed based on accessed state, lowers base cost for every kind of transaction.
- Wallets: The fee cost estimation needs to be updated with new changes and complexity.
- Tooling: Transaction analysis needs to distinguish new gas accounting.
- L2s: L2s aiming to be EVM compatible need to implement this change, ETH will can better for payments even on L2 chains.
- Stakers & nodes: No direct impact, state growth should stay constrained.
- CL clients: No direct impact on consensus.
- EL clients: Changes in tx processing and gas accounting, potential performance overhead like gas limit increase
EIP-7688 Forward Compatible Consensus Data Structures CL ScheduledThis EIP stabilizes Merkle tree indices for all consensus data, preventing coincidental verifier breakage when fields are added, removed, or list capacities change during Ethereum upgrades.
- Users: No direct impact
- App developers: Less maintenance for EIP-4788 based projects.
- Wallets: No direct impact.
- Tooling: Less maintenance for consensus light client components.
- L2s: Less maintenance for light client based bridges.
- Stakers & nodes: Fewer required upgrades of staking pool delegate contracts.
- CL clients: Greater flexibility for future consensus design changes.
- EL clients: No direct impact.
EIP-7708 ETH Transfers Emit a Log EL ScheduledMake every ETH transfer—including from contracts and SELFDESTRUCT—emit an event log. Apps and explorers can track ETH movements uniformly, similar to ERC-20 transfers, improving deposit detection and reducing ad-hoc tracing.
- Users: Deposits and withdrawals are detected more reliably across apps and exchanges; no change to how users send or receive ETH.
- App developers: Can subscribe to a standard ETH transfer log instead of tracing; requires small updates to indexers and business logic.
- Wallets: Optionally watch a canonical event for ETH transfers to improve UX; otherwise existing send/receive flows remain unchanged.
- Tooling: Explorers and data indexers must parse and surface the new log; moderate engineering to integrate, test, and backfill if desired.
- L2s: Rollups mirroring L1 EVM semantics may add the same log for consistency; others have no direct requirements.
- Stakers & nodes: More log entries per block; execution node receipts grow slightly, increasing storage and bandwidth requirements for some RPC setups.
- CL clients: No consensus-layer changes anticipated; minimal or no code modifications beyond recognizing updated receipt sizes from execution payloads.
- EL clients: Implement emitting a log on value-transferring CALLs, transactions, and SELFDESTRUCT; update EVM and receipt construction; add tests.
EIP-7732 Enshrined Proposer-Builder Separation CL ScheduledProposes the decoupling of the consensus block from the execution payload, both in broadcast and validation. This feature enables L1 scaling by significantly changing the time required to both broadcast and executing the payload together with all the blob data, from the current ~2 seconds to aproximately ~9 seconds. It allows for a maximum portion of the slot to be spent in propagation large data.
- Users: Second order effect of lower prices and higher tx throughput.
- App developers: No direct impact. It enables applications to leverage previous builder information, something that is not currently available. It enables trustless preconfirmation schemes.
- Wallets: No direct impact. It enables wallets to send encrypted txs to anonymous builders.
- Tooling: Explorers and block monitors need updates to handle the separation of the beacon block from the payload.
- L2s: Second order effect of higher blob count being possible.
- Stakers & nodes: Major changes and updates are needed for trustless monitoring in staking pools. Staking UX is improved by a refined builder picking and monitoring.
- CL clients: Major changes for CL clients
- EL clients: No changes for EL clients.
EIP-7778 Block Gas Accounting without Refunds EL ScheduledCloses a loophole where gas refunds let blocks pack extra work. Refunds still reduce user costs, but don't shrink the block's counted gas. Aligns block size with real EVM work and reduces worst-case block-size variance.
- Users: No substantial direct impact; transactions execute as before. Refunds still discount user costs but no longer shrink counted block gas.
- App developers: Contracts generally unchanged. Only strategies exploiting large refunds lose ability to help pack extra computation into blocks via accounting quirks.
- Wallets: No changes required. Gas estimation, fee math, and refund display remain the same at the transaction level for users today.
- Tooling: Block builders, simulators, and analyzers should enforce and reflect gross block-gas accounting; update tests and dashboards to avoid refund-based variance.
- L2s: Minimal direct impact. Sequencers mirroring L1 semantics may adopt same accounting; otherwise, no changes to rollup fee or capacity models.
- Stakers & nodes: Lower variance in execution work per block improves predictability and reduces pathological worst-case loads; efficiency gains from smoother resource usage.
- CL clients: No consensus-layer changes expected; negligible impact beyond observing more consistent block execution times on the execution layer during validation overhead.
- EL clients: Must implement block accounting change and tests; ensure refunds don't reduce block-gas used. Otherwise limited complexity and compatibility concerns overall.
EIP-7843 SLOTNUM Opcode EL ScheduledLet contracts directly read the current slot number cheaply, removing timestamp math and reducing breakage if Ethereum's slot duration changes later.
- Users: Indirectly benefits from more reliable app timing if slot duration changes in future networks.
- App developers: Simplifies reading beacon time onchain, avoiding timestamp math and EIP-4788 proofs; fewer assumptions about the slot schedule.
- Wallets: Little to no impact; wallets typically don't consume slot numbers. Optional UI or simulation support could display it.
- Tooling: Block explorers, RPC simulators, and debuggers may add opcode support and parse the new header slot_number field.
- L2s: Optional support; helpful if mirroring L1 semantics. Not required unless chains want SLOTNUM compatibility and header field parity.
- Stakers & nodes: No operational changes expected; clients handle computation and propagation. Node operators shouldn't need configuration or workflow updates.
- CL clients: Must compute slot_number and include it in headers and engine API payloads; aligns with existing consensus-layer slot calculations.
- EL clients: Implement new opcode, validate header field, expose via RPC, and price gas; updates required across execution clients.
EIP-7928 Block-Level Access Lists EL ScheduledThis introduces access lists at the block level rather than individual transactions, dramatically reducing gas costs for applications that access similar state and enabling new optimization patterns.
- Users: Lower gas costs for complex applications, especially DeFi protocols and applications that access similar state across multiple transactions.
- App developers: Can optimize applications for block-level access patterns, significantly reduce gas costs for state-heavy applications, and enable new design patterns.
- Wallets: Indirect benefits through lower gas costs for applications, but minimal direct impact on wallet development.
- Tooling: Gas estimation tools, transaction simulation, and optimization analysis need updates to handle block-level access list patterns.
- L2s: More efficient state access in Layer 2 settlement transactions and optimized bridge operations.
- Stakers & nodes: More efficient block processing due to optimized state access patterns, reducing computational overhead.
- CL clients: No direct impact on consensus layer operations as this affects execution layer state access optimization.
- EL clients: Significant implementation work required for block-level access list management, state access optimization, and gas accounting updates.
EIP-7954 Increase Maximum Contract Size EL ScheduledRaises limits so developers can deploy larger contracts: up to 64KiB deployed code and 128KiB initcode after a fork. Existing contracts remain valid.
- Users: No required action; may benefit from dapps deploying larger contracts after the network upgrade.
- App developers: Can deploy contracts up to 64KiB and initcode up to 128KiB, reducing pressure to split logic.
- Wallets: No new transaction types; deployments may include larger bytecode. Any size validations should reflect new limits.
- Tooling: Explorers, indexers, verifiers, and RPC tooling should handle larger contract bytecode and initcode in deployment flows.
- L2s: Systems mirroring Ethereum’s limits may need updates to contract-size checks to remain compatible with L1 rules.
- Stakers & nodes: Operators need upgraded clients at fork; larger contracts can slightly increase storage and processing per deployment.
- CL clients: Mostly fork-activation wiring and testing; the rule change is in execution and enforced by paired EL clients.
- EL clients: Update EIP-170/EIP-3860 size checks, fork configuration, and tests to accept 64KiB code and 128KiB initcode.
EIP-7976 Increase Calldata Floor Cost EL ScheduledIncreases the cost for data storage in transactions to help ensure Ethereum runs smoothly.
- Users: Ensures stable transaction speeds as network demands grow.
- App developers: May require adjustments in gas estimation for data-heavy applications.
- Wallets: Need to update gas estimation to reflect increased calldata costs.
- Tooling: Must adapt to account for changes in gas pricing rules.
- L2s: Improves interaction with Ethereum mainnet through efficient gas management.
- Stakers & nodes: Minimal impact on operations, but potential for increased transaction throughput.
- CL clients: May require updates to ensure efficient handling of calldata estimation.
- EL clients: Must be updated to accommodate changes in calldata pricing for optimal performance.
EIP-7981 Increase Access List Cost EL ScheduledAdjusts transaction costs for access lists to balance gas fees and prevent block size inflation.
- Users: Improves transaction fairness by standardizing costs based on data usage.
- App developers: Encourages efficient transaction design due to higher costs for larger access lists.
- Wallets: Could require updates to handle new cost structures in gas estimation.
- Tooling: Need to adapt estimation tools for new access list pricing.
- L2s: Reduces potential for block size inflation leading to enhanced scalability.
- Stakers & nodes: Minimal direct impact, but improved network health benefits all participants.
- CL clients: Adjustments required for gas cost calculations influencing consensus protocols.
- EL clients: Optimizes execution efficiency under new pricing impacting overall gas usage.
EIP-7997 Deterministic Factory Contract EL ScheduledEnables developers to deploy smart contracts at identical addresses across EVM chains.
- Users: Consistent addresses across chains reduce cognitive load and potential for error.
- App developers: Simplifies deployment of apps to multiple chains and development of apps that use cross-chain interop.
- Wallets: Provides a native solution to the problem of deploying multi-chain smart contract accounts.
- Tooling: Tools will be able to replace their default CREATE2 factory with the canonical one, or one deployed from it.
- L2s: Need to adopt the EIP to make the factory widely available and materialize benefits for developers.
- Stakers & nodes: No impact.
- CL clients: No consensus changes expected.
- EL clients: Need to implement a new kind of system contract that is not deployed via transaction but is not a precompile either. Conceptually simple but new in the EL.
EIP-8024 Backward Compatible SWAPN, DUPN, EXCHANGE EL ScheduledAdds new instructions to increase the reachable elements of the stack.
- Users: Cheaper transactions from more efficient bytecode.
- App developers: Once Solidity adopts it, no more workarounds will be necessary for "stack too deep" errors.
- Wallets: No impact.
- Tooling: Must implement support for new instructions.
- L2s: Can adopt new instructions.
- Stakers & nodes: No impact.
- CL clients: No impact.
- EL clients: Must implement new instructions.
EIP-8037 State Creation Gas Cost Increase EL ScheduledProposes to increase gas costs for state creation to mitigate state growth under higher throughput regimes.
- Users: Users may experience higher transaction fees for creating new accounts and contracts, but improved scalability benefits all.
- App developers: Developers should anticipate increased deployment costs, necessitating adjustments to gas estimation tools and budget projections.
- Wallets: Wallet developers need to update gas estimations to reflect new costs; otherwise, minimal code changes are needed.
- Tooling: Tooling and infrastructure must accommodate new pricing models for transaction estimates, with only minor changes to existing tools.
- L2s: L2s adopting this EIP will align with mainnet behaviors, requiring thorough testing and client updates for accurate operations.
- Stakers & nodes: Node operators will need to update their clients for new gas parameters; otherwise, operations and validation remain unchanged.
- CL clients: Minimal changes expected for CL clients; primarily involves standard fork coordination with minimal complexity.
- EL clients: Must integrate new gas costs into transaction handling, requiring updates to gas accounting and ensuring compatibility with existing EIP standards.
EIP-8038 State-Access Gas Cost Update EL ScheduledIncreases gas costs for accessing state data to ensure alignment with current performance.
- Users: Users may experience cost adjustments for transactions related to state access.
- App developers: Developers must account for higher state access costs, potentially leading to adjustments in gas estimations during deployment.
- Wallets: Wallets need to update gas estimation logic to incorporate the new parameters, affecting the transaction success rate.
- Tooling: Tools must adapt to new gas cost models to ensure accurate reporting and analysis of transaction behaviors.
- L2s: L2 implementations need to align with the updated state access costs; anticipate necessary updates to ensure compatibility.
- Stakers & nodes: Node operators must upgrade to new client versions to accommodate updated gas pricing; minimal impact on runtime behavior.
- CL clients: No consensus changes expected for CL; only standard fork coordination. No new serialization or gossip rules necessitated by this proposal.
- EL clients: Adaptations required in gas accounting for state access operations; must ensure compatibility with previous gas models and EIP-2929.
EIP-8045 Exclude Slashed Validators from Proposing CL ScheduledAfter a slashing event, punished validators can still be scheduled to propose blocks, causing missed slots and slow recovery. This change simply skips slashed validators so healthy ones keep proposing and the chain keeps running.
- Users: Users should experience fewer stalled slots and better network responsiveness after large validator slashings, because only non-slashed validators will propose blocks.
- App developers: Application behavior during recovery from mass slashings becomes more predictable, with fewer missed blocks and smoother chain progress. No application changes required.
- Wallets: Wallets get more consistent head updates after slashings, reducing confusing gaps in block production. No direct wallet code changes are expected.
- Tooling: Indexers, explorers, and relays see steadier block flow after slashings, easing incident handling. No protocol-facing changes required for these services.
- L2s: L2 sequencers relying on L1 data and finality benefit from steadier L1 block production after slashings, improving uptime. No L2 code impact.
- Stakers & nodes: Once slashed, a validator immediately loses proposer eligibility. Node operators must account for skipped proposing duties but otherwise run unchanged software.
- CL clients: Consensus clients must update proposer selection logic to prefilter slashed validators using beacon state, integrate with EIP-7917 lookahead, and add tests.
- EL clients: Execution clients are unaffected because block proposer selection lives in the consensus layer; no modifications are required in execution code.
EIP-8061 Increase Exit and Consolidation Churn CL ScheduledRaises limits on how many validators can activate, exit, or consolidate each epoch and separates consolidation churn, improving validator consolidation speed and easing deposit and exit queues while preserving a long weak-subjectivity period and existing security assumptions.
- Users: No direct user-facing changes; effects are limited to validator churn parameters, with only indirect benefits through future finality improvements.
- App developers: Application logic and smart contracts remain unchanged; only underlying consensus churn limits adjust, so most applications require no code modifications.
- Wallets: Wallet protocols stay the same; only beacon-chain churn parameters change, so implementations rarely need updates beyond optional queue displays.
- Tooling: Validator dashboards, explorers, and forecasting tools must update churn constants and formulas to correctly estimate activation, exit, and consolidation queues.
- L2s: Layer 2 protocols see minimal direct impact; beacon-chain validator churn parameters change, but L2 smart contract logic remains unchanged.
- Stakers & nodes: Stakers and node operators gain higher churn throughput, shortening queues and reducing consolidation costs while maintaining a long weak-subjectivity period.
- CL clients: Consensus clients must update configuration constants and churn computation logic, adding a separate consolidation churn quotient and revising queue accounting.
- EL clients: Execution clients require no code changes; all churn computations reside in the consensus layer, leaving execution implementations unaffected.
EIP-8246 Remove SELFDESTRUCT Burn EL ScheduledIn a few rare cases a contract can still permanently destroy the ether it holds, the last remaining way ether can leave circulation through the virtual machine. This change keeps the balance instead, while still wiping the contract's code and storage, and removes a special case that every client, specification, and test suite has to carry.
EIP-8282 Builder Execution Requests CL ScheduledEIP-7732 (ePBS) adds 'builders' as a new staked role. Today builders join and leave through the same contracts validators use. This adds dedicated deposit and exit contracts just for builders, keeping the two apart, simplifying client code, and limiting how many costly signature checks an attacker can force per block.
- Users: No visible change. This only affects how ePBS builders register and exit at the protocol level.
- App developers: No direct impact. The new predeploys are builder-lifecycle infrastructure, not application-facing contracts.
- Wallets: No impact. Builder onboarding is separate from user wallets and validator deposits.
- Tooling: Builder onboarding tooling must target the new deposit and exit predeploys and request types instead of the validator deposit flow.
- L2s: No direct impact.
- Stakers & nodes: Builder operators onboard and exit via new contracts; exits are authorized by the cold execution address, not the hot BLS key.
- CL clients: Moderate: route builder onboarding and exit by request type and drop the validator-path builder branches; most lifecycle logic is reused from EIP-7732.
- EL clients: Low: the deposit and exit predeploys are near line-level copies of audited EIP-7002/7251 contracts; mainly wiring new request types into the request bus.
EIP list: EF: Glamsterdam Hoodi announcement (16 Oct 2026) (checked 12 Nov 2026). Plain-language text and per-audience impact from Forkcast (badge = Forkcast's inclusion status for Glamsterdam), refreshed 4.3 h ago.
If a fork splits the chain: exchange policies
Planned upgrades like this one are not expected to split the chain. This is what exchanges say they do if one ever does.
| Exchange | Planned upgrade | Contentious fork / chain split | Source |
|---|---|---|---|
| Kraken | Supports the upgraded chain; account balances move to it. | Waits; balances follow the dominant chain (most hash power / confirmations). Support for the minority chain is not guaranteed and airdrops are not owed. Withdraw to your own wallet before the fork if you want both coins. | Kraken: General statement on forks, airdrops, migrations (checked 12 Nov 2026) |
| Coinbase | Pauses sends/receives on the network around the upgrade when needed (status page maintenance). | Supports only one version of an asset; any forked token is evaluated case by case (stated before the 2022 Merge). Enabling withdrawal of a fork does not mean it will be listed. | Fortune, 26 Aug 2022: Coinbase will evaluate potential forks (checked 12 Nov 2026) |
| Binance | Publishes a "Binance Will Support the … Network Upgrade & Hard Fork" notice, handles the technical side for users and suspends deposits and withdrawals on that network around the fork. Trading is normally not affected. | No standing public policy found. Decided per event in its announcements. | Binance: Maintenance Updates (announcement catalogue) (checked 12 Nov 2026) |
| eToro | Routine forks go unnoticed by holders; crypto sends may pause for about an hour before and during the fork (e.g. Pectra). | Halts trading if a fork could split the chain, until coins are stable; then evaluates the new coin. Past splits were paid out in fiat (BSV, 2018) rather than in the new coin. | eToro Hard Fork and Airdrop Policy (checked 12 Nov 2026) |
Questions
When is Glamsterdam on mainnet?
No date yet. Hoodi (the last testnet) was postponed on 22 Oct 2026 and must fork cleanly first. Forkcast's planning assumption is shown above, but it is not an announced date.
Do I need to do anything with my ETH?
No. ETH holders and users of exchanges have nothing to do. Ignore anyone offering an "upgrade" or "migration" of your ETH.
What breaks?
Mostly contracts and scripts that hard-code gas numbers. Wallets that assume a plain transfer always costs exactly 21,000 gas should re-test.
Also on the Network Desk for Ethereum
How this works and where the data comes from
Each upgrade page is built from primary sources: client release notes, foundation announcements, governance proposals and Forkcast data for Ethereum. Every curated fact carries its source and the date we checked it. Live data refreshes automatically: exchange flags every 15 minutes, chain heights and governance every 15 minutes, client releases hourly, readiness data every 6 hours.
Countdowns: fixed-time forks use the announced timestamp; Ethereum slots are exact (12 s per slot); height-based forks (Cosmos) are estimated from the average block time of the last 2,000 blocks and will drift. When a target changes we record it as a date slip.
Exchange pauses: we read Binance (deposit/withdraw flags per network), KuCoin (per chain), Kraken (asset funding status) and Coinbase (status page component per network). A pause is any period where deposits or withdrawals are off. Reopen time is measured from the activation time to the first check where both are back on.
Sources: EF: Glamsterdam testnet announcement (Sepolia) (checked 12 Nov 2026); EF: Glamsterdam Hoodi announcement (16 Oct 2026) (checked 12 Nov 2026); EF: Glamsterdam on Hoodi postponed (22 Oct 2026) (checked 12 Nov 2026); EF: EIP-8037/EIP-8038 Glamsterdam (6 Nov 2026) (checked 12 Nov 2026); ethereum/glamsterdam-gas-invariants (checked 12 Nov 2026); Forkcast: Glamsterdam (checked 12 Nov 2026); EIP-7773 (Glamsterdam meta) (checked 12 Nov 2026)
Information only, not financial advice. Data comes from public sources and can be delayed or wrong; check the primary source before acting.