--
Ethereum is moving to proof-of-stake approximately in mid-September. This event, known as “The Merge”, is a major change to how the system works and node operators need to be ready before then to ensure a smooth upgrade. This post goes over everything node operators need to know in a a checklist format. All these points and more are covered in our comprehensive docs regarding how to prepare for the merge, found here.
- Node operators will need to run execution clients in addition to consensus clients after the Ethereum “Merge”. Our documentation has been updated with instructions that walk you through the details of this in both testnet and mainnet environments. Prepare for The Merge is for current node operators, while our Quickstart has been updated for newcomers.
- If you are connecting your beacon node to your execution node over HTTP, the HTTP connection will need to be authenticated after The Merge. Prysm’s Quickstart and Prepare for The Merge documents have been updated with HTTP authentication instructions.
- Validators will need to specify a Fee Recipient address in order to collect transaction fees after The Merge. This is a typical Ethereum wallet address that will be receiving all transaction fees from your block proposals as a validator. Prysm’s Fee Recipient guidelines go over how to configure this feature.
- If you need a refresher on nodes, validators, networks, and how they all relate, refer to our new Nodes and Networks conceptual guidance.
- Review Prysm’s Security Best Practices if you’re running a validator — this guidance will help you stake responsibly.
- Use Prysm v3.0.0
Prysm v3 is a Merge-ready release that includes updates, deprecations, and breaking changes. Review the release notes to understand how this release impacts your configuration. Stay updated on any hot-fix releases or patch releases that can come out from now and mid-September by following our Discord’s announcements channel or our mailing list. You can also see our guide on upgrading and staying up-to-date here.
- Unset USE_PRYSM_VERSION
If you’ve ever set the USE_PRYSM_VERSION environment variable to use a release candidate, either clear it via UNSET USE_PRYSM_VERSION (Linux/MacOS) or set USE_PRYSM_VERSION= (Windows).
- Verify your Prysm version
Verify that you’re running Prysm v3.0.0 by issuing the following command: prysm.sh beacon-chain --version (Linux) prysm.bat beacon-chain --version (Windows) and the same for the validator command.
- Review “Before and now”
The Before and now section gives you a high-level overview of the items that you need to keep in mind while preparing for The Merge. See the Ethereum.org Merge announcement and Merge readiness checklist for more detailed information.
- Review system requirements
Review the post-Merge system requirements section to ensure that your configuration will support The Merge. Note that a 2TB+ SSD is highly recommended.
- Use a Merge-ready version of your execution client
Follow the release pages and any announcement channels of your execution client of choice, such as go-ethereum, nethermind, besu, or others.
If you’re running a validator, configuring a fee recipient address will allow you to earn what were previously miners’ transaction fee tips. Instructions are provided here: Configure a Fee Recipient address.
- Connect to your Execution Client on Port 8551
Previously, you would only need to connect to your execution client client such as go-ethereum on port 8545. However, the merge introduces an additional default port, 8551, which is used for critical communications between Prysm and its execution client. This is known as the authrpc.port in go-ethereum, but will have other names in your execution client. Connecting to your execution client on port 8551 via HTTP will require authentication.
- Set up HTTP authentication using a JWT token
If you’re not using IPC to connect your beacon node and execution node, ensure that both your execution node and beacon node are configured to use JWT authentication. These instructions are included here: Configure JWT
- Update your firewall
If you’re not using IPC to connect your beacon node and execution node, your beacon node will need to connect to its execution node on port 8551. Previously, port 8545 was used. Ensure that your firewall rules are updated accordingly, and refer to Configure ports and firewalls for improved network connectivity for general connectivity improvement tips.
See Check node and validator status to learn how to check the status of your execution node, beacon node, and validator node.
Refer to our Quickstart and Prepare for The Merge guidance for instructions, and don’t hesitate to reach out on Discord for support.
