Users, Node Operators and Dapp Developers Need Know

Users and holders

You do not need to do anything to protect your funds entering The Merge. This bears repeating: As a user or holder of ETH or any other digital asset on Ethereum, as well as non-node-operating stakers, you do not need to do anything with your funds or wallet before The Merge.

Despite swapping out proof-of-work, the entire history of Ethereum since genesis remains intact and unaltered after the transition to proof-of-stake. Any funds held in your wallet before The Merge will still be accessible after The Merge. No action is required to upgrade on your part.

As we approach The Merge of Ethereum Mainnet, you should be on high alert for scams trying to take advantage of users during this transition. Do not send your ETH anywhere in an attempt to 'upgrade to ETH2.' There is no 'ETH2' token, and there is nothing more you need to do for your funds to remain safe.

Node operators and dapp developers

Staking node operators and providers

If you are a staker running your own node setup or a node infrastructure provider, there are a few things you need to be aware of to be prepared for The Merge.

1. Run both a consensus layer client and an execution layer client; third-party endpoints to obtain execution data will be unavailable after The Merge.

2. Authenticate both execution layer and consensus layer clients with a shared JWT secret so they can securely communicate.

3. Set a fee recipient address to receive your earned transaction fee tips/MEV.

Not completing the first two items above items will result in your node being seen as 'offline' after The Merge until both layers are synced and authenticated.

Non-validating node operators and infrastructure providers

You probably are already running an execution layer client, such as Geth, Erigon, Besu or Nethermind. Up until The Merge, an execution layer client was enough to receive, properly validate, and propagate blocks being gossiped by the network. After The Merge, the validity of transactions contained within an execution payload will also depend on the validity of the 'consensus block' it is contained within.

As a result, a full Ethereum node after The Merge requires both an execution layer client and a consensus layer client. These two clients work together using a new Engine API. The Engine API requires authentication using a JWT secret, which is provided to both clients allowing secure communication.

1.Install a consensus layer client in addition to an execution layer client

2.Authenticate execution and consensus clients with a shared JWT secret so they can securely communicate with one another.

Dapp 和智能合约开发人员

Dapp and smart contract developers

• block structure
• slot/block timing
• opcode changes
• sources of on-chain randomness
• concept of safe head and finalized blocks

View Tokenview Beacon Explorer