🦦
Erigon 2 Documentation
  • Welcome to Erigon 2
    • Disclaimer
    • Project Links
  • ELI5 NODES
    • How to run an Ethereum node
    • How to run a Gnosis Chain node
    • How to run a Polygon node
  • Basic usage
    • Getting started
      • Linux and MacOS
      • Windows
      • Docker
    • Usage
      • Type of Node
    • Upgrading from a previous version
    • Supported Networks
    • Default Ports and Firewalls
    • Otterscan
    • Wallet
  • Advanced Usage
    • Configure Erigon
    • Consensus Layer
      • Prysm
      • Lighthouse
      • JWT secret
      • Block production
    • Options
    • RPC daemon
    • TxPool
    • Sentry
    • Downloader
    • TLS Authentication
    • ❔FAQ
    • External resources
      • Erigon on a Raspberry Pi 4
  • DIAGNOSTIC TOOL
    • Introduction
    • Installation
    • Setup
    • User Interface
  • About
    • Contributing to Erigon
    • Donate
    • License
    • Privacy policy
Powered by GitBook
On this page
  • System Requirements
  • Install Erigon​
  • Start Erigon​
  • Basic Configuration​

Was this helpful?

  1. ELI5 NODES

How to run an Ethereum node

Last updated 2 months ago

Was this helpful?

System Requirements

Follow the :

  • For an of Ethereum mainnet: 3.5 TB

  • For a of Holesky testnet : 190 GB

DO NOT USE HDD: Hard Disk Drives (HDD) are not recommended for running Erigon, as it may cause the node to stay N blocks behind the chain tip and lead to performance issues.

USE SSD or NVMe: Solid State Drives (SSD) or Non-Volatile Memory Express (NVMe) drives are recommended for optimal performance. These storage devices provide faster read/write speeds and can handle the demanding requirements of an Erigon node.

Install Erigon

For MacOS and Linux, run the following commands to build the latest Erigon version from source:

git clone --branch v2.61.3 --single-branch https://github.com/erigontech/erigon.git
cd erigon
make erigon

This should create the binary at ./build/bin/erigon.

If you are using Windows follow first the dedicated or use .

Start Erigon

Alongside Erigon you must use a like Prysm or Lighthouse. This will also allow you to access the Ethereum blockchain directly and give you the possibility to stake your GNO and do .

Start Erigon

./build/bin/erigon

Install and run Prysm:

In order to communicate with Erigon the execution endpoint <erigon address>:8551 must be specified, where <erigon address> is either //localhost or the IP address of the device running Erigon.

./prysm.sh beacon-chain --execution-endpoint=http://localhost:8551 --mainnet --jwt-secret=/home/admin/.local/share/erigon/jwt.hex --checkpoint-sync-url=https://beaconstate.info --genesis-beacon-api-url=https://beaconstate.info

Start Erigon

./build/bin/erigon

Install and run Lighthouse:

In order to communicate with Erigon the execution endpoint <erigon address>:8551 must be specified, where <erigon address> is either //localhost or the IP address of the device running Erigon.

lighthouse bn \
  --network mainnet \
  --execution-endpoint http://localhost:8551 \
  --execution-jwt /home/admin/.local/share/erigon/jwt.hex \
  --checkpoint-sync-url https://mainnet.checkpoint.sigp.io \
  • If you want to store Erigon files in a non-default location, add flag --datadir=<your_data_dir>

    • Default data directory is /home/admin/.local/share/erigon.

  • Default chain is --chain=mainnet, add the flag:

    • --chain=sepolia for Sepolia testnet;

    • --chain=holesky for Holesky testnet.

  • To increase download speed add --torrent.download.rate=512mb (default is 16mb)

Prysm must fully synchronize before Erigon can start syncing, since Erigon requires an existing target head to sync to. The quickest way to get Prysm synced is to use a public checkpoint synchronization endpoint from the list at .

Prysm must point to the automatically created by Erigon in the directory (in the below example the default data directory is used).

If your Prysm is on a different device, add --authrpc.addr 0.0.0.0 ( listens on localhost by default) as well as --authrpc.vhosts <CL host>.

Because Erigon needs a target head in order to sync, Lighthouse must be synced before Erigon may synchronize. The fastest way to synchronize Lighthouse is to use one of the many public checkpoint synchronization endpoints at .

Lighthouse must point to the automatically created by Erigon in the directory (in the below example the default data directory is used).

Basic Configuration

--prune=hrtc to run a with latest 90'000 blocks instead of an . If you change your mind remember to delete the --datadir folder content.

--http.addr="0.0.0.0" --http.api=eth,web3,net,debug,trace,txpool to use and e.g. be able to connect your .

To stop the Erigon node you can use the CTRL+C command. Additional flags can be added to the node with several .

https://eth-clients.github.io/checkpoint-sync-endpoints
Engine API
https://eth-clients.github.io/checkpoint-sync-endpoints
​
RPC
wallet
configure
options
JWT secret
datadir
JWT secret
datadir
​
installation
guide
Docker
​
Consensus Layer
block production
Prerequisites
Run a Node and Stake ETH using Prysm | Prysm
Prysm installation instructions
Logo
Installation - Lighthouse Book
Lighthouse installation instructions
Logo
archive node
full node
full node
archive node
Page cover image