The Boba Mainnet archive node has a size of 12GB on July 29, 2024
Boba
Boba is built on the Optimistic Rollup developed by Optimism.
In this guide, we are walking through the process of setting up a Boba Mainnet archive node using a forked version of Optimism's op-erigon,op-node and l2geth. These three components must be configured together to ensure that the node can effectively serve all historical data, which may be necessary when an Indexer syncs a specific subgraph on the Boba Network
Before you start, make sure that you have your own synced Ethereum L1 RPC URL (e.g. Erigon) and L1 Consensus Layer Beacon endpoint with all historical blobs data (e.g. Lighthouse) ready.
sudo ufw allow from ${REMOTE.HOST.IP} to any port 9545 8545
Not advised to allow all or unknown IP address to RPC port
Enable Firewall
sudo ufw enable
To check the status of UFW and see the current rules
sudo ufw status verbose
Install dependencies
Required Software Dependencies
Dependency
Version
Version Check Command
go
^1.21
go version
node
^20
node --version
pnpm
^8
pnpm --version
foundry
^0.2.0
forge --version
make
^4
make --version
yarn
1.22.21
yarn --version
nvm
0.39.3
nvm --verison
Install GO
sudo wget https://go.dev/dl/go1.21.6.linux-amd64.tar.gz && sudo rm -rf /usr/local/go && sudo tar -C /usr/local -xzf go1.21.6.linux-amd64.tar.gz && rm go1.21.6.linux-amd64.tar.gz
#to verify Go installation
go version
#If it returns Command 'go' not found simply run
echo 'export PATH=$PATH:/usr/local/go/bin:/root/.local/bin' >> /root/.bashrc
#and then apply changes with
source /root/.bashrc
git clone https://github.com/bobanetwork/boba.git
cd boba
Check out the required release branch
Release branches are created when new versions of the op-node are created. Read through the Releases page to determine the correct branch to check out.
Replace {L1 RPC endpoint} and {L1 Beacon RPC endpoint} with your synced endpoints
Build Legacy Geth (l2geth)
Clone the Boba Legacy Monorepo and build l2geth:
cd /root/
git clone https://github.com/bobanetwork/boba_legacy.git
cd boba_legacy
cd l2geth
make geth
Create database directory for l2geth, download and extract archive snapshot:
mkdir -p /root/data/boba/boba-legacy/ && cd /root/data/boba/boba-legacy/
aria2c --file-allocation=none -c -x 10 -s 10 "https://boba-db.s3.us-east-2.amazonaws.com/mainnet/boba-mainnet-geth-db-legacy.tgz"
tar -xzvf boba-mainnet-geth-db-legacy.tgz
rm -rf boba-mainnet-geth-db-legacy.tgz
ls #to see the name of extracted archive folder
mv /root/data/boba/boba-legacy/geth-1149018/* /root/data/boba/boba-legacy/
rm -rf geth-1149018
Create systemd service for l2geth
sudo nano /etc/systemd/system/boba-legacy.service
Paste the configs and save by entering ctrl+X and Y+ENTER:
cd /root/
git clone https://github.com/bobanetwork/op-erigon.git
cd op-erigon
Release branches are created when new versions of the erigon are created. Read through the Releases page to determine the correct branch to check out.
git checkout v1.1.5
make erigon
Create database directory, download and extract the most recent snapshot
Consider verifying a snapshot by comparing the sha256sum of the downloaded file to the sha256sum listed on this page. Check the sha256sum of the downloaded file by running sha256sum <filename>in a terminal
It's usually simpler to begin with startingop-erigon before you start op-node. You can start op-erigon even if op-node isn't running yet, but op-erigon won't get any blocks until op-node starts.
sudo systemctl daemon-reload #refresh systemd configuration when changes made
sudo systemctl enable op-erigon.service #enable op-erigon service at system startup
sudo systemctl start op-erigon.service #start op-erigon
sudo nano /etc/systemd/system/op-erigon.service #make changes in op-erigon.service file
Start op-node
Once you've started op-erigon, you can start op-node. op-node will connect to op-erigon and begin synchronizing the BOBA network. op-node will begin sending block payloads to op-erigon when it derives enough blocks from Ethereum
sudo systemctl daemon-reload #refresh systemd configuration when changes made
sudo systemctl enable op-node.service #enable op-node service at system startup
sudo systemctl start op-node.service #start op-node
sudo nano /etc/systemd/system/op-node.service #make changes in op-node.service file
Start l2geth
sudo systemctl daemon-reload #refresh systemd configuration when changes made
sudo systemctl enable boba-legacy.service #enable l2geth service at system startup
sudo systemctl start boba-legacy.service #start l2geth
sudo nano /etc/systemd/system/boba-legacy.service #make changes in boba-legacy.service file
Monitor the logs for errors
sudo journalctl -fu op-node.service #follow logs of op-node.service
sudo journalctl -fu op-erigon.service #follow logs of op-erigon.service
sudo journalctl -fu boba-legacy.service #follow logs of boba-legacy.service
During the initial synchonization, you are expected to get following log messages from op-node
INFO [08-04|16:36:07.150] Advancing bq origin origin=df76ff..48987e:8301316 originBehind=false
After a few minutes, op-node finds the right batch and then it starts synchronizing. During this synchonization process, you get log messags from op-node
INFO [08-04|16:36:01.204] Found next batch epoch=44e203..fef9a5:8301309 batch_epoch=8301309 batch_timestamp=1,673,567,518
INFO [08-04|16:36:01.205] generated attributes in payload queue txs=2 timestamp=1,673,567,518
INFO [08-04|16:36:01.265] inserted block hash=ee61ee..256300 number=4,069,725 state_root=a582ae..33a7c5 timestamp=1,673,567,518 parent=5b102e..13196c prev_randao=4758ca..11ff3a fee_recipient=0x4200000000000000000000000000000000000011 txs=2 update_safe=true
Run curl command in the terminal to check the status of your node
curl -H "Content-type: application/json" -X POST --data '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}' http://localhost:9545
If it returns false then your node is fully synchronized with the network
