π»Baremetal
Authors: [man4ela | catapulta.eth]
System Requirements
8+ cores CPU
Debian 12/Ubuntu 22.04
=> 16 GB RAM
=1TB+
(NVMe)
Setup of BSC Erigon
This guide covers the installation of BSC Erigon V3, which is Erigon V3's fork managed by Node-Real. It has built-in snapshot download function and allows to sync BSC Testnet Chapel archive Node in effecteively 48 hours. It is important to keep in mind that the client is still under development and you need to be prepared to face difficulties during synchronization or other techincal issues
Pre-Requisites
sudo apt update -y && sudo apt upgrade -y && sudo apt autoremove -y
sudo apt install -y libgtest-dev libomp-dev libgmp-dev git make wget aria2 gcc pkg-config libusb-1.0-0-dev libudev-dev jq g++ curl libssl-dev screen apache2-utils build-essentialSetting up Firewall
Set explicit default UFW rules
sudo ufw default deny incoming
sudo ufw default allow outgoingAllow SSH and peers
sudo ufw allow 22/tcp
sudo ufw allow 30303 #p2p port
sudo ufw allow 42069 #torrent portAllow remote RPC connections with the Node
Not advised to allow all or unknown IP address to RPC port
Enable Firewall
To check the status of UFW and see the current rules
Install GO
Build Erigon RPC Node
Check for the latest actual release at https://github.com/node-real/bsc-erigon/releases
This guide has been tested and successfully synced the node with v1.3.2-beta2:
Create Data directory and jwt secret file
Create Systemd service for BSC Erigon
Paste the configs and save by entering ctrl+X and Y+ENTER:
Replace {IP} with the actual address of the server in order to to explicitly set the external IP address that the node should advertise to peers in a P2P network
Launch BSC Erigon
Monitor the logs for errors
During the inizializtion, first you are expected to see logs of a snapshot download process :
If the download progress shows 0% for too long, try restarting the client. Once the snapshot has been fully downloaded and applied by the client, the node will start syncing process and will reach a chainhead in under 48 hrs
Run curl command in the terminal to check the status of your node
curl command in the terminal to check the status of your nodeWhen it returns false then your node is fully synchronized with the network
References
Last updated