What you need to set up an Ethereum node
To set up an Ethereum node after The Merge, you must run two separate software clients simultaneously: an execution client and a consensus client. This dual-client architecture is mandatory because the execution client handles transactions and smart contract execution, while the consensus client manages the Proof-of-Stake protocol, and they communicate through an authenticated Engine API connection. Before you begin, ensure your hardware meets the essential requirements: a Solid State Drive (SSD) is non-negotiable due to the constant random reads and writes the blockchain requires, with a 4-8 TB NVMe SSD recommended for a full node since the Ethereum blockchain surpassed 3 TB by mid-2025. You'll also need at least 4 GB of RAM (more is better), a multi-core processor, and a Linux or macOS operating system, plus basic command-line familiarity to interact with the client software.
Choose your execution and consensus clients
Your first decision is selecting which execution client and which consensus client to run, and you have several solid options for each. For the execution layer, Geth (Go Ethereum) is the most popular and battle-tested choice, but Nethermind and Besu are excellent alternatives that offer strong performance and are written in C# and Java respectively, Erigon and Reth are also gaining traction for their optimized storage efficiency. On the consensus side, Lighthouse is a widely used Rust-based client known for its performance and reliability, while Prysm offers a user-friendly experience with extensive documentation, and Teku (Java-based) is another robust option, Nimbus, Lodestar, and Grandine round out the field.
Step 1: Install an execution client
Once you've chosen your execution client, the installation process is straightforward, we'll use Geth as the primary example since it's the most widely deployed. Begin by visiting the official Geth download page and grabbing the appropriate binary for your operating system, or if you're on Linux, you can add the Ethereum repository and install via your package manager with `sudo apt-get install geth` for Ubuntu/Debian systems. After installation completes, verify everything is working by opening your terminal and running `geth version`, you should see version information displayed, confirming the installation was successful. Before starting Geth for the first time, you'll want to set up a dedicated data directory where the blockchain will be stored, and you can do this by creating a folder like `~/ethereum-node` and running `geth --datadir ~/ethereum-node init` to initialize the client with the appropriate settings.
Step 2: Install a consensus client
With your execution client installed, the next step is to install your chosen consensus client, we'll use Lighthouse as our primary example, which you can download from the official Lighthouse GitHub releases page or install via package managers like `sudo apt-get install lighthouse` on Ubuntu. Once downloaded, extract the archive and move the binary to a location in your PATH, such as `/usr/local/bin/`, then verify the installation by running `lighthouse --version` in your terminal. The consensus client will also need to know which network to join (mainnet or a testnet like Goerli or Sepolia) and where to store its own data, which you can specify with the `--datadir` flag.
Step 3: Configure the Engine API and network ports
Connecting your two clients requires configuring the authenticated Engine API, which is the secure communication channel that lets your execution client and consensus client talk to each other, this is essential because the consensus client needs to instruct the execution client on which blocks to process and the execution client needs to report back on execution results. Beyond the Engine API, you must ensure your network configuration allows peer-to-peer communication: the default port for Ethereum node discovery and block propagation is TCP and UDP port 30303, so you'll need to open this port in your firewall and set up port forwarding on your router if you're behind NAT, this is how other nodes find and connect to yours, which is critical for participating in the network.
Step 4: Sync your node with the Ethereum network
With both clients installed and configured, it's time to start them and begin the synchronization process, first launch your execution client with `geth --datadir ~/ethereum-node --syncmode snap` to use the default 'snap sync' mode, which downloads only the most recent state and historical data, significantly reducing both storage requirements and sync time compared to full sync. Then, in a separate terminal, start your consensus client with the appropriate flags, and you'll see both clients begin communicating through the Engine API and discovering peers on the network. The initial synchronization can take anywhere from several hours to a few days depending on your internet connection speed, hardware specifications, and the age of the blockchain, you can monitor progress by checking the logs for block numbers and using commands like `geth attach` to query the current sync status or `lighthouse beacon_node --http` to access the consensus client's metrics. During this time, your node is downloading and verifying the entire history of the Ethereum network, which requires patience but is essential for your node to function as a fully participating member of the network.
Step 5: Monitor and maintain your node
Once your node is synced and operational, you'll want to establish a monitoring routine to ensure it stays healthy and continues running smoothly, start by checking your peer count with `geth attach` and running `admin.peers.length` to verify you're connected to the network, and use `eth.syncing` to confirm you're fully synchronized. Monitor your system resources using tools like `htop` for CPU and memory usage, `df -h` to track SSD disk space (which will grow as the blockchain expands), and `nethogs` to see network bandwidth consumption, these metrics help you identify potential issues before they become problems. Finally, keep both your execution and consensus clients updated by regularly checking for new releases and subscribing to their respective GitHub release feeds, as running outdated software can cause your node to fall out of sync with the network or miss important protocol upgrades, a quick `sudo apt-get update && sudo apt-get upgrade geth lighthouse` or equivalent command for your package manager will typically handle the update process, and remember to restart both clients after updating to apply the changes.
