# Next Ethereum Upgrade: Glamsterdam Status and Fork History

> The next Ethereum upgrade explained: Glamsterdam's ePBS and block-level access lists, its testnet status and what Fusaka, Pectra and Dencun changed on chain.

Markdown copy of https://voltfincrypto.com/apps/next-ethereum-upgrade

**Question:** What is the next Ethereum upgrade, what does it change and what did past forks change on chain?

- Kind: Report in Voltfin Folio
- Topic: [Ethereum](https://voltfincrypto.com/topics/ethereum)
- Chains: Ethereum
- Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is.

Ethereum changes through scheduled network upgrades, each a bundle of EIPs that every client activates at the same epoch. The upgrade being prepared after Fusaka is Glamsterdam, whose headline changes are enshrined proposer-builder separation (EIP-7732) and block-level access lists (EIP-7928). This report says what it changes, where it stands in testing and what is still undecided, dated to each edition.

It also keeps a record of past forks measured on chain rather than described: the block each one activated at and the parameters it changed, such as the gas limit and blob capacity. It shows how quickly new transaction types were used after each fork, so an upgrade's effect can be checked from blocks, not only from announcements.

## Blueprint

### The next upgrade at a glance

Which upgrade is next, its headline EIPs, its testnet and mainnet schedule as published and what is still open.

Cites: EIPs scheduled for inclusion; Public testnets forked so far.

### What Glamsterdam changes

Enshrined proposer-builder separation, block-level access lists and the other EIPs in scope, each in plain words with what it means for users, stakers and builders.

### Where testing stands

Devnets, public testnets and client releases for the upgrade, with the date each step happened or is planned.

Cites: Client releases with the fork scheduled; Testnet fork dates.

### Past forks, measured on chain

Each fork since the Merge with its activation block and the parameters it changed, read from blocks before and after.

Cites: Activation block per fork; Gas limit before and after each fork; Blob target and maximum per fork.

### How fast new features were used

How quickly blob transactions after Dencun and set-code transactions after Pectra were adopted, from daily counts.

Cites: Type-3 transactions per day after Dencun; Type-4 transactions per day after Pectra.

### What to watch next

Open decisions, scheduled calls and the measurements this report will take once the upgrade activates.

## How it will be measured

- Upgrade status comes from public sources and is recorded with each one: EIP meta specs, client release notes, testnet announcements and the core developer call notes.
- Activation blocks of past forks are taken from client chain configurations and confirmed on chain by the first block carrying the fork's new header fields or transaction types.
- Parameters are read from block headers and client configurations before and after each activation: the gas limit, blob gas per block and the blob base fee.
- Adoption of new transaction types counts type-3 transactions after Dencun and type-4 transactions after Pectra, day by day from activation.
- Each edition is dated: status claims cite their source and date, and on-chain figures are pinned to blocks before publication.

## Data it needs

- `chain_activity_daily` (to build): Transactions, active sending addresses, new addresses, contracts created and gas used on each chain per day, counted from blocks and transactions.
- `gas_blocks` (to build): Base fee, priority fee percentiles, gas used and gas limit for each block on fee-market chains, for a near-live gas tracker.
- `blob_usage_daily` (to build): EIP-4844 blobs posted per day, blob gas used, blob base fee, and the rollup that posted them.
- `account_abstraction_daily` (to build): ERC-4337 UserOperations, bundlers and paymasters, and EIP-7702 delegations per chain per day.
- `mev_daily` (to build): Blocks by builder, MEV-Boost relay share, and detected sandwich attacks with the value taken from users, per day.
- Source: Fork activation epochs and timestamps from client chain configurations and EIP meta specs, recorded with their source
- Source: EIP lists per fork from the Ethereum EIPs repository and the core developer call notes
- Source: First block after each fork: gas_limit, blob_gas_used and excess_blob_gas
- Source: Daily counts of type-3 and type-4 transactions after their activation

## Questions

### What is the next Ethereum upgrade?

Glamsterdam is the upgrade being prepared after Fusaka. Its two headline changes are enshrined proposer-builder separation (EIP-7732), which moves the builder auction into the protocol, and block-level access lists (EIP-7928), which record what each block reads and writes so clients can process it in parallel. Each edition gives its current status and dates.

### When is the Glamsterdam mainnet date?

A mainnet date is set only after an upgrade has run on public testnets and client teams agree on an epoch. Until then any date is a target, not a schedule. This report shows the published target, the testnets already forked and the date of the source behind each.

### What is ePBS?

Enshrined proposer-builder separation makes the split between the validator who proposes a block and the builder who assembles it part of the protocol. Until then the split runs through MEV-Boost relays outside the protocol; under EIP-7732 the proposer commits to a builder's bid and the builder reveals the payload afterwards.

### What did Fusaka change?

Fusaka introduced PeerDAS, which lets nodes check blob data by sampling pieces of it, and a way to raise blob capacity in small blob-parameter forks. It also capped the gas a single transaction may use, raised the default gas limit and tied the blob base fee floor to execution gas costs.

### What did Pectra change?

Pectra let ordinary accounts delegate to contract code with EIP-7702, raised the maximum effective balance of a validator so stake can be consolidated (EIP-7251), passed deposits to the beacon chain straight from execution blocks (EIP-6110), let withdrawal credentials trigger exits (EIP-7002) and raised the blob target.

### How are past forks measured on chain?

Each fork's activation block is confirmed by the first block that carries its new fields or transaction types. The report then compares parameters such as the gas limit and blob usage before and after, and counts how quickly new transaction types were used.

## Glossary

- **Hard fork**: A coordinated change to the protocol rules that all clients activate at the same block or epoch; nodes that do not upgrade split off.
- **Glamsterdam**: The combined name of the Amsterdam execution-layer upgrade and the Gloas consensus-layer upgrade, prepared as one fork.
- **ePBS**: Enshrined proposer-builder separation, EIP-7732: the protocol itself runs the exchange between a block's proposer and its builder.
- **Block-level access list**: A list carried with each block of the accounts and storage slots it touches and their new values, so clients can verify and execute in parallel (EIP-7928).
- **Blob-parameter-only fork**: A small upgrade that changes only blob capacity settings, introduced with Fusaka so capacity can grow between major forks.

## Related apps

- [Fusaka Upgrade Impact: Blobs, L2 Fees and Spam](https://voltfincrypto.com/apps/fusaka-upgrade-impact)
- [Ethereum Block Builders: Market Share of Blocks](https://voltfincrypto.com/apps/ethereum-block-builders)
- [Ethereum Gas Limit Tracker: Block Gas Limit Over Time](https://voltfincrypto.com/apps/ethereum-gas-limit)
- [EIP-7702 Adoption: Delegated EOAs and Top Contracts](https://voltfincrypto.com/apps/eip-7702-adoption)
- [Ethereum Blob Fees and Blobs per Block vs Target](https://voltfincrypto.com/apps/ethereum-blob-fees)
- [Ethereum Gas Tracker](https://voltfincrypto.com/apps/ethereum-gas-tracker)

Build it in Voltfin Studio: https://app.voltfincrypto.com/signup?next=%2F