Full Node Build
Install pre-requisites
Install Go
Follow the instructions here to install Go.
For an Ubuntu LTS, we can use:
Unless you want to configure in a non standard way, then set these in the .zshrc
in the user's home (i.e. ~/
) folder.
Add the "export Pathing" rules at the bottom, and then save the file:
After updating your ~/.zshrc
you will need to source it:
Build Daemon from source
To confirm that the installation has succeeded, you can run:
Setup P2P Network
Configure the Node
Initialize Node
The command below will initialize the node, and generate a random 32-bit string for the node moniker
. This provides increased privacy from tools like Observatory.
Download Genesis
This will generate the following files in ~/.celestia-appd/config/
genesis.json
node_key.json
priv_validator_key.json
Set Seeds
We can add these seeds
to our config.toml
:
Update Node configs
We can use sed
to update various node configuration values without having to manually edit each file - which can be a pain.
Replace the values below with your own. These commands will update the following:
minimum_gas_prices
pruning
configssnapshot
configs
Updating node ports
We'll use a powerful tool called sed
for this process. sed
is a stream editor that can perform operations, like substitutions, on a text file.
We will specifically focus on updating the ports to use a standardized prefix for your chain. This ensures consistency and improves overall system organization. It will also allow you to run multiple chains on a single server.
Let's start by understanding what we're updating:
proxy_app: This is the address used for inter-process communication between the ABCI application and the consensus engine.
laddr: This is the address that your node listens on for incoming connections.
pprof_laddr: This is the address for the profiling server to listen on.
prometheus_listen_addr: This is the address for the Prometheus metrics server to listen on.
address: These are various addresses that your node may use to listen for different types of connections.
Set Your Chain and Port Prefix
Your chain in this case is Celestia
. For Celestia
, we want to set the port prefix as 116
. The port prefix will be used to replace the first 2 or 3 digits of the original ports.
Update config.toml
Next, we will update the config.toml
file. For 5-digit ports, the first 3 digits will be replaced. Here is how to calculate the new port values and update the config.toml
file:
Update app.toml
For 4-digit ports, the first 2 digits will be replaced. Here is how to calculate the new port values and update the app.toml
file:
Create (or restore) a local key pair
Either create a new key pair or restore an existing wallet for your validator:
After creating a new key, the key information and seed phrase will be shown. It is essential to write this seed phrase down and keep it in a safe place. The seed phrase is the only way to restore your keys.
Setup cosmovisor
Follow the Setup Cosmovisor instructions to setup cosmovisor and start the node.
Upgrade to a validator
Do not attempt to upgrade your node to a validator until the node is fully in sync as per the previous step.
To upgrade the node to a validator, you will need to submit a create-validator
transaction:
The above transaction is just an example. There are many more flags that can be set to customize your validator, such as your validator website, or keybase.io id, etc. To see a full list:
Backup critical files
There are certain files that you need to back up to be able to restore your validator if, for some reason, it damaged or lost in some way. Please make a secure backup of the following files located in ~/.
celestia-app/config/
:
priv_validator_key.json
node_key.json
It is recommended that you encrypt and backup of these files.
Last updated