Glossary · Consensus

The Merge

Published 22 May 2025 · Updated 4 Nov 2026 · 14 min read

The Merge was Ethereum's 15 September 2022 upgrade that joined Mainnet, its original execution layer, with the Beacon Chain, its proof-of-stake consensus layer. Validators replaced miners as block producers. The change preserved Ethereum's accounts, contracts and transaction history rather than creating a replacement network or token.

  • Ethereum's energy use fell about 99.95%, and new ETH issuance fell about 88.7%.
  • The Merge did not lower fees, add capacity or enable withdrawals in September 2022.
  • After the Merge, each Ethereum node runs an execution client and a consensus client.

What the Merge joined

From 1 December 2020, the Ethereum network ran two chains side by side. Mainnet processed transactions using proof of work. The Beacon Chain ran proof of stake separately. In September 2022, Mainnet's blocks began coming from Beacon Chain validators. The definitions below describe that handover from several angles, including consensus rules, communication between clients and application behavior.

SourceDateDefinition, in its own wordsWhat it adds
ethereum.org, "The Merge"DateUpdated 15 May 2026Definition, in its own words"The Merge was the joining of the original execution layer of Ethereum (the Mainnet that has existed since genesis) with its new proof-of-stake consensus layer, the Beacon Chain."What it addsExecuted on 15 September 2022. Energy use about 99.95% lower
EIP-3675, "Upgrade consensus to Proof-of-Stake"DateCreated July 2021, live at ParisDefinition, in its own words"This EIP deprecates Proof-of-Work (PoW) and supersedes it with the new Proof-of-Stake consensus mechanism (PoS) driven by the beacon chain."What it addsThe terminal block rule, fixed block fields, no block or ommer rewards
Ethereum Foundation, mainnet announcementDate24 August 2022Definition, in its own words"Once the execution layer reaches or exceeds the TTD, the subsequent block will be produced by a Beacon Chain validator."What it addsTriggered by total difficulty, not by a block number
Engine API README, ethereum/execution-apisDateRead 4 November 2026Definition, in its own words"This interface allows the communication between consensus and execution layers of the two-component post-Merge Ethereum Client."What it addsWhy every node now runs two clients
EIP-4399, "Supplant DIFFICULTY opcode with PREVRANDAO"DateCreated October 2021, live at ParisDefinition, in its own words"The return value of the DIFFICULTY (0x44) instruction after this change is the output of the randomness beacon provided by the beacon chain."What it addsThe opcode that contracts read for randomness
Ethereum Foundation, "How The Merge Impacts Ethereum's Application Layer"Date29 November 2021Definition, in its own words"The Merge is designed to have minimal impact on how Ethereum operates for end users, smart contracts and dapps."What it addsExact 12-second slots, the safe and finalized block tags

Block production and fork choice moved from proof of work to proof of stake. Ethereum kept its accounts, balances, contracts and transaction history on the same chain. The names changed too. Ethereum's former "Eth1" component is now called the execution layer, while "Eth2" became the consensus layer. The ethereum.org documentation says "Eth2" is deprecated. Older names, including Serenity and Ethereum 2.0, belong to an earlier naming scheme, not a second Ethereum network.

The Merge removed energy-intensive mining and reduced new ETH creation. It was not a new chain or a replacement Ether token, and holders needed no action. The ethereum.org page says the Merge "set the stage for further scalability upgrades not possible under proof-of-work". The September 2022 CCRI report, commissioned by ConsenSys, estimates a 99.988% electricity reduction, from about 22,900,320 to about 2,600.86 MWh annually. The ethereum.org Merge page gives a more conservative figure of about 99.95%. The report estimates a 99.992% reduction in Ethereum's annual carbon footprint.

How the September 2022 switch happened

Bellatrix and Paris implemented one hard fork in two steps. The first prepared Ethereum's consensus rules. The second ended proof of work when accumulated mining difficulty crossed a preset threshold, rather than at a scheduled block number.

