Erigon
Overview
Official Links
1. Initial configuration
Create a service user for the execution service, create data directory and assign ownership.
sudo adduser --system --no-create-home --group execution
sudo mkdir -p /var/lib/erigon
sudo chown -R execution:execution /var/lib/erigon
Install dependencies.
sudo apt install curl libsnappy-dev libc6-dev jq libc6 unzip -y
2. Install Binaries
Downloading binaries is often faster and more convenient.
Building from source code can offer better compatibility and is more aligned with the spirit of FOSS (free open source software).
3. Setup and configure systemd
Create a systemd unit file to define your execution.service
configuration.
sudo nano /etc/systemd/system/execution.service
Paste the following configuration into the file.
[Unit]
Description=Erigon Execution Layer Client service for Mainnet
Wants=network-online.target
After=network-online.target
Documentation=https://www.nodebridgeafrica.com
[Service]
Type=simple
User=execution
Group=execution
Restart=on-failure
RestartSec=3
KillSignal=SIGINT
TimeoutStopSec=900
ExecStart=/usr/local/bin/erigon \
--datadir /var/lib/erigon \
--chain mainnet \
--port 30303 \
--torrent.port 42069 \
--maxpeers 50 \
--private.api.addr 127.0.0.1:9099 \
--authrpc.port 8551 \
--metrics \
--pprof \
--prune htc \
--prune.r.before=11052984 \
--authrpc.jwtsecret=/secrets/jwtsecret
[Install]
WantedBy=multi-user.target
To exit and save, press Ctrl
+ X
, then Y
, then Enter
.
Run the following to enable auto-start at boot time.
sudo systemctl daemon-reload
sudo systemctl enable execution
Finally, start your execution layer client and check it's status.
sudo systemctl start execution
sudo systemctl status execution
Press Ctrl
+ C
to exit the status.
4. Helpful execution client commands
sudo journalctl -fu execution | ccze
A properly functioning Erigon execution client will indicate "Handling new payload". For example,
erigon[3]: [INFO] [09-29|03:36:24.689] [NewPayload] Handling new payload height=19999 hash=0xea060...2846a907ceb4
erigon[3]: [INFO] [09-29|03:36:25.278] [updateForkchoice] Fork choice update: flushing in-memory state (built by previous newPayload)
erigon[3]: [INFO] [09-29|03:36:25.280] RPC Daemon notified of new headers from=19998 to=19999 hash=0xeeed..710b597 header sending=13.32ยตs log sending=290ns
erigon[3]: [INFO] [09-29|03:36:25.280] head updated hash=0xea06098ad5e...5e5f43 number=20000
Now that your execution client is configured and started, proceed to the next step on setting up your consensus client.
If you're checking the logs and see any warnings or errors, please be patient as these will normally resolve once both your execution and consensus clients are fully synced to the Ethereum network.
Last updated