The Complete Guide to Setting Up an Ethereum Node and Mining

How to set up a stable and secure Ethereum node and earn money from it?

Subject Setting up an Ethereum node, validator management and mining options are still of great importance to developers, infrastructure operators, traders and DeFi enthusiasts. After The Merge, the mining model on the mainnet was discontinued, but the launch of nodes execution and consensus/validator, staking rewards, and services like MEV-Boost continue. This article takes a practical, server-centric approach, from hardware selection to client installation, security and monitoring, and monetization tips.

Types of nodes in the Ethereum ecosystem and the state of mining

There are several types of nodes in the Ethereum ecosystem, each with different roles and hardware requirements:

• Execution client: Responsible for running the EVM and maintaining state and blocks. Popular: Geth (go-ethereum), Erigon, Nethermind, Besu.
• Consensus client / Beacon: Responsible for PoS consensus, proposing/confirming blocks. Popular: Lighthouse, Prysm, Teku, Nimbus.
• Validator node: Validator requires a consensus client and validator key; with 32 ETH, a full validator can be run or pools can be used.
• Archive (Archive node): Store all state and history; very space-consuming and essential for analytical queries or API provisioning.
• Mining (PoW): Stopped on the mainnet but used for forks (like ETHW) and other cryptocurrencies GPU mining.

Suitable server requirements for Ethereum node and validator

To select a server, first determine the application: validator, full node (full/fast sync), archive node, or GPU mining. Below is a suggested configuration based on the application.

Recommended configuration for the production validator

• CPU: 2 vCPUs or more for multiple concurrent validators.
• RAM: 8–16GB.
• Storage: NVMe 500 GB (for fast/full sync), high-speed SSD. Less space required if you use Erigon.
• Network: At least 100 Mbps unlimited and stable ping.
• Availability: High uptime, port 30303/UDP/TCP open for peers.
• Protection: Anti-DDoS service and snapshot backup.

Config for full node/archive

• Full node: NVMe 1 TB, 16 GB RAM, CPU 4+ cores.
• Archive node: NVMe 3+ TB (requirements increase as chain grows), 32+ GB RAM, 8+ cores.

Config for GPU mining (for PoW chains or other coins)

• GPU: NVIDIA RTX 30/40 series with 8+ GB VRAM (depending on algorithm).
• A dedicated GPU mining motherboard or server; proper power supply and cooling are required.
• Cloud GPU servers suitable for rendering/AI can also be used for temporary mining, but check the cost and policies.

Installation and Setup — Practical Examples (Execution + Consensus + Validator)

Below is an example of installing Geth (execution client) with systemd and a docker-compose example for geth + lighthouse + mev-boost.

Simple Geth installation with systemd (Ubuntu)

Commands to install Geth with PPA:

sudo add-apt-repository -y ppa:ethereum/ethereum
sudo apt update
sudo apt install -y geth

Example systemd unit for geth:

/etc/systemd/system/geth.service
[Unit]
Description=Geth Ethereum node
After=network.target

[Service]
User=geth
Group=geth
Type=simple
ExecStart=/usr/bin/geth --http --http.addr 0.0.0.0 --http.vhosts="*" --syncmode=snap --http.api eth,net,web3,debug,personal --cache=2048
Restart=on-failure
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target

After creating the unit:

sudo systemctl daemon-reload
sudo systemctl enable --now geth
journalctl -u geth -f

docker-compose example for geth + lighthouse + mev-boost

docker-compose example (update versions as needed):

