The Zora Mainnet archive node has a size of 693GB on October 10th, 2024
Zora
Zora operates within Optimism Superchain ecosystem and is built using the OP stack, leveraging the scalability and security of Optimism's Layer 2 infrastructure.
In this guide, we are walking through the process of setting up a Zora Mainnet archive node using Optimism's op-gethand op-node.
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. A beacon endpoint meeting this criteria is essential for syncing to start.
sudo ufw allow from ${REMOTE.HOST.IP} to any port 8545
sudo ufw allow from ${REMOTE.HOST.IP} to any port 7545
Not advised to allow all or unknown IP address to RPC port
sudo ufw allow 9222
sudo ufw allow 30303
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
cd #to return to /root/ directory
git clone https://github.com/mehdius1364/node
cd node
export CONDUIT_NETWORK=zora-mainnet-0
./download-config.py $CONDUIT_NETWORK
#move genesis.json and rollup.json into op-geth directory
mv /root/node/networks/zora-mainnet-0/genesis.json /root/node/networks/zora-mainnet-0/rollup.json /root/data/zora/zora-op-geth/
Build op-node
cd /root/zora/
git clone https://github.com/ethereum-optimism/optimism.git
cd optimism
git checkout v1.9.1
make op-node
# The binary is built at /root/zora/optimism/op-node/bin/op-node
cat /root/data/zora/zora-op-geth/jwt.hex #to retrieve {JWT} value
Build the Execution Engine (op-geth)
Build op-geth
cd /root/zora/
git clone https://github.com/ethereum-optimism/op-geth.git
cd op-geth
git checkout v1.101408.0
make geth
# The binary is built at /root/github/op-geth/build/bin/geth
It's usually simpler to begin with startingop-geth before you start op-node. You can start op-geth even if op-node isn't running yet, but op-geth won't get any blocks until op-node starts.
sudo systemctl daemon-reload #refresh systemd configuration when changes made
sudo systemctl enable zora-op-geth.service #enable zora-op-geth service at system startup
sudo systemctl start zora-op-geth.service #start op-geth
sudo nano /etc/systemd/system/zora-op-geth.service #make changes in zora-op-geth.service file
Start op-node
Once you've started op-geth, you can start op-node. op-node will connect to op-geth and begin synchronizing the Zora network. op-node will begin sending block payloads to op-geth when it derives enough blocks from Ethereum
sudo systemctl daemon-reload #refresh systemd configuration when changes made
sudo systemctl enable zora-op-node.service #enable zora-op-node service at system startup
sudo systemctl start zora-op-node.service #start zora-op-node
sudo nano /etc/systemd/system/zora-op-node.service #make changes in zora-op-node.service file
Monitor the logs for errors
sudo journalctl -fu zora-op-node.service #follow logs of zora-op-node.service
sudo journalctl -fu zora-op-geth.service #follow logs of zora-op-geth.service
You are expected to get following log messages from op-node