Bellatrix changed Ethereum's consensus layer at epoch 144,896 on 6 September 2022. Paris followed under EIP-3675 at terminal total difficulty (TTD) 58,750,000,000,000,000,000,000, with timing dependent on hash rate. The announcement expected Paris between 10 and 20 September 2022. Chain data shows the terminal block, 15,537,393, at 06:42:42 UTC on 15 September 2022, with one transaction. The first proof-of-stake block, 15,537,394, arrived in slot 4,700,013 at 06:42:59 UTC, 17 seconds later. The Ethereum Foundation described completion about two epochs later, when that block was finalized.

Ethereum rehearsed on Ropsten in June 2022, Sepolia in July 2022 and Goerli in August 2022. Gray Glacier delayed the difficulty bomb on 30 June 2022 through EIP-5133. Five consensus clients and four execution clients shipped releases for the Merge, giving operators paired client software to update. Nodes that did not update followed the old proof-of-work chain. Some miners continued proof of work through EthereumPoW, a separate network rather than Ethereum Mainnet.

How blocks changed after the Merge

Before the Merge, a block appeared whenever a miner found a valid nonce. Since then, a block is due every 12 seconds from one chosen validator. The figure steps through both, and through the two ways a proposer gets a block today.

Figure 1 · Page team model of the consensus specs, the Engine API and the Builder APIFollow one block, step by stepChoose an era and building path, then follow six steps across three lanes showing participants, client calls and slot timing.
Era
Build path

Build paths apply to proof of stake. Before the Merge, the mining pool's node chose the transactions.

