Gravity Alpha Mainnet (L2) Node Setup
Instructions about how to run a Gravity Alpha Mainnet node.
Last updated
Was this helpful?
Instructions about how to run a Gravity Alpha Mainnet node.
Last updated
Was this helpful?
We'd like to inform you that ArbOS32 will be activated on Gravity chain in the new year, and we are migrating from AnyTrust to Celestia for data availability.
Prior to April 18th, 2025, please do the following:
Upgrade to Node version nitro-node >= v3.3.2 (Celestia fork)
Configure your node to support both data availability sources
A local directory for storing node data
An Ethereum mainnet RPC endpoint with unlimited rate limit for eth_getLogs
An Ethereum beacon chain RPC endpoint
Connection to a Celestia lightnode or public RPC endpoint
Setup the Celestia DAS Server
Repository:
Configuration for mainnet:
Connect to a Celestia RPC endpoint
Use
Or setup your own Celestia lightnode
Syncing a node from scratch can be extremely time-consuming and resource-intensive. We strongly recommend downloading our latest snapshot:
Extract the snapshot to your local directory before running the node.
In our experiment, syncing from scratch without using snapshots will take 12-15 days for Gravity Alpha Mainnet. The experiment was done in March 2025, when the block height of Gravity Alpha Mainnet is around 51,413,000.
Save the following script as run-gravity-node.sh
, make it executable with chmod +x run-gravity-node.sh
, and update the TODO variables:
The chain info is obtained from Conduit:
Relay endpoint is provided by Conduit as wss://relay-gravity-mainnet-0.t.conduit.xyz
Gravity Alpha Mainnet uses Anytrust DA, with aggregator URL: https://das-gravity-mainnet-0.t.conduit.xyz
Celestia namespace for Gravity mainnet: 0000047d50b18e30e965
For more information, please check out the following guides: