# FAQ for the Ethereum Merge This is not a definitive guide. Please refer to guides by the ethstaker/ethereum cat herders and/or the wider community for step by step information on how to configure your node. This guide is meant as a general overview for what you need to do in various situations. ## General information One of the best resources for up to date information about the merge can be found on the [Ethereum launchpad website](https://launchpad.ethereum.org/en/merge-readiness/). A compilation of all resources relating to the Ethereum Merge can be found [here](https://notes.ethereum.org/Moiv99h9QTmI-imPL8pvQg?view). On a high level, the common changes for anyone running an Ethereum node are: - You would need to run a Consensus Layer(CL/eth2) node as well as a Execution Layer(EL/eth1) node. These two nodes need to connect to each other in order to function properly. - There is a new API port called the engine API. The EL and CL communicate with each other over the engine API port. Therefore, the CL will need to be able to access the EL Engine API port. - The communication over the Engine API port is authenticated with a JWT token. The easiest way is to generate the JWT token independently and pass this value to both the EL/CL nodes. - Since transactions are proposed by validators, they are eligible to receive transaction fee tips (priority fees). These fees are paid by whoever submitted a transaction and come in the form of ETH and are available to be spent immediately on the network. To receive these fees, the fee receipient Ethereum Address needs to be set in the CL. In case there are still questions on how any of these changes would affect you, please do join us at the [Merge Community Calls](https://github.com/ethereum/pm/issues/580). ## What are you interested in? - I am running an EL node (eth1) and want to know how to prepare for the merge: [here](https://notes.ethereum.org/k06rhqPATJ2PhQW5LvgvBA#EL-node-runner-preparation-guide) - I am running an Ethereum validator and want to know how to prepare for the merge: [here](https://notes.ethereum.org/k06rhqPATJ2PhQW5LvgvBA?both#CLeth2-validator-preparation-guide) :::info <center>⚠️⚠️⚠️</center> Irrespective of what scenario you are dealing with, please visit [here](https://notes.ethereum.org/@launchpad/merge-configuration-checklist) for a checklist on if your node is configured properly. <center>⚠️⚠️⚠️</center> ::: ### EL(eth1) node runner preparation guide: If you are running an EL(eth1) node, you will need to add a CL beacon node to your setup. This is required since after the merge, the EL will rely on the CL in order to stay in sync. If you do not run a CL, post merge the EL will stall indefinitely - i.e, All the data you get from the node will be stale and invalid. You cannot connect to a remote CL for this data (Infura, etc), It would be best to run the CL locally. In preparation for the merge, you will need to do the following: - Add the flags required by your EL(eth1) node to enable your Engine API port and JWT token - Setup a CL beacon node. You can choose any of these clients: Teku, Lighthouse, Lodestar, Nimbus or Prysm - Configure the CL beacon node with the Engine API and the same JWT token used on the EL Once setup, it should look as shown in the diagram below. The JSON-RPC queries used to interact with your Ethereum node in the past will remain unchanged! The only extra part is the CL beacon node addition to keep the EL in sync. ![Ethereum Node](https://storage.googleapis.com/ethereum-hackmd/upload_3640e2ab0a01f17630e49fe0aa91a336.png) Please refer to guides from the community (ethstaker/ethereum cat herders/Somer Esat/etc) for more in depth articles on how to do the above steps. :::info CL beaconchain sync times can be quite high, the recommended approach is to use Checkpoint Sync. A guide for Checkpoint Sync can be found [!! Still WIP, Sam will Update it soon!! here](https://notes.ethereum.org/J33FFss4RfytFaAAYLOtAg). ::: :::info After the CL beacon node has been setup, please refer to the [Checklist for Ethereum Merge](https://notes.ethereum.org/@launchpad/merge-configuration-checklist) to confirm that your setup is correctly configured. ::: ### CL(eth2) validator preparation guide: If you are running a CL(eth2) validator, you will need to have an EL running locally. You can no longer use a remote eth1 node (Infura, etc). This requirement is due to the use of the new Engine API which is a trusted endpoint. You would then need to do the following: - Run (Or update) the EL with the required flags. You can choose any of these clients: Nethermind, Besu, Geth or Erigon - Configure the CL beacon node with the Engine API and the same JWT token used on the EL Once setup, it should look as shown in the diagram below. ![Ethereum Validator](https://storage.googleapis.com/ethereum-hackmd/upload_caf60fba95afe589a75f30ba42d18a82.png) :::info After the CL beacon node has been setup, please refer to the [Checklist for Ethereum Merge](https://notes.ethereum.org/@launchpad/merge-configuration-checklist) to confirm that your setup is correctly configured. :::
Last changed by  
 
launchpad
6796

Read more

Withdrawals

In this document I will include all the methods to make full withdrawals with the different clients and also show some examples about how to do a BLS to Execution change with ethdo tool. General assumptions Instead of using a long public key in all the queries, I just refer to it as $validator. export validator="0xb37101f32ee0d54ca6958764d21bd416b397c0a199d5ff447b8cd41bba89d78da9d12622134cc8a3cafe30daad85cd46" We assume for full withdrawal the withdrawal credential of type 0x01. If you have an address that is 0x00, then proceed to the bottom of the doc where it discusses how to convert a BLS (0x00) address into an execution address (0x01) All of our beacon nodes use port 4000 for API communication.

2/5/2024
How to run a node on the Holesky testnet?

Who is this guide for? This guide is meant to be a starting point and provides a mid-level summary of the required steps. It is not intended to be a beginner's guide, so copying and running commands from here may not work without some tweaking. The testnet is meant to mimic a chain that is post-merge. Therefore, the genesis state will be in a merged state. The chain will have to go through a the shapella fork at epoch 256. The JSON-RPC endpoint, faucet, and other tooling URLs can be found on https://holesky.ethpandaops.io/ Which version/branch do I use? Consensus layer

9/28/2023
ETH Withdrawals FAQ

Who is this guide for? If you run Ethereum validators, you can start testing withdrawals and preparing for withdrawals to go live on mainnet. Look out for Goerli and Sepolia, as these will fork before the mainnet. Before that, there will be devnets and mainnet shadowforks. DO NOT ATTEMPT TO CHANGE YOUR BLS KEYS ON MAINNET until the client software is ready to accept your BLS key changes. Each client team will announce once they are ready. We will provide a testnet environment where the BLS change can be tested out without any risk! [toc]

7/26/2023
How to run a node on the Zhejiang testnet?

Who is this guide for? This guide is meant to be a starting point and provides a mid-level summary of the required steps. It is not intended to be a beginner's guide, so copying and running commands from here may not work without some tweaking. The testnet is meant to mimic a chain that is post-merge. Therefore, the genesis state will be in a merged state. The chain will have to go through a fork on both EL and CL at the same time. This fork is called Shanghai on the EL side and Capella on the CL side. These two events will be triggered simultaneously. This is achieved by EL forking at a specific time rather than at a block number, and CL forking at a specific epoch. What is in the Zhejiang testnet? The Zhejiang testnet aims to test the following features:

2/6/2023
Read more from launchpad
Published on HackMD