1 of 6
Mining pool nodeMinersOther nodes
1. Hand out workNew headThe pool's node builds a block template from its mempool on top of the heaviest chain and sends the work to its miners.
Call or message
eth_getWork
Between
Mining pool node to Miners
2. Race for a nonceRandom waitMiners hash the header until one finds a nonce that meets the difficulty target. In the last 50 blocks the wait was 1 to 59 seconds.
Call or message
Ethash
Between
Miners
3. Return the solutionWhen foundThe winning miner sends the nonce back. The pool's node seals the block, and the block reward goes to the pool's address.
Call or message
eth_submitWork
Between
Miners to Mining pool node
4. Broadcast the blockAt onceThe pool's node announces the block to its peers over the eth protocol of devp2p.
Call or message
NewBlock, eth protocol
Between
Mining pool node to Other nodes
5. Check work and transactionsOn arrivalEach node checks the proof of work, executes every transaction and compares the resulting state root with the header.
Call or message
Check Ethash, execute
Between
Other nodes
6. Follow the heaviest chainEach new blockWhen two valid blocks compete, nodes follow the chain with more total difficulty. A losing block can come back as an ommer.
Call or message
Most total difficulty
Between
Other nodes
Consensus clientExecution clientOther nodes
1. Ask for a payloadBefore 0 sThe proposer's consensus client, chosen for this slot, sends the head with payload attributes: timestamp, prevRandao and fee recipient.
Call or message
engine_forkchoiceUpdatedV1
Between
Consensus client to Execution client
2. Hand over the payload0 sThe execution client fills a payload from its mempool. The consensus client fetches it and wraps it in a beacon block.
Call or message
engine_getPayloadV1
Between
Execution client to Consensus client
3. Sign and gossip0 sThe proposer signs the block and gossips it on the consensus layer's network. The eth protocol no longer carries new blocks.
Call or message
beacon_block gossip
Between
Consensus client to Other nodes
4. Execute the payloadOn arrivalEach consensus client checks the beacon block and passes the payload to its execution client, which runs it and answers VALID or INVALID.
Call or message
engine_newPayloadV1
Between
Other nodes
5. Vote for the headBy about 4 sA committee of validators assigned to the slot attests to the block it sees as head and to the current checkpoints.
Call or message
Attestations
Between
Other nodes
6. Aggregate and update the headBy about 8 sAggregators combine the votes, and each consensus client tells its execution client the new head. About two epochs later the block is finalized.
Call or message
engine_forkchoiceUpdatedV1
Between
Other nodes
Proposer's nodeRelay and buildersOther nodes
1. Register with relaysAhead of the slotThrough mev-boost, the validator signs its fee recipient and gas limit preferences and registers them with the relays it chose.
Call or message
registerValidator
Between
Proposer's node to Relay and builders
2. Builders competeSlot beforeBuilders assemble candidate blocks and send them with bids to relays, which check them. None of this is part of the protocol.
Call or message
Blocks and bids
Between
Relay and builders
3. Ask for the best bid0 sThe proposer's node asks for a payload header and its bid value. It can still build a local block instead.
Call or message
getHeader
Between
Proposer's node to Relay and builders
4. Sign the blinded blockRight afterThe proposer signs a block that holds only the header. The signature binds it, since a second block would risk slashing.
Call or message
submitBlindedBlock
Between
Proposer's node to Relay and builders
5. Reveal the payloadRight afterThe relay answers with the full payload, so the proposer's node can assemble the complete block.
Call or message
Payload returned
Between
Relay and builders to Proposer's node
6. Publish and attestBy about 4 sThe proposer gossips the full block. Other nodes execute it with engine_newPayloadV1, and the slot's committee attests.
Call or message
beacon_block, engine_newPayloadV1
Between
Proposer's node to Other nodes
Consensus clientExecution clientOther nodes
1. Ask for a payloadBefore 0 sThe proposer's consensus client sends the head with payload attributes, which now also carry withdrawals and the parent beacon block root.
Call or message
engine_forkchoiceUpdatedV3
Between
Consensus client to Execution client
2. Hand over payload and blobs0 sThe execution client returns the payload, its blob bundle with cell proofs, and execution requests such as deposits and exits.
Call or message
engine_getPayloadV5
Between
Execution client to Consensus client
3. Sign and gossip0 sThe proposer gossips the block and the blob data as columns. Under PeerDAS each node keeps only some columns and samples others.
Call or message
beacon_block, data_column_sidecar
Between
Consensus client to Other nodes
4. Execute the payloadOn arrivalThe consensus client passes the payload, the expected blob hashes and the execution requests to its execution client, which runs it.
Call or message
engine_newPayloadV4
Between
Other nodes
5. Vote for the headBy about 4 sA committee of validators assigned to the slot attests to the block it sees as head and to the current checkpoints.
Call or message
Attestations
Between
Other nodes
6. Aggregate and update the headBy about 8 sAggregators combine the votes and each node updates its head. At 14:24 UTC on 4 November 2026 the finalized checkpoint was 79 slots back.
Call or message
engine_forkchoiceUpdatedV3
Between
Other nodes
Proposer's nodeRelay and buildersOther nodes
1. Register with relaysAhead of the slotThrough mev-boost, the validator signs its fee recipient and gas limit preferences and registers them with the relays it chose.
Call or message
registerValidator
Between
Proposer's node to Relay and builders
2. Builders competeSlot beforeBuilders assemble candidate blocks and send them with bids to relays, which check them. None of this is part of the protocol.
Call or message
Blocks and bids
Between
Relay and builders
3. Ask for the best bid0 sThe proposer's node asks for a payload header with its bid value and blob commitments. It can still build a local block instead.
Call or message
getHeader
Between
Proposer's node to Relay and builders
4. Sign the blinded blockRight afterThe proposer signs a block that holds only the header. The signature binds it, since a second block would risk slashing.
Call or message
submitBlindedBlockV2
Between
Proposer's node to Relay and builders
5. Relay publishes the blockRight afterSince Fulu the builder side publishes the full block and its blob data itself, so the payload does not return to the proposer.
Call or message
202 Accepted
Between
Relay and builders to Other nodes
6. Execute and attestBy about 4 sOther nodes execute the payload with engine_newPayloadV4, sample blob columns, and the slot's committee attests.
Call or message
engine_newPayloadV4, attestations
Between
Other nodes
Time between blocks13.35 s average1 to 59 s in the last 50 proof-of-work blocks
Who picks transactionsThe pool's nodeMiners only hash the header
When it is finalProbabilisticEach new block on top makes a reversal less likely
Time between blocks12 s per slotNo missed slot in the first 50 after the Merge
Who picks transactionsThe proposer's execution clientFrom its own mempool
When it is finalAbout 12.8 minAfter two epochs of 32 slots (Casper FFG)
Time between blocks12 s per slotNo missed slot in the first 50 after the Merge
Who picks transactionsAn external builderDelivered through a relay, outside the protocol
When it is finalAbout 12.8 minAfter two epochs of 32 slots (Casper FFG)
Time between blocks12 s per slot0.71% of slots empty since the Merge
Who picks transactionsThe proposer's execution clientWith blobs, up to 21 per block
When it is final79 slots behind the headAbout 15.8 min at 14:24 UTC, 4 November 2026
Time between blocks12 s per slot0.71% of slots empty since the Merge
Who picks transactionsAn external builderThree largest built 83.3% of relay-delivered blocks (relayscan, 24 h to 09:07 UTC)
When it is final79 slots behind the headAbout 15.8 min at 14:24 UTC, 4 November 2026

