💻Baremetal
Authors: [man4ela | catapulta.eth]
System Requirements
8+ cores CPU
Debian 12/Ubuntu 22.04
=> 16 GB RAM
1,5TB+ (SSD or NVMe)
Unichain
Unichain operates within Optimism Superchain ecosystem. It is powered by the OP Stack, in collaboration with Optimism, leveraging the scalability and security of Optimism's Layer 2 infrastructure.
In this guide, we are walking through the process of setting up a Unichain Mainnet archive node using Optimism's op-geth and 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.
Pre-Requisites
sudo apt update -y && sudo apt upgrade -y && sudo apt autoremove -y
sudo apt install -y git make wget aria2 gcc pkg-config libusb-1.0-0-dev libudev-dev jq gcc g++ curl libssl-dev screen apache2-utils build-essential pkg-configvSetting up Firewall
Set explicit default UFW rules
Allow SSH
Allow remote RPC connections with Mode Node
Allow remote P2P connections with Mode 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 dependencies
Required Software Dependencies
go
^1.23
go version
docker
^28
docker version
Install GO
Install Docker
Check if Go and all dependencies are installed
Build the Rollup Node (op-node)
Create working directory
Install Op-node
Build the Execution Engine (op-geth)
Build op-geth
Download genesis.json and create jwt.hex into database directory:
Create systemd service for op-node
Save by entering ctrl+X and Y+ENTER
Create systemd service for op-geth
Paste the following configs:
Initialize the node:
Launch Unichain
Start op-geth
Start op-node
Monitor the logs for errors
You are expected to get following log messages from op-node
The expected log messages from op-geth:
Run curl command in the terminal to check the status of your node
curl command in the terminal to check the status of your nodeIf it returns false then your node is fully synchronized with the network
Sync speed depends on your L1 node, as the majority of the chain is derived from data submitted to the L1.
You can check your syncing status using the optimism_syncStatus RPC on the op-node
optimism_syncStatus RPC on the op-nodeReferences
Last updated
Was this helpful?