Encyclopedia Ethereum · Entry 269
The Beacon Chain after the Merge: consensus alongside execution
In this article
At a glance
Key facts
Consensus was introduced alongside the existing chain
Before the Merge, the Beacon Chain ran alongside Ethereum’s existing execution system. The Merge changed how Ethereum agreed on blocks by connecting execution to proof-of-stake consensus.
That history explains why tools still use terms such as beacon node or beacon block. They describe the consensus system, not a separate application currency.
One transaction has execution and consensus context
Suppose a user sends ETH. Execution determines whether the signed transaction is valid and how balances change. Consensus determines how its containing block fits into the accepted chain and eventual finality.
An execution receipt and a validator’s consensus vote answer different questions about the same overall Ethereum network. Reading one does not replace every check provided by the other.
No new ETH conversion was required
The Merge preserved account balances and historical execution data. Ordinary holders did not need to exchange ETH for a newly issued “ETH2” token as part of that protocol transition.
A page claiming that an old balance must be migrated by sharing secrets or making a special conversion deserves careful scrutiny. Use the network’s documented history to distinguish an actual protocol change from a misleading offer.
Direct answers
Questions people ask
Is the Beacon Chain still a separate place to hold ordinary wallet ETH?
It is the consensus side of the integrated Ethereum system. Ordinary wallet balances are execution state; validator balances have their own consensus accounting.
Did the Merge erase Ethereum’s previous transactions?
No. The existing execution history and balances were carried forward when proof-of-stake consensus took over.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
The Beacon Chain introduced Ethereum’s proof-of-stake consensus and became the consensus side of Ethereum at the Merge. Today execution clients process transactions while consensus clients coordinate the accepted chain and validator duties. It is not a second wallet balance that users must migrate to, and the Merge did not require converting ordinary ETH to a new user token.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimRole: The Beacon Chain coordinates proof-of-stake consensus.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimMerge: Ethereum’s execution history joined that consensus system.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimContinuity: Existing ETH balances and transaction history were preserved.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimRevision history
- — First publication after primary-source research and separate automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- The Mergeethereum.org contributors
Consensus transition preserved execution balances and transaction history.
Locator: Merging with Mainnet; misconceptions · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:26.611ZOpen source - Ethereum nodes and clientsethereum.org contributors
Post-Merge client roles, optional validators and synchronization modes.
Locator: Execution and consensus clients; synchronization; node types · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:26.405ZOpen source - Ethereum proof of stakeethereum.org contributors
Consensus proposal schedule, voting and finality distinctions.
Locator: Slots; epochs; block proposals; attestations; finality · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:26.560ZOpen source - Ethereum security and scam preventionethereum.org contributors
Primary community guidance on wallet secrets, phishing, malicious sites and transaction checking.
Locator: Wallet security; common scams; hardware wallets · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:24.140ZOpen source - Ethereum staking launchpad FAQ sourceEthereum Foundation
Staking lifecycle, qualifying balances, network duties and deposit-data handling.
Locator: Validators; deposits; activation; rewards; key management · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:58:48.434ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “The Beacon Chain after the Merge: consensus alongside execution.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-beacon-chain/