A pool node builds while miners race with Ethash. Blocks arrive after random waits, and two valid blocks can compete.

Every 12-second slot, the consensus client requests an execution payload through engine_forkchoiceUpdatedV1 and engine_getPayloadV1. Attesters vote by about four seconds.

In November 2026, engine_forkchoiceUpdatedV3, engine_getPayloadV5 and engine_newPayloadV4 support the flow with blobs. A relay can publish for the proposer.

This page team model uses consensus specs, the Engine API and the Builder API, with specification deadlines rather than measured delays.

Under proof of work, a pool prepared blocks and miners raced with Ethash. Nodes followed the chain with the most total difficulty, with ommer rewards and probabilistic finality. The last 50 mining blocks averaged 13.35 seconds, ranging from 1 to 59 seconds (chain data read on 4 November 2026). Under proof of stake, an Ethereum validator proposes per 12-second slot, chosen at random, weighted by effective balance. Attestations are due around four seconds, aggregates around eight. Gasper combines LMD-GHOST with Casper FFG, normally reaching finality after two 32-slot epochs.

Consensus clients ask their execution clients for payloads over the authenticated Engine API, on port 8551 by default. Blocks now travel on consensus-layer gossip, since EIP-3675 deprecated block gossip on the eth protocol. Many proposers take blocks from external builders through mev-boost and relays, a temporary path with higher trust assumptions, per the Builder API spec. A validator can still build locally. Three builders delivered 83.3% of relay blocks in the 24 hours to 09:07 UTC on 4 November 2026 (relayscan.io). Glamsterdam plans to enshrine proposer-builder separation.

What changed and what stayed

The table compares twelve properties before the Merge, right after it in September 2022 and on 4 November 2026. Read each row from left to right to see which change came with the Merge and which came with a later upgrade.

TopicBefore the MergeAfter the Merge, September 20224 November 2026
Who produces blocksBefore the MergeMiners, mostly through poolsAfter the Merge, September 2022One validator per 12-second slot, chosen at random by effective balance4 November 2026The same, 812,979 active validators. Many blocks come from external builders through relays
Sybil resistanceBefore the MergeEthash workAfter the Merge, September 202232 ETH per validator4 November 202632 to 2,048 ETH of effective balance per validator since Pectra (EIP-7251)
Time between blocksBefore the Merge13.35 s on average, 1 to 59 s (last 50 blocks)After the Merge, September 202212 s per slot, no missed slot in the first 504 November 202612 s per slot, 0.71% of slots empty since the Merge
FinalityBefore the MergeProbabilistic, each new block makes a reversal less likelyAfter the Merge, September 2022Two epochs, 12.8 minutes by the spec4 November 2026The same. The finalized checkpoint was 79 slots behind the head
New ETH per dayBefore the MergeAbout 14,700: 13,000 to miners, 1,700 to stakersAfter the Merge, September 2022About 1,700 to stakers, with 14 million ETH staked4 November 2026Up to about 3,030 with 44.23 million ETH staked (page team calculation)
Fee burnBefore the MergeBase fees burned since London, August 2021After the Merge, September 2022Unchanged4 November 2026Unchanged. Base fee 0.0877 gwei in the head block
ElectricityBefore the MergeAbout 22.9 TWh a year (CCRI)After the Merge, September 2022About 2,601 MWh a year (CCRI)4 November 2026About 5,750 MWh a year in CCRI's October 2023 study
Gas limit per blockBefore the Merge30 millionAfter the Merge, September 202230 million4 November 202660 million, the default in Fusaka client releases (EIP-7935)
WithdrawalsBefore the MergeBeacon Chain stake locked since December 2020After the Merge, September 2022None. Staked ETH and rewards stayed locked4 November 2026Since April 2023 (Shapella). Exit queue 1 day 18 hours
Data for rollupsBefore the MergeCalldataAfter the Merge, September 2022Calldata4 November 2026Blobs since March 2024, up to 21 per block since January 2026
Node softwareBefore the MergeOne execution clientAfter the Merge, September 2022An execution client and a consensus client, joined by the Engine API4 November 2026The same pair, Engine API methods up to V5
Randomness opcodeBefore the MergeDIFFICULTY returns the proof-of-work difficultyAfter the Merge, September 2022PREVRANDAO returns the beacon chain's randomness4 November 2026The same. block.prevrandao in Solidity since 0.8.18

