Nodepilot Base Instructions
Important note for Base node operators
Base node operators require some manual steps to be performed after their node is up.
Update the L1 URL
With all the recent changes going with base, to run a base node now, you need to also run an ethereum node. This ethereum node should be fully synced and the CL and EL endpoints should be accessible to the base node.
Peform the following steps once your base node is up and has extracted the snapshot. To check whether snapshot is extracted, you can check the section below.
- SSH to your base node —> become the base user by running
sudo su - base
—> cd into/home/base/node
directory. - Modify the
.env
file in this directory by using your choice of editor. For example,nano .env
.- You can keep
OP_NODE_L1_ETH_RPC
as it is or change it to your own ethereum node Geth RPC endpoint likehttp://<eth-node-ip>:8545
. - Change the value of
OP_NODE_L1_BEACON
tohttp://<eth-node-ip>:5052
.
- You can keep
- Save the file and exit the editor. run
docker compose up -d
to restart the base node. - check the logs of docker container.
Check if snapshot is extracted
After you see node in “Ready” state on Scale3 platform, you can whitelist your IP and ssh the node. Run the following command to check if the snapshot script is running:
If you see the process running, it means the snapshot is being extracted. To check logs of the snapshot script, run:
They are not much useful, but good to have.
To check the disk unilization by snapshot, run df -h | grep /data
.
If you wish to manually restore snapshot, you can find the snapshot script in directory /home/base/scripts
.
Eg: command to run the script is
If you have more queries, please reachout to us on live chat or on Discord.