# The Beacon Chain after the Merge: consensus alongside execution 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. Evidence: [The Merge](https://ethereum.org/en/roadmap/merge/); [Ethereum nodes and clients](https://ethereum.org/en/developers/docs/nodes-and-clients/) Canonical: https://degreesofsatoshi.com/encyclopedia/ethereum-beacon-chain/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Role:** The Beacon Chain coordinates proof-of-stake consensus. ([The Merge](https://ethereum.org/en/roadmap/merge/)) - **Merge:** Ethereum’s execution history joined that consensus system. ([The Merge](https://ethereum.org/en/roadmap/merge/)) - **Continuity:** Existing ETH balances and transaction history were preserved. ([The Merge](https://ethereum.org/en/roadmap/merge/)) ## 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. Evidence: [The Merge](https://ethereum.org/en/roadmap/merge/) ## 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. Evidence: [Ethereum nodes and clients](https://ethereum.org/en/developers/docs/nodes-and-clients/); [Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/) ## 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. Evidence: [The Merge](https://ethereum.org/en/roadmap/merge/); [Ethereum security and scam prevention](https://ethereum.org/en/security/) ## Questions ### 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. Evidence: [The Merge](https://ethereum.org/en/roadmap/merge/); [Ethereum staking launchpad FAQ source](https://raw.githubusercontent.com/ethereum/staking-launchpad/dev/src/pages/FAQ/index.jsx) ### 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. Evidence: [The Merge](https://ethereum.org/en/roadmap/merge/) ## Claims and scope ### ethereum-beacon-chain-quick-answer 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: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-beacon-chain-fact-role Role: The Beacon Chain coordinates proof-of-stake consensus. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-beacon-chain-fact-merge Merge: Ethereum’s execution history joined that consensus system. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-beacon-chain-fact-continuity Continuity: Existing ETH balances and transaction history were preserved. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [The Merge](https://ethereum.org/en/roadmap/merge/) — ethereum.org contributors. Consensus transition preserved execution balances and transaction history. Locator: Merging with Mainnet; misconceptions. Retrieved: 2026-10-02T18:55:26.611Z. - [Ethereum nodes and clients](https://ethereum.org/en/developers/docs/nodes-and-clients/) — ethereum.org contributors. Post-Merge client roles, optional validators and synchronization modes. Locator: Execution and consensus clients; synchronization; node types. Retrieved: 2026-10-02T18:55:26.405Z. - [Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/) — ethereum.org contributors. Consensus proposal schedule, voting and finality distinctions. Locator: Slots; epochs; block proposals; attestations; finality. Retrieved: 2026-10-02T18:55:26.560Z. - [Ethereum security and scam prevention](https://ethereum.org/en/security/) — ethereum.org contributors. Primary community guidance on wallet secrets, phishing, malicious sites and transaction checking. Locator: Wallet security; common scams; hardware wallets. Retrieved: 2026-10-02T18:55:24.140Z. - [Ethereum staking launchpad FAQ source](https://raw.githubusercontent.com/ethereum/staking-launchpad/dev/src/pages/FAQ/index.jsx) — Ethereum Foundation. Staking lifecycle, qualifying balances, network duties and deposit-data handling. Locator: Validators; deposits; activation; rewards; key management. Retrieved: 2026-10-02T18:58:48.434Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees 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/