The Merge changed block producers, finality and new ETH creation, not Ethereum's capacity or fee rules. Later changes explain the table's larger gas limit and rollup data support. Dencun introduced blobs in March 2024. Their maximum reached 21 per block on 7 January 2026. Fusaka client releases set the default gas limit to 60 million, which blocks reached in November 2025. Neither feature belongs to the Merge itself. After Paris, difficulty is zero, the nonce is 0x0000000000000000 and the ommers list is empty.

ETH issuance, burn and supply

Rewards and destroyed fees push Ethereum's supply in opposite directions. The Merge changed the reward side. Adjust the model's inputs to separate protocol rules from sample activity, not to forecast supply. The proof-of-work comparison shows about 13,000 ETH in daily mining rewards before September 2022.

Figure 2 · Page team model of the reward formula and EIP-1559Compare new ETH with burned feesAdjust stake, base fee and gas use, or choose a dated preset, to compare daily rewards, destroyed fees and annual supply changes.
Preset
44.23 million ETH
0.0877 gwei
28.2 million gas
ETH per daySupply growsMining rewards, 202213,000 a dayStaking issuance3,028 a dayBase fee burn18 a day
New ETH per day3,028 ETHA maximum, with every validator on time
ETH burned per day18 ETHBase fee × gas used × 7,149 blocks
Net change in supply+3,010 ETH a day+0.90% of supply a year

Burn stays below issuance at these settings, so modeled ETH supply increases while the selected conditions hold.

Burn falls within about 10% of issuance, resembling the 2022 balance near 16 gwei with 14 million ETH staked.

Burn exceeds issuance at these settings, so modeled ETH supply shrinks for as long as fees remain that high.

This page team model applies the consensus reward formula with perfect participation, 7,149 blocks daily and no blob fees.

The ethereum.org supply page, updated 14 October 2026, records pre-Merge rewards near 13,000 ETH daily for miners and 1,700 for Beacon Chain stakers. Removing mining rewards cut total issuance about 88.7%, with about 14 million ETH staked in September 2022. In the page team model, annual issuance equals approximately 166.3 times the square root of staked ETH. At approximately 44.23 million ETH staked on 4 November 2026, that gives a maximum near 3,030 ETH daily. Missed duties and penalties reduce rewards.

EIP-1559 introduced the base fee burn in August 2021, unchanged by the Merge. In 2022, ethereum.org put the break-even near an average gas price of 16 gwei. Repeating the 4 November 2026 head block's gas use and 0.0877 gwei base fee gives about 18 ETH destroyed daily. This page team estimate multiplies base fee, gas used and daily blocks, excluding blob fees. Etherscan reports 122,189,140 ETH in supply on 4 November 2026, versus about 120.52 million in September 2022. That is about 1.4% more in a little over four years.

What changed for each Ethereum role

The handover affected readers differently depending on whether they held ETH, wrote software or helped run Ethereum. Select a role to compare responsibilities before, during and after September 2022. Ethereum staking brings duties that simply holding ETH does not. Ethereum had 812,979 active validators at 14:24 UTC on 4 November 2026.