version: "3.7"
services:
  geth:
    image: ethereum/client-go:stable
    volumes:
      - ./geth-data:/root/.ethereum
    ports:
      - "30303:30303"
      - "8545:8545"
    command: ["--http", "--http.addr", "0.0.0.0", "--syncmode", "snap", "--http.api", "eth,net,web3"]
    restart: unless-stopped

  lighthouse-beacon:
    image: sigp/lighthouse:latest
    command: ["beacon", "--http", "--metrics"]
    volumes:
      - ./lighthouse-data:/var/lib/lighthouse
    ports:
      - "5052:5052"
    depends_on:
      - geth
    restart: unless-stopped

  lighthouse-validator:
    image: sigp/lighthouse:latest
    command: ["vc", "--validators-dir", "/validator_keys", "--beacon-node", "http://lighthouse-beacon:5052"]
    volumes:
      - ./validator_keys:/validator_keys
    depends_on:
      - lighthouse-beacon
    restart: unless-stopped

  mev-boost:
    image: flashbots/mev-boost:latest
    environment:
      - ETH2_REST_URL=http://lighthouse-beacon:5052
    ports:
      - "18550:18550"
    restart: unless-stopped

Note: Keep validator keys in a local folder and restrict access. For better security, use a remote signer or HSM / cloud KMS.

Operational security and key protection

• Key protection: Never put an unencrypted mnemonic or keystore file on the server. Use hardware signers (YubiHSM, Nitro Enclaves or cloud-based HSM) or remote-signers.
• Secure backup: An encrypted version of the keystore and mnemonic should be kept in an offline location.
• Firewall (UFW) Example:

sudo ufw allow ssh
sudo ufw allow 30303/tcp
sudo ufw allow 30303/udp
sudo ufw allow 5052/tcp
sudo ufw enable

SSH Update and Protection: Disable root login, use SSH keys, and 2FA.

DDoS and Network: Use anti-DDoS servers, BGP failover, and multiple locations to improve availability.

Monitoring logs: logrotate, fail2ban and alerting to detect disconnections or attacks.

Monitoring and Maintenance (Prometheus/Grafana)

Key monitoring tips:

• Install node_exporter and collect metrics from lighthouse/geth on the metrics port.
• Grafana dashboard to display latency, block height, peer count, CPU, I/O, and disk usage.
• Define alerts for block discrepancies with the network, peer reduction, fork, sync lag, and validator status (slashing/downtime).

Earning money: Staking, MEV and (in case of PoW) mining

Staking (solo validator): With 32 ETH you can start a validator. Income includes base reward and a portion of MEV. Risks: slashing, penalties for downtime and server costs.

Group/Pool Sticking: Lower capital requirements, but fees and liquidity are different.

MEV-Boost: Using relays and builders to increase rewards; setting up mev-boost can increase validator income.

PoW mining: For PoW chains or forks, mining is dependent on hashrate, electricity and hardware costs; it is usually more profitable than pools.

Revenue estimate It depends on variable factors including the number of validators, network reward rate, staking commission rate, and server and energy costs.

Choosing a Data Center Location — Comparisons and Practical Tips

• The location should be chosen based on access to peers, cost, local regulations, and latency.
• For a validator, uptime and stability are more important than latency; a data center with high SLA and DDoS protection is important.
• For MEV or trade-related services, location close to major ecosystems (EU/US/Asia) is important to reduce latency.
• Using multiple locations (multi-region) for redundancy is recommended (Active/Passive or Active/Active).

Here are our company services with 85+ global locations, BGP network, anti-DDoS servers, graphics server (GPU Cloud), and high-performance cloud server are considered as suitable options for deploying nodes, validators, and mining/rendering servers.

Practical tips and checklist for a successful launch

Pre-deployment checklist:

• Select client type (Geth/Erigon + Lighthouse/Prysm).
• Choosing a server with NVMe and adequate bandwidth.
• Key backup and storage program.
• Monitoring and alerting (Prometheus/Grafana).
• Test restore from backup.
• Firewall and hardening settings.
• Update and patch management policies.

Practical suggestion: Deploy on a cloud server with daily snapshots and fast upgrade capability; have at least 2 servers for redundancy for the validator (one execution node and one beacon node in different locations for failover).

Conclusion

Setting up an Ethereum node and entering the world of staking or mining requires choosing the right server, maintaining key security, careful monitoring, and deciding on solo vs pooled. Services such as cloud servers, VPS, Dedicated, and GPU Cloud with DDoS protection and BGP networking can provide the right infrastructure. Information about plans and technical advice are available to help you choose the best server combination and security settings.

Frequently Asked Questions