Ethereum's Glamsterdam Upgrade: Will It Make Ethereum Faster and Cheaper?
Glamsterdam combines Gloas, the consensus-layer upgrade, with Amsterdam, the execution-layer upgrade, redesigning how Ethereum builds, shares and verifies blocks.
Glamsterdam is scheduled to activate on the Sepolia testnet on 6 October 2026 at 13:53:36 UTC. Hoodi and Ethereum mainnet dates have not yet been decided. Sepolia is a test milestone, not a mainnet launch date.
The upgrade is intended to remove bottlenecks, prepare Ethereum for higher capacity, price long-term storage more accurately and replace the flat transaction base with resource-based gas components. It does not guarantee that every transaction or smart-contract interaction becomes cheaper.
Quick answer
Glamsterdam changes capacity and cost accounting, but not every fee overnight
Glamsterdam changes Ethereum's block pipeline and gas accounting. The immediate effect depends on the transaction, while the larger scaling gains depend on how clients use the new architecture.
- Sepolia is first, not mainnet. The scheduled 6 October activation is a public testnet event. Hoodi and mainnet dates are still to be determined.
- “Cheaper” depends on the transaction. Some minimal transaction shapes use less execution gas, a normal ETH transfer remains at 21,000, and state creation or access can cost more.
- The largest changes are structural. Enshrined proposer-builder separation and block-level access lists create the foundation for higher throughput, safer propagation and future parallel processing. They are not a universal speed switch.
What Glamsterdam is and when it happens
Ethereum's consensus layer coordinates validators and agreement on the chain; its execution layer processes transactions and smart-contract state. Glamsterdam upgrades both. The official Glamsterdam meta EIP lists ePBS, block-level access lists, resource-based transaction gas and other networking and developer changes.
Only Sepolia has an activation date:
| Network | Current status | Activation timing |
|---|---|---|
| Sepolia | Scheduled public testnet activation | 6 October 2026, 13:53:36 UTC |
| Hoodi | Testing milestone still to be decided | No confirmed date |
| Ethereum mainnet | Not yet scheduled | No confirmed date |
The Ethereum Foundation's testnet announcement gives the Sepolia activation as epoch 353,024 and slot 11,296,768. It explicitly leaves Hoodi and mainnet as “TBD.” Any date presented elsewhere should be checked against the official deployment schedule before it is treated as confirmed.
Testnets exist to expose problems before mainnet. A smooth Sepolia activation would be useful evidence, but client compatibility, block propagation, builder behavior and application effects would still need evaluation.
Why Ethereum is changing its block pipeline
Ethereum's capacity is not determined by one number. Nodes must receive data, execute transactions, verify results, update state and stay synchronized. Adding more work without changing that pipeline can increase the hardware and bandwidth burden.
Glamsterdam addresses three connected constraints:
- A compressed block-production path. Builders and proposers currently coordinate partly through systems outside the core protocol. The final payload must move through a narrow timing window.
- Sequential discovery of transaction dependencies. A node often learns which accounts and storage slots a transaction touches by executing it. Unknown dependencies limit safe parallel work.
- Gas prices that do not always match resource costs. Some operations create permanent database growth or require expensive lookups without being charged proportionally.
Rather than promise one throughput target, Glamsterdam changes the structure beneath future capacity increases: more propagation time, better information before execution and more accurate resource pricing.
The main mechanisms
ePBS
Block-production separation
Moves the builder-to-proposer exchange and payment logic into the protocol and gives execution payloads a longer propagation window.
BALs
Dependency maps
List the state touched by a block, helping nodes fetch data efficiently and laying groundwork for parallel processing and executionless state updates.
Gas accounting
Resource-aware pricing
Raises or separates costs for state creation and access so capacity can grow without allowing database demands to grow without restraint.
Transaction gas
Resource-based components
Replaces the flat base with charges for the work a transaction actually performs. Some minimal shapes cost less, an ordinary ETH value transfer remains at 21,000 execution gas, and new-account creation adds state gas.
How ePBS separates proposing from building
Ethereum validators propose blocks, while specialized builders often assemble transaction payloads. Today, their hand-off commonly uses third-party relays and middleware.
EIP-7732 brings that relationship into Ethereum's consensus rules. The proposer includes a builder commitment, the builder later reveals the payload and the protocol handles payment. A committee records whether the payload and related blob data arrived on time.
The change also separates consensus validation from execution-payload validation. According to the official Glamsterdam roadmap page, this expands the execution payload's propagation window from about two seconds to roughly nine seconds.
The longer window should help larger payloads and blob data reach independent nodes. Users may not see faster confirmations, because demand, fees and application behaviour still determine when a transaction is included.
For validators, staking pools and builder infrastructure, ePBS is a material operational change. Those operators need compatible clients and must understand the new duties and interfaces.
How block-level access lists prepare for parallel processing
Ethereum cannot safely parallelize unknown work. If nodes do not know which accounts and storage slots transactions affect, they must first discover possible conflicts through execution.
EIP-7928 introduces block-level access lists. A BAL records the accounts and storage locations accessed by the transactions in a block, together with the resulting post-execution values. The block header commits to that list with a hash.
With that map, a node can identify independent data requests earlier and perform parallel disk reads. Post-execution values can also support state updates without replaying every transaction. Companion networking changes help nodes exchange these lists.
BALs do not make Ethereum parallel overnight. They give clients the information needed to parallelize more work, and the speed-up will vary by client and workload.
Will Glamsterdam make Ethereum fees cheaper?
Glamsterdam can reduce one kind of transaction cost while deliberately increasing others.
The flat 21,000-gas base is being decomposed
EIP-2780 replaces the flat intrinsic cost with named components tied to the resources a transaction uses. Its current reference cases are more nuanced than the high-level “cheaper transfers” description:
- A self-transfer uses 12,000 execution gas.
- A zero-value transaction to a different existing externally owned account uses 15,000 execution gas.
- A normal ETH value transfer to a different existing externally owned account remains at 21,000 execution gas.
- A transfer that creates a new account uses 21,000 execution gas plus 183,600 state gas under the current EIP parameters.
Ethereum.org's overview still says a standard ETH payment could become “up to 71% cheaper,” but the current normative EIP does not reduce the 21,000 execution-gas reference case for an ordinary value transfer. This article follows the specification as of 2 October 2026. The EIP remains under review, so the parameters must be rechecked before publication and mainnet activation.
Gas units are not the same as the final amount paid. The final fee also depends on the fee per gas, priority fee, calldata, execution, state creation and congestion.
State-heavy operations can become more expensive
EIP-8037 reprices the creation of new state, such as accounts, storage slots and deployed bytecode. It also separates some state costs into a dedicated accounting reservoir. EIP-8038 raises costs for reading or updating state where current prices no longer reflect the work performed by modern nodes.
This is intentional: every node may have to store and serve new state for years. More accurate charges are meant to support sustainable capacity increases and reduce denial-of-service exposure.
The Ethereum Foundation's developer impact report says historical replay flagged a small set of contracts; most flagged issues could be addressed with a gas-limit increase, while the large majority were unaffected. Developers still need to test their own contracts.
| Activity | Possible effect after Glamsterdam | Why it is not guaranteed |
|---|---|---|
| Self-transfer or zero-value transaction to an existing account | Lower execution-gas reference case | These are not the same as an ordinary ETH payment |
| Sending ETH to an existing account | Ordinary value transfer remains at 21,000 execution gas | Final cost still depends on fee conditions and transaction details |
| Sending ETH to a new account | Adds a substantial state-gas charge under the current specification | Parameters remain under review, and creating permanent state has a cost |
| Interacting with a state-heavy contract | Some operations may cost more | The result depends on the opcodes and state touched |
| Using a well-optimized application | May benefit from future capacity and client improvements | Application design and congestion remain important |
| Using a layer 2 | May benefit indirectly from better payload and blob scaling | L2 fees also depend on the rollup's own design and demand |
Fees will change by transaction type. Under the current specification, self-transfers and zero-value transfers get cheaper, an ordinary ETH payment stays at 21,000 execution gas, and creating new state costs more.
What users, stakers and developers may need to do
For ordinary holders: there is no new ETH token to claim or convert into. Wallet balances need no swap. Anyone asking for ETH at an “upgrade address” is attempting a scam.
Most holders need to do nothing. Validators, node operators and developers do need to prepare:
Participant checklist
ETH holders and application users
- Do not convert, wrap or transfer ETH merely because an upgrade is approaching.
- Expect fee estimates to vary by transaction type; a lower reference case for one transaction shape does not apply to every action.
- Treat an unconfirmed mainnet date as unconfirmed, even when a social-media post presents it as settled.
Participant checklist
Validators and node operators
- Update both execution and consensus clients to releases explicitly marked as compatible with the relevant network activation.
- Review ePBS duties, payload-timeliness behavior and any changes published by the client team.
- Monitor official announcements for the Hoodi and mainnet schedules.
Participant checklist
Smart-contract and infrastructure developers
- Replay or test state-heavy transactions under the new gas schedule.
- Check hard-coded gas assumptions and integrations that parse ETH movements or receipts.
- Test against supported Glamsterdam environments before mainnet.
- Recheck the final EIP set and client releases; implementation details can still change before mainnet.
Glamsterdam also schedules EIP-7708, which makes non-zero ETH transfers emit a standard log. The current EIP explicitly excludes the base-fee burn because it can already be derived from the block header. Transfer logs may simplify tracking for wallets, exchanges and bridges, but those systems still need to adapt and validate their accounting.
Could Glamsterdam affect the ETH price?
A smooth upgrade would strengthen Ethereum's technical case. Delays or compatibility problems could hurt confidence. Neither outcome predicts ETH's next move, because liquidity, leverage, macro conditions and broader demand may matter more.
Keep the milestones separate:
- A proposal is selected.
The market learns what developers intend to build.
- A testnet activates.
The code is exercised in a public testing environment.
- Mainnet activates.
The production network adopts the change after a date is agreed and clients are ready.
Each event can change expectations, but none guarantees the next. Sepolia provides technical evidence, not proof of a future ETH return.
What this means for TurboStrategy readers
Protocol upgrades are useful context for understanding Ethereum market narratives. They do not replace risk limits, exchange checks or a defined trading process. A technically strong upgrade can still coincide with a falling ETH market, and a delay can occur during a broader rally.
This article is educational and does not announce an Ethereum trading product or a launch date. Product availability should be verified only through TurboStrategy's official product pages and the entitlements shown inside a customer's account. No protocol change guarantees trading performance, uninterrupted exchange access or successful order execution.
What to watch between Sepolia and mainnet
Between Sepolia and mainnet, watch what actually happens:
- Did Sepolia activate at the scheduled time?
Look for finalization, broad client participation and any unexpected chain splits.
- How did ePBS behave under public-testnet conditions?
Watch payload delivery, timeliness votes, builder payments and the behavior of staking infrastructure.
- Did block-level access lists remain available and consistent?
Client teams need reliable production, exchange and consumption of BAL data.
- What did application testing reveal?
Pay particular attention to contracts with hard-coded gas assumptions or heavy state access.
- Which client releases are marked ready?
Compatibility should come from official client teams, not an unverified download link.
- When is Hoodi scheduled?
A later testnet stage can provide additional evidence before mainnet.
- Has a mainnet date actually been agreed?
Check the Ethereum Foundation announcement and the activation table in the meta EIP.
- Did the final scope change?
Review EIP-7773 again close to activation. Do not rely on an older article, including this one.
Glamsterdam changes what Ethereum can scale safely
Glamsterdam gives Ethereum more room to scale by changing block production, exposing transaction dependencies earlier and charging more accurately for the resources transactions use.
The immediate effects will vary. Some transactions get cheaper, state-heavy operations may cost more, and larger performance gains depend on client implementation. Sepolia is the first test; Hoodi and mainnet still have no dates.
Frequently asked questions
What is the Ethereum Glamsterdam upgrade?
Glamsterdam is a coordinated Ethereum network upgrade combining changes to the Gloas consensus layer and Amsterdam execution layer. Its headline features include enshrined proposer-builder separation, block-level access lists and revised gas accounting.
When will Glamsterdam launch?
It is scheduled to activate on the Sepolia testnet on 6 October 2026 at 13:53:36 UTC. As of 2 October 2026, Hoodi and Ethereum mainnet activation dates have not been decided.
Is the 6 October date the Ethereum mainnet launch?
No. It is the Sepolia testnet activation. A mainnet date requires a separate decision and official announcement.
Will all Ethereum transactions become cheaper?
No. Under the current EIP-2780 reference cases, a self-transfer uses 12,000 execution gas and a zero-value transaction to a different existing externally owned account uses 15,000, but an ordinary ETH value transfer remains at 21,000. A transfer that creates a new account adds state gas, and some state-heavy operations are being repriced upward. The final amount paid also depends on network fee conditions and transaction details.
Will Glamsterdam make Ethereum process transactions in parallel?
Block-level access lists expose dependencies and enable parallel data reads, creating important groundwork for parallel processing. Actual parallel execution and its performance depend on client implementations and workloads, so it should not be treated as an instant universal multiplier.
Do ETH holders need to swap or upgrade their coins?
No. Existing ETH does not need to be converted. Instructions to send ETH to an upgrade or migration address should be treated as a scam.
What must validators do?
Validators and non-staking node operators must update both their execution and consensus clients to compatible releases before an activation on the network they operate. They should follow official client and Ethereum Foundation announcements.
Does Glamsterdam guarantee that ETH will rise?
No. Protocol development can affect expectations, but ETH price is influenced by many market and economic factors. Testnet or mainnet success does not guarantee appreciation.
Is TurboStrategy launching Ethereum support with Glamsterdam?
This article makes no product announcement. Readers should rely on TurboStrategy's official product pages and their account entitlements for current availability.
Official sources
- Ethereum.org: Glamsterdam roadmap
- Ethereum Foundation: Glamsterdam testnet announcement
- EIP-7773: Glamsterdam hard-fork meta specification
- EIP-7732: Enshrined proposer-builder separation
- EIP-7928: Block-level access lists
- EIP-2780: Resource-based intrinsic transaction gas
- Ethereum Foundation: Glamsterdam repricing impact for smart-contract developers
- EIP-8037: State creation gas cost increase
- EIP-8038: State-access gas cost update
- EIP-7708: ETH transfers emit a log