Figure 3 · Specs, Ethereum Foundation posts and readings of 4 November 2026Find your role's changesPick a role to compare three dated eras, with status tags and sources showing which responsibilities changed, continued or ended.
Role
Before the MergeBeforeBlocks came about every 13 seconds on average, at random gaps. DIFFICULTY (0x44) returned the proof-of-work difficulty, and ommers were part of the chain.EF blog, 29 November 2021. Chain data
At the Merge, September 2022ChangedSlots are exactly 12 seconds. DIFFICULTY became PREVRANDAO, the beacon chain's randomness, which a proposer can bias by one bit. JSON-RPC added the safe and finalized tags.EIP-4399, EIP-3675, execution-apis
4 November 2026NewSolidity has block.prevrandao since 0.8.18. Rollups post data in blobs, up to 21 per block. EIP-7702 lets accounts set code. One transaction may use up to 16,777,216 gas.Solidity changelog, consensus-specs, EIP-7702, EIP-7825
Before the MergeBeforeOne execution client, such as go-ethereum, Nethermind, Besu or Erigon, checked proof of work and executed transactions. Blocks spread over the eth protocol.EIP-3675
At the Merge, September 2022ChangedEvery node runs an execution client and a consensus client. They talk over the Engine API on port 8551 with a shared JWT secret. Nodes that did not upgrade followed the old chain.EF announcement, 24 August 2022. Engine API spec
4 November 2026ChangedThe same pair of clients, with newer Engine API versions such as engine_newPayloadV4 and engine_getPayloadV5. Since Fusaka a node keeps only part of the blob data and samples columns to check availability.execution-apis, EIP-7594
Before the MergeBeforeValidators had staked 32 ETH each on the Beacon Chain since December 2020 and voted on beacon blocks, while Mainnet blocks still came from miners.ethereum.org
At the Merge, September 2022ChangedValidators propose and attest for Mainnet blocks, set a fee recipient for priority fees and MEV, and run an execution client. Staked ETH and rewards stayed locked.EF announcement, 24 August 2022
4 November 2026NewWithdrawals since April 2023. Since Pectra one validator can hold up to 2,048 ETH (EIP-7251). The entry queue was 18 days 15 hours and the exit queue 1 day 18 hours.EIP-4895, EIP-7251, validatorqueue.com, 4 November 2026
Before the MergeBeforeETH sat in accounts on the execution layer. Base fees were burned from August 2021, and miners received new ETH with every block.ethereum.org
At the Merge, September 2022SameNo action was needed. Balances, contracts and history carried over, and the Ethereum Foundation told holders to be on the lookout for scams.EF announcement, 24 August 2022
4 November 2026SameThe same ETH. Etherscan showed a supply of 122,189,140 ETH on 4 November 2026, against about 120.52 million in September 2022.Etherscan, ethereum.org
Before the MergeBeforeEthash mining paid 2 ETH per block plus ommer rewards, about 13,000 ETH a day across all miners.ethereum.org
At the Merge, September 2022EndedMining stopped at the terminal block. Block and ommer rewards were removed, and nodes ignore proof-of-work blocks built on top of it. EthereumPoW went on as a separate network.EIP-3675, EF announcement. Cointelegraph, 4 October 2022
4 November 2026EndedEthereum has no mining. A validator chosen at random proposes the block in each 12-second slot.ethereum.org, consensus-specs

Review timing and randomness assumptions. Ethereum applications gained safe and finalized block tags without replacing existing contracts.

Run paired execution and consensus clients. Operating a self-verifying Ethereum node does not require a 32 ETH deposit.

Validators took over proposals and set a fee recipient for priority fees and MEV. Withdrawals arrived later, in April 2023.

Keep existing ETH and accounts. The Merge required no token conversion, despite scams claiming holders needed to update their ETH.

Ethereum Mainnet mining ended in September 2022. EthereumPoW continued separately, without becoming the same network as Ethereum.

Each card names its sources. Queue times and supply are readings of 4 November 2026.

Holders had no migration task, while developers inherited small but real interface changes. EIP-4399 replaced DIFFICULTY with PREVRANDAO, stored as prevRandao in the header. Solidity 0.8.18 introduced block.prevrandao on 1 February 2023. Exact 12-second slots and safe or finalized queries changed timing assumptions. Node operators added a second client, and validators took over block production before withdrawals became available. Ethereum mining ended on Mainnet, and EthereumPoW continued separately.

Ethereum upgrades around and after the Merge

Ethereum's transition began before September 2022 and continued through later paired forks. After the Merge, each major upgrade combines execution and consensus changes under one name. The timeline separates preparation, completed mainnet changes and testnet progress checked on 4 November 2026.

  1. December 2020

    The Beacon Chain starts

    A separate proof-of-stake chain launched on 1 December 2020. It ran alongside Ethereum Mainnet, preparing the consensus system that later took over block production. It did not yet produce Mainnet's transaction blocks.

  2. June 2022

    Testnets merge and the bomb waits

    Ropsten became the first long-standing public testnet to merge. Gray Glacier followed on 30 June 2022 at block 15,050,000, delaying the difficulty bomb through EIP-5133 while Ethereum prepared for the mainnet handover.

  3. September 2022

    Bellatrix and Paris complete the Merge

    Bellatrix prepared consensus on 6 September 2022. Paris completed the handover on 15 September 2022, replacing Ethereum's proof-of-work block production through the Merge. The consensus layer then ran fork choice as well as block proposals.

  4. April 2023

    Shapella enables staked ETH withdrawals

    Shanghai and Capella activated together on 12 April 2023. Capella added partial withdrawals of rewards above the balance cap and full withdrawals after an exit, and EIP-4895 carried them to the execution layer. Validator exits remain rate limited for security.

  5. March 2024

    Dencun introduces data blobs

    Cancun and Deneb activated on 13 March 2024. EIP-4844 added blobs for rollup data, separating this scaling change from Ethereum's earlier switch in consensus. This introduced proto-danksharding, not a network of shard chains.

  6. May 2025

    Pectra expands account capabilities

    Prague and Electra activated on 7 May 2025. EIP-7251 raised the maximum effective validator balance to 2,048 ETH. EIP-7002 enabled execution-triggered exits, and EIP-7702 let externally owned accounts set code. Activation still requires 32 ETH.

  7. December 2025

    Fusaka adds data sampling

    Fulu and Osaka activated on 3 December 2025. PeerDAS introduced partial blob storage and sampling, and transactions were capped at 16,777,216 gas. Fusaka releases had already made 60 million gas the default limit. Blob-only forks increased blob limits afterward.

  8. October 2026

    Glamsterdam reaches a testnet

    Sepolia activated Amsterdam and Gloas on 6 October 2026. Hoodi's 26 October 2026 date was postponed on 22 October 2026. Neither a new Hoodi date nor a mainnet date was set when this page was checked on 4 November 2026.

What the Merge did not deliver

The Merge changed how Ethereum agrees on blocks, not everything people expected from it. The six limits below separate what the protocol guarantees from what depends on demand, validator participation or services outside the protocol.

Lower transaction fees

The Merge did not reduce gas fees. Ethereum's base fee responds to demand for block space, so consensus alone does not determine transaction cost.

Extra network capacity

Blocks became about 10% more frequent without a capacity expansion at the Merge. The ethereum.org roadmap says shard chains are no longer part of its plans.

Immediate withdrawals and exits

Staked ETH stayed locked until Shapella in April 2023. Exits are rate-limited at 256 ETH per epoch, and validatorqueue.com showed 39,817 ETH waiting to exit, about 1 day 18 hours, on 4 November 2026.

Decentralized block building

Relayscan.io's 24-hour reading to 09:07 UTC on 4 November 2026 assigns three builders 83.3% of relay-delivered blocks. Relays add trust outside Ethereum's protocol, while EIP-7732 remains planned.

Unbiased application randomness

PREVRANDAO is biasable by one bit per proposer, who can withhold a block. EIP-4399 advises applications to use future randomness with a lookahead.

Uninterrupted checkpoint finality

Ethereum blocks kept arriving during finality interruptions on 11 and 12 May 2023, which lasted 4 and 9 epochs, about 25 and 58 minutes. Checkpoint progress depends on validator participation.

