Aller au contenu principal

Celestia Node

This tutorial goes over building and installing celestia-node. This tutorial assumes you completed the steps in setting up your development environment here.

Install celestia-node

Installing celestia-node for the Blockspace Race testnet means installing a specific version to be compatible with the network.

Install the celestia-node binary by running the following commands:

cd $HOME
rm -rf celestia-node
git clone
cd celestia-node/
git checkout tags/v0.10.2
make build
make install
make cel-key

Verify that the binary is working and check the version with the celestia version command:

$ celestia version
Semantic version: v0.10.2
Commit: 960b522ec4ed2fb2069a220e2cef2da609158f4d
Build Date: Thu Dec 15 10:19:22 PM UTC 2022
System version: amd64/linux
Golang version: go1.20.2


When interacting with a Celestia node, you may need to open ports on your machine to allow communication between nodes, such as bridge nodes. It is essential that specific ports are accessible. Make sure that your firewall allows connections to the correct ports.

If you run a node on a cloud server, make sure that the ports are open on the server's firewall. If you run a node at home, make sure that your router allows connections to the correct ports.

For example, validator ports 9090 and 26657 need to be accessible by the bridge, and port 2121 is required for P2P connections for all node types.

The following ports are used by Celestia nodes:

PortProtocolAddressDescriptionEnabled by default on nodeFlag
26658HTTPlocalhostRPCtrue--rpc.port string
26659HTTPlocalhostREST Gatewayfalse--gateway.port string

Upgrading your binary

To upgrade your binary, you can use the following commands:

  1. Install the latest version of the celestia-node binary. The latest version will overwrite your existing binary.
  1. For bridge, full, and light nodes, remove the data store:
celestia <node-type> unsafe-reset-store <network>
  1. Then you can remove the old config with:
celestia <node-type> config-remove <network>
  1. And restart your node:
celestia <node-type> start <network>

Changing the location of your node store

In this section, we'll guide you through starting your node using a node store in a different location than you originally started with.

First, stop your node safely using control + C.

Then, init your node again with a new node store:

celestia <node-type> init /home/user/celestia-<node-type>-location/ blockspacerace

Next, start your node:

celestia full start --core.ip blockspacerace /home/user/celestia-<node-type>-location/

If you choose to change the location of your node store, you will need to execute each command on your node with the following flag: /home/user/celestia-<node-type>-location/

When using cel-key, the process is different. To show the keys you should add --keyring-dir like this example:

./cel-key list blockspacerace --node.type full --keyring-dir /home/user/celestia-<node-type>-location/keys/


Network selection

Note: If you do not select a network, the default network will be 'Mocha'.

celestia <node-type> init <network>
celestia <node-type> start <network> --core.ip <address> --gateway --gateway.addr <ip-address> --gateway.port <port>

Please refer to the ports section for information on which ports are required to be open on your machine.

NOTE: It is advised before switching networks to reinitialize your node via init command. This is due to an old config being present. Re-initialisation will reset the config.

Resetting your config

If you an encounter an error, it is likely that an old config file is present:

Error: nodebuilder/share: interval must be positive; nodebuilder/core: invalid IP addr given:

# or

Error: nodebuilder/share: interval must be positive

You can re-initialize your node's config with the following commands:


Save your config so custom values are not lost.

All node types on v0.9.1 and later

Run the following command to update your config:

celestia <node-type> config-update <network>

This will pull in any new values from new configuration and merge them into the existing configuration.


After using the config-update command, it is encouraged to double-check that your custom values are preserved.

Then, to start your node again:

celestia <node-type> start <network>

Clearing the data store

Version 0.9.0+

For bridge, full, and light nodes, remove the data store with this command:

celestia <node-type> unsafe-reset-store <network>
Example for light node on Blockspace Race on v0.9.0+
celestia light unsafe-reset-store blockspacerace

Please refer to the ports section for information on which ports are required to be open on your machine.

FATAL headers given to the heightSub are in the wrong order

If you observe a FATAL log line like:

FATAL   header/store    store/heightsub.go:87   PLEASE FILE A BUG REPORT: headers given to the heightSub are in the wrong order"

then it is possible the celestia-node data/ directory contains headers from a previous instance of the network that you are currently trying to run against. One resolution strategy is to delete the existing celestia-node config for the target network and re-initialize it:

# rm -rf ~/.celestia-<node-type>-<network>
rm -rf ~/.celestia-bridge-private

# celestia <node-type> init <network>
celestia bridge init private