Setting up a Celestia Full Storage Node
This tutorial will guide you through setting up a Celestia Full Storage Node, which is a Celestia node that doesn't connect to Celestia App (hence not a full node) but stores all the data.
The following hardware minimum requirements are recommended for running the full storage node:
- Memory: 8 GB RAM
- CPU: Quad-Core
- Disk: 250 GB SSD Storage
- Bandwidth: 1 Gbps for Download/100 Mbps for Upload
Setting up your full storage node
The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64 instance machine.
Setup the dependencies
You can follow the tutorial for setting up your dependencies here
Install Celestia node
Note: Make sure that you have at least 250+ Gb of free space for Celestia Full Storage Node
You can follow the tutorial for installing Celestia Node here
Run the full storage node
Initialize the full storage node
Run the following command:
celestia full init
Start the full storage node
Start the Full Storage Node with a connection to a validator node's gRPC endpoint (which is usually exposed on port 9090):
NOTE: In order for access to the ability to get/submit state-related information, such as the ability to submit PayForData transactions, or query for the node's account balance, a gRPC endpoint of a validator (core) node must be passed as directed below.
A note on ports:
--core.grpc.portdefaults to 9090, so if you do not specify it in the command line, it will default to that port. You can use the flag to specify another port if you prefer.
celestia full start --core.ip http://<ip-address> --core.grpc.port <port>
celestia full start --core.remote <ip-address>:<port>
If you would like to find example RPC endpoints, check out the list of resources here.
You can create your key for your node by following the
cel-key instructions here
Once you start the Full Node, a wallet key will be generated for you. You will need to fund that address with testnet tokens to pay for PayForData transactions. You can find the address by running the following command:
./cel-key list --node.type full --keyring-backend test
You have two networks to get testnet tokens from:
NOTE: If you are running a full-storage node for your sovereign rollup, it is highly recommended to request Arabica devnet tokens as Arabica has the latest changes that can be used to test for developing your sovereign rollup. You can still use Mamaki Testnet as well, it is just mostly used for Validator operations.
Optional: run the full storage node with a custom key
In order to run a full storage node using a custom key:
- The custom key must exist inside the celestia full storage node directory
at the correct path (default:
- The name of the custom key must be passed upon
start, like so:
celestia full start --core.ip http://<ip-address> --core.grpc.port <port> --keyring.accname <name-of-custom-key>
celestia full start --core.remote <ip-address>:<port> --keyring.accname <name-of-custom-key>
Optional: start the full storage node with SystemD
Follow the tutorial on setting up the full storage node as a background process with SystemD here.
With that, you are now running a Celestia Full Storage Node.