Building Ethereum software after the Merge

Ethereum applications depend on more than contract execution. We check how software interprets chain progress, connects to nodes and responds to changing protocol rules. PixelPlex was founded in 2007 and has built blockchain software since 2013. Our Ethereum development services cover consulting, applications, contracts and infrastructure, including testing of nodes, business logic and permissions.

PixelPlex case icon

Our KickICO platform case documents an Ethereum crowdfunding and ICO platform launched in 2017, before the Merge. We built its ICO and KICK token contracts, an ICO contract generator and a server API connecting blockchain operations with the interface.

  1. Randomness and timing

    We review contracts for block-time assumptions and PREVRANDAO use, including whether decisions depend on a value that a validator can influence.
  2. Deposit confirmation rules

    We check whether deposit crediting waits for safe or finalized blocks, with explicit security assumptions rather than a fixed delay treated as certainty.
  3. Paired client setup

    We check execution and consensus client connectivity, the shared Engine API secret and fee recipient settings where software interacts with proposing nodes.
  4. Fork readiness checks

    We review Pectra's EIP-7702 account behavior and Fusaka's per-transaction gas cap against application logic, node configuration and existing test cases.
  5. Public testnet coverage

    We test node interactions, business logic, contracts and permissions on public testnets before mainnet, separating application behavior from network configuration assumptions.

Discuss your Ethereum application's technical requirements

We can review your contract assumptions, node connections or fork readiness and help define the engineering work involved.

Discuss Ethereum development

The Merge FAQ

What was the Ethereum Merge in simple terms?

The Merge was the Ethereum upgrade of 15 September 2022 that moved block production from miners to Beacon Chain validators using proof of stake. Accounts, balances, contracts and history stayed on the same chain. Execution clients still execute transactions, and holders had nothing to do.

When did the Merge happen on Ethereum?

The Merge happened on 15 September 2022, when block 15,537,394 became Ethereum's first proof-of-stake block at 06:42:59 UTC. Bellatrix activated on 6 September 2022. Paris used terminal total difficulty rather than a block number as its trigger. The terminal block, 15,537,393, arrived at 06:42:42 UTC on 15 September 2022.

Did the Merge make Ethereum cheaper or faster?

The Merge did not lower gas fees or add capacity, because it changed how blocks are produced, not how much fits in them. Blocks come about 10% more often, with 12-second slots against a proof-of-work target of about 13.3 seconds. Blobs came later with Dencun in March 2024. Fusaka client releases made 60 million gas the default, and blocks reached it in November 2025.

What happened to Ethereum miners after the Merge?

Ethereum mining ended at the Merge, because proof-of-work blocks stopped being valid on Ethereum after the terminal block. Block and ommer rewards were removed. Before the September 2022 switch, they totaled about 13,000 ETH a day. Some miners continued on EthereumPoW, a separate network.

How did the Merge change ETH supply?

The Merge cut new ETH issuance by about 88.7% by ending mining rewards of about 13,000 ETH a day. Stakers kept receiving about 1,700 a day. EIP-1559's base fee burn continued unchanged. Issuance grows with the amount staked. Etherscan showed 122,189,140 ETH on 4 November 2026 against about 120.52 million in September 2022, about 1.4% more.

Is the Merge the same as Ethereum 2.0?

No. Eth2 and Ethereum 2.0 are older names that ethereum.org has deprecated, while the Merge is the specific upgrade of September 2022. "Eth1" is now the execution layer and "Eth2" the consensus layer. The Merge created no new token or network.

Which clients does Ethereum need after the Merge?

After the Merge, every Ethereum node runs an execution client and a consensus client, connected by the Engine API. The Engine API uses an authenticated port, 8551 by default, with a shared JWT secret. The ethereum.org documentation says running an Ethereum node does not require 32 ETH.
Sources (35)

Get updates about blockchain, technologies and our company

We will process the personal data you provide in accordance with our Privacy policy. You can unsubscribe or change your preferences at any time by clicking the link in any email.

Follow us on social networks and don't miss the latest tech news

  • facebook
  • X
  • linkedin
  • instagram
Stay tuned and add value to your feed