This is a set up guide for a Validator Node on Celestia’s Mamaki Testnet, this also applies to set up a full node, up until Step 7.

Mamaki test network is deprecated now and replaced with Mocha test network, please see this guide for updated instructions

https://mirror.xyz/0xf3bF9DDbA413825E5DdF92D15b09C2AbD8d190dd/AM4qp-HcHmTDu3rFLVyQVBGlqnSeLElKzrZ_iSoFHW4

First, make sure to update and upgrade the OS:

sudo apt update && sudo apt upgrade -y

Install essential packages for Celestia

These are essential packages that are necessary to execute many tasks like downloading files, compiling and monitoring the node:

sudo apt install curl tar wget clang pkg-config libssl-dev jq build-essential bsdmainutils git make ncdu -y

Firewall Settings

we need to enable firewall and open ports on our device

sudo ufw allow 26657/tcp
sudo ufw allow 26656/tcp          #Port listen for incom TXs, config
sudo ufw allow 9090/tcp
sudo ufw enable

sudo ufw status

IMPORTANT: If you are going to remote into this server, make sure to enable SSH before enabling ufw

Additional Ports

These are additional ports from some additional bootstrap Peers to help with syncing (these additional peers are added later, and can change)

#these ports are to the ones in additional peers, add in the same method as above
16656,57030,41768,52552,43656,50674,41622,2665,41914,36126,41636,49656,47474,54244,44306,38360,57914,37462,37898,37754,5603,39208,49052,36656,26676,26666

Install Golang

remove any existing installation

sudo rm -rf /usr/local/go
sudo rm -rf ~/go

cd $HOME
sudo wget https://golang.org/dl/go1.18.2.linux-amd64.tar.gz
sudo tar -xvf go1.18.2.linux-amd64.tar.gz
sudo rm go1.18.2.linux-amd64.tar.gz
sudo mv go /usr/local

Now we need to add the /usr/local/go/bin directory to $PATH:

mkdir ~/go
echo 'GOROOT=/usr/local/go' >> ~/.bashrc
echo 'GOPATH=~/go' >> ~/.bashrc
echo 'PATH=$PATH:$GOROOT/bin:$GOPATH/bin' >> ~/.bashrc

make changes to the applicable file, should now be persistent in the .bashrc

source .bashrc

Confirm installation

go version

This should Return

go version go1.18.2 linux/amd64

For Celestia Validator Node setup: running a Celestia App daemon with an internal Celestia Core node. https://docs.celestia.org/developers/celestia-app/, the application will be configured as a validator later.

Install Celestia App

create a binary file named celestia-appd inside $HOME/go/bin folder which will be used later to run the node. Check the Discord ‘mamaki testnet’ announcements for the latest version (currently this is v0.6.0)

cd $HOME 
rm -rf celestia-app 
git clone https://github.com/celestiaorg/celestia-app.git 
cd celestia-app 
git checkout v0.6.0 
make install

check if the binary was successfully compiled, will output help example commands

celestia-appd --help

cd $HOME
rm -rf networks
git clone https://github.com/celestiaorg/networks.git

set variables with whatever you want in <> but do not change Network: mamaki

CELESTIA_NODENAME="<YOUR_NODE_NAME>" 
CELESTIA_WALLET="<YOUR_WALLET_NAME>" 
CELESTIA_CHAIN="mamaki"

save the variables

echo 'export CELESTIA_CHAIN='$CELESTIA_CHAIN >> $HOME/.bashrc
echo 'export CELESTIA_NODENAME='${CELESTIA_NODENAME} >> $HOME/.bashrc
echo 'export CELESTIA_WALLET='${CELESTIA_WALLET} >> $HOME/.bashrc
source $HOME/.bashrc

Initialize the application node

celestia-appd init $CELESTIA_NODENAME --chain-id $CELESTIA_CHAIN

Copy the config genesis file

cp $HOME/networks/mamaki/genesis.json $HOME/.celestia-app/config/

Set to validator mode (IF YOU ONLY WANT TO RUN A FULL NODE SKIP THIS LINE)

sed -i 's/mode = \"full\"/mode = \"validator\"/g' $HOME/.celestia-app/config/config.toml

Set up P2P Networks: Bootstrap Peers and Additional Peers

update bootstrap peers

BOOTSTRAP_PEERS=$(curl -sL https://raw.githubusercontent.com/celestiaorg/networks/master/mamaki/bootstrap-peers.txt | tr -d '\n')

check

echo $BOOTSTRAP_PEERS

Set, add to config

sed -i.bak -e "s/^bootstrap-peers *=.*/bootstrap-peers = \"$BOOTSTRAP_PEERS\"/" $HOME/.celestia-app/config/config.toml 

Additional Peers

NOTE: there may be additional bootstrap peers to add to this list to help with connections, check the discord and add to the config.toml

There are additional bootstrap peers that can be added from here

curl -s https://rpc-mamaki.pops.one/net_info | jq -r '.result.peers[] | .url'

Other peers from here

networks/mamaki/peers.txt at master · celestiaorg/networks

Contribute to celestiaorg/networks development by creating an account on GitHub.

https://github.com

to make changes to the config, and paste them in manually

sudo nano $HOME/.celestia-app/config/config.toml

To save time, you can copy from below and place in between the quotes on

bootstrap-peers = “<place here no spaces,to separate>”

Set Consensus Configuration Options

sed -i 's/timeout-commit = ".*/timeout-commit = "25s"/g' $HOME/.celestia-app/config/config.toml
sed -i 's/peer-gossip-sleep-duration *=.*/peer-gossip-sleep-duration = "2ms"/g' $HOME/.celestia-app/config/config.toml

Set P2P Configuration Options

max_num_inbound_peers=40 
max_num_outbound_peers=10 
max_connections=50 

sed -i -e "s/^use-legacy *=.*/use-legacy = false/;\
s/^max-num-inbound-peers *=.*/max-num-inbound-peers = $max_num_inbound_peers/;\
s/^max-num-outbound-peers *=.*/max-num-outbound-peers = $max_num_outbound_peers/;\
s/^max-connections *=.*/max-connections = $max_connections/" $HOME/.celestia-app/config/config.toml

above is the recommended settings since 0.0.6 release, these can be changed manually by

sudo nano $HOME/.celestia-app/config/config.toml

Other things recommended to change- from the 0.5.3 Release use-legacy = false pex = true peer-gossip-sleep-duration=”2ms”

For lower disk space usage, recommend setting up pruning using the configurations below.

pruning_keep_recent="100"
pruning_interval="10"

sed -i -e "s/^pruning *=.*/pruning = \"custom\"/;\
s/^pruning-keep-recent *=.*/pruning-keep-recent = \"$pruning_keep_recent\"/;\
s/^pruning-interval *=.*/pruning-interval = \"$pruning_interval\"/" $HOME/.celestia-app/config/app.toml

for pruning "100-0" you should disable snapshots to avoid conflict with 100-blocks pruning and 1500-blocks snapshot-interval

sed -i 's/snapshot-interval *=.*/snapshot-interval = 0/g' $HOME/.celestia-app/config/app.toml

Reset Before Starting the Node

celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app

Config Client

celestia-appd config chain-id $CELESTIA_CHAIN

creates an application CLI configuration file, needed for wallet later

celestia-appd config keyring-backend test

Syncing from Genesis can take a long time, depending on your hardware. Using this method you can synchronize your Celestia node very quickly by downloading a recent snapshot of the blockchain. If you would like to sync from the Genesis, then you can skip this part.

cd $HOME
rm -rf ~/.celestia-app/data
mkdir -p ~/.celestia-app/data
SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \
    egrep -o ">mamaki.*tar" | tr -d ">")
wget -O - https://snaps.qubelabs.io/celestia/${SNAP_NAME} | tar xf - \
    -C ~/.celestia-app/data/

Takes about 10-15 mins to download

Set up celestia-appd as a background process.

sudo tee <<EOF >/dev/null /etc/systemd/system/celestia-appd.service
[Unit]
Description=celestia-appd Cosmos daemon
After=network-online.target
[Service]
User=$USER
ExecStart=$HOME/go/bin/celestia-appd start
Restart=on-failure
RestartSec=3
LimitNOFILE=4096
[Install]
WantedBy=multi-user.target
EOF

enable and start the process

sudo systemctl enable celestia-appd
sudo systemctl daemon-reload
sudo systemctl start celestia-appd

Confirm its running

systemctl status celestia-appd

Output the Logs

journalctl -u celestia-appd.service -f

To Check for Sync State

curl -s localhost:26657/status | jq .result | jq .sync_info

Allow to sync before continuing

If you need to create a wallet and connect to Mamaki Testnet network

Download Keplr and create wallet

Install Keplr for chrome, and follow the steps to ‘create new wallet’ remember to save your seed phrase.

Connect Keplr to Mamaki Network

https://aviaone.com/celestia-connect-wallet-keplr-testnet-mamaki.html if you have kerplr installed and active, you will be prompted to connect network, allow this

Request Test Tokens from the Faucet

find your address on the Keplr app after selecting the correct network for Celestia (Mamaki), copy your address from Keplr and request from the Celestia discord (LINK) on the ‘faucet’ channel

$request celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Import Wallet

celestia-appd keys add $CELESTIA_WALLET --recover

Enter Seed

save address and valoper address (validator) as variables. The valoper address is the wallets validator address, which appears in different format but derived from the same seed.

CELESTIA_ADDR=$(celestia-appd keys show $CELESTIA_WALLET -a)
echo $CELESTIA_ADDR
echo 'export CELESTIA_ADDR='${CELESTIA_ADDR} >> $HOME/.bashrc

CELESTIA_VALOPER=$(celestia-appd keys show $CELESTIA_WALLET --bech val -a) 
echo $CELESTIA_VALOPER 
echo 'export CELESTIA_VALOPER='${CELESTIA_VALOPER} >> $HOME/.bashrc 
source $HOME/.bashrc

We can get our address by running the command below

celestia-appd keys show $CELESTIA_WALLET

to display wallets in stored within the node

celestia-appd keys list

To Delete old wallets

celestia-appd keys delete OLD_WALLET --keyring-backend=test

Double Check that you are Synced before continuing

curl -s localhost:26657/status | grep block_height

Check Balance, also confirm wallet set correctly

celestia-appd q bank balances $CELESTIA_ADDR

Check Variables

echo $CELESTIA_NODENAME $CELESTIA_CHAIN $CELESTIA_WALLET

Connect Validator

1TIA = 1,000,000 uTIA

celestia-appd tx staking create-validator \
 --amount=1000000utia \
 --pubkey=$(celestia-appd tendermint show-validator) \
 --moniker=$CELESTIA_NODENAME \
 --chain-id=$CELESTIA_CHAIN \
 --commission-rate=0.1 \
 --commission-max-rate=0.2 \
 --commission-max-change-rate=0.01 \
 --min-self-delegation="1" \
 --from=$CELESTIA_WALLET

This is for the first time creating validator, it will output a transaction is successful and you should be able to find in the block explorer to confirm its success.

Problems with this transaction may be a result of your node not being synced properly, double check, there’s additional ways to check sync under ‘Other commands’ section.

Download and save "$HOME/.celestia-app/config/priv_validator_key.json" to your PC!

This is important, to backup and recover your validator should you have a failure on this device. If you don’t know how to do this, there is a part on ‘Migration’ towards the end of this document, which describes the process on backing this up.

check validator

celestia-appd q staking validator $CELESTIA_VALOPER

Output active set

celestia-appd q staking validators --limit=3000 -oj \ | jq -r '.validators[] | select(.status=="BOND_STATUS_BONDED") | [(.tokens|tonumber / pow(10;6)), .description.moniker] | @csv' \ | column -t -s"," | tr -d '"'| sort -k1 -n -r | nl

Edit Avatar

celestia-appd tx staking edit-validator --identity "YOUR_KEYBASE_ID" --from $CELESTIA_WALLET

Change Moniker

celestia-appd tx staking edit-validator --from=$CELESTIA_WALLET --new-moniker <new_moniker_here> --chain-id mamaki --fees 500utia

Delegate to Validator (including your own)

example from docs

celestia-appd tx staking delegate celestiavaloper1q3v5cugc8cdpud87u4zwy0a74uxkk6u43cv6hd <ammount>utia --from=$CELESTIA_WALLET --chain-id=mamaki

Block Explorer

Main Project Information | Celestia (TIA) Blockchain Explorer

Fast, simple and secure blockchain solution to stake your crypto assets and earn yields. Stake with the best validator. High performance. Delivered.

https://celestia.explorers.guru

View Logs Methods

journalctl -u celestia-appd.service -f

journalctl -u celestia-appd -f -o cat

Check Sync Methods

curl -s localhost:26657/status | jq .result | jq .sync_info

curl -s localhost:26657/status | grep block_height

Latest block height: your nodes latest block height this should match the explorer

Max peer block height: the max height of peers you are connected to, should be close to your own if you are connected to peers

Unjail

when your validator misses signing for a period it could end up in ‘jail’ basically you receive a penalty slash and kicked out of the active set, your validator will still be active but not earning rewards or producing blocks, until you manually unjail

celestia-appd tx slashing unjail --from=$CELESTIA_WALLET --chain-id mamaki --fees=4000utia --keyring-backend=test

Should you wish to migrate device to another, for a variety of reasons such as hardware failure/ upgrades or expected downtime. I’ve had to do this recently myself, so I am documenting a process for reference to minimise downtime.

1. Backup Priv_validator_key.json

On the Old Device that you wish to retire Locate priv_validator_key.json it should be in here by default

cd .celestia-app/config
ls -la

copy to a backup folder, double check the username with, replace with yours echo $USER mkdir /home/<user>/backups sudo cp /home/<user>/.celestia-app/config/priv_validator_key.json /home/<user>/backups extract this file, the method I’m using is to copy the contents of the file carefully to an external device, assuming you are accessing the server via a local device change permissions sudo chown USER:USER /home/<user>/backups/priv_validator_key.json Open the file for editing, in order to copy sudo nano /home/<user>/backups/priv_validator_key.json copy the contents carefully to a .txt file locally, to load onto the New server later. NOTE: echo $CELESTIA_WALLET the variable set up in this device build, want to label to same in the next build. (keep CELESTIA_NODENAME consistent too) 2. Start Node & Sync New Server follow the steps for a validator up until Create wallet (Step 7) allow this node to fully sync, use snapshot (Step 5) to do this for a fast migration. 3. Replace the Priv_validator_key.json on New Server Stop the Node, IMPORTANT make sure you stop your node, before replacing the key sudo systemctl stop celestia-appd Open the priv_validator_key.json on the New Device for editing. In order to replace. sudo nano /home/<user>/.celestia-app/config/priv_validator_key.json replace the contents carefully with the old key data 4. Ensure our Old Node is Stopped To avoid slashing with possible double signing, head back to the Old Device and make sure we are shut down sudo systemctl stop celestia-appd confirm sudo systemctl status celestia-appd To be extra safe, having already backed up the important files, delete old wallet celestia-appd keys delete <your old wallet name> --keyring-backend=test celestia-appd keys list should display nothing This device can be shut down, and reinstalled. 5. Recover Wallet on New Server celestia-appd keys add $CELESTIA_WALLET --recover Double check celestia-appd keys list check this is your wallet address, good idea to double check the environment variables and wallet output the same 6. Restart node on New Server we don’t need to create a validator again, simply restart the service. sudo systemctl daemon-reload sudo systemctl start celestia-appd journalctl -u celestia-appd.service -f Upgrading Celestia - PENDING Latest image at time of writing 0.6.0, any updated binaries (see announcements on discord) can be replaced. Making Changes on a Running Node- PENDING should you wish to change any settings such as P2P configuration settings

This is a set up guide for a Validator Node on Celestia’s Mamaki Testnet, this also applies to set up a full node, up until Step 7.

Mamaki test network is deprecated now and replaced with Mocha test network, please see this guide for updated instructions

https://mirror.xyz/0xf3bF9DDbA413825E5DdF92D15b09C2AbD8d190dd/AM4qp-HcHmTDu3rFLVyQVBGlqnSeLElKzrZ_iSoFHW4

First, make sure to update and upgrade the OS:

sudo apt update && sudo apt upgrade -y

Install essential packages for Celestia

These are essential packages that are necessary to execute many tasks like downloading files, compiling and monitoring the node:

sudo apt install curl tar wget clang pkg-config libssl-dev jq build-essential bsdmainutils git make ncdu -y

Firewall Settings

we need to enable firewall and open ports on our device

sudo ufw allow 26657/tcp
sudo ufw allow 26656/tcp          #Port listen for incom TXs, config
sudo ufw allow 9090/tcp
sudo ufw enable

sudo ufw status

IMPORTANT: If you are going to remote into this server, make sure to enable SSH before enabling ufw

Additional Ports

These are additional ports from some additional bootstrap Peers to help with syncing (these additional peers are added later, and can change)

#these ports are to the ones in additional peers, add in the same method as above
16656,57030,41768,52552,43656,50674,41622,2665,41914,36126,41636,49656,47474,54244,44306,38360,57914,37462,37898,37754,5603,39208,49052,36656,26676,26666

Install Golang

remove any existing installation

sudo rm -rf /usr/local/go
sudo rm -rf ~/go

cd $HOME
sudo wget https://golang.org/dl/go1.18.2.linux-amd64.tar.gz
sudo tar -xvf go1.18.2.linux-amd64.tar.gz
sudo rm go1.18.2.linux-amd64.tar.gz
sudo mv go /usr/local

Now we need to add the /usr/local/go/bin directory to $PATH:

mkdir ~/go
echo 'GOROOT=/usr/local/go' >> ~/.bashrc
echo 'GOPATH=~/go' >> ~/.bashrc
echo 'PATH=$PATH:$GOROOT/bin:$GOPATH/bin' >> ~/.bashrc

make changes to the applicable file, should now be persistent in the .bashrc

source .bashrc

Confirm installation

go version

This should Return

go version go1.18.2 linux/amd64

For Celestia Validator Node setup: running a Celestia App daemon with an internal Celestia Core node. https://docs.celestia.org/developers/celestia-app/, the application will be configured as a validator later.

Install Celestia App

create a binary file named celestia-appd inside $HOME/go/bin folder which will be used later to run the node. Check the Discord ‘mamaki testnet’ announcements for the latest version (currently this is v0.6.0)

cd $HOME 
rm -rf celestia-app 
git clone https://github.com/celestiaorg/celestia-app.git 
cd celestia-app 
git checkout v0.6.0 
make install

check if the binary was successfully compiled, will output help example commands

celestia-appd --help

cd $HOME
rm -rf networks
git clone https://github.com/celestiaorg/networks.git

set variables with whatever you want in <> but do not change Network: mamaki

CELESTIA_NODENAME="<YOUR_NODE_NAME>" 
CELESTIA_WALLET="<YOUR_WALLET_NAME>" 
CELESTIA_CHAIN="mamaki"

save the variables

echo 'export CELESTIA_CHAIN='$CELESTIA_CHAIN >> $HOME/.bashrc
echo 'export CELESTIA_NODENAME='${CELESTIA_NODENAME} >> $HOME/.bashrc
echo 'export CELESTIA_WALLET='${CELESTIA_WALLET} >> $HOME/.bashrc
source $HOME/.bashrc

Initialize the application node

celestia-appd init $CELESTIA_NODENAME --chain-id $CELESTIA_CHAIN

Copy the config genesis file

cp $HOME/networks/mamaki/genesis.json $HOME/.celestia-app/config/

Set to validator mode (IF YOU ONLY WANT TO RUN A FULL NODE SKIP THIS LINE)

sed -i 's/mode = \"full\"/mode = \"validator\"/g' $HOME/.celestia-app/config/config.toml

Set up P2P Networks: Bootstrap Peers and Additional Peers

update bootstrap peers

BOOTSTRAP_PEERS=$(curl -sL https://raw.githubusercontent.com/celestiaorg/networks/master/mamaki/bootstrap-peers.txt | tr -d '\n')

check

echo $BOOTSTRAP_PEERS

Set, add to config

sed -i.bak -e "s/^bootstrap-peers *=.*/bootstrap-peers = \"$BOOTSTRAP_PEERS\"/" $HOME/.celestia-app/config/config.toml 

Additional Peers

NOTE: there may be additional bootstrap peers to add to this list to help with connections, check the discord and add to the config.toml

There are additional bootstrap peers that can be added from here

curl -s https://rpc-mamaki.pops.one/net_info | jq -r '.result.peers[] | .url'

Other peers from here

networks/mamaki/peers.txt at master · celestiaorg/networks

Contribute to celestiaorg/networks development by creating an account on GitHub.

https://github.com

to make changes to the config, and paste them in manually

sudo nano $HOME/.celestia-app/config/config.toml

To save time, you can copy from below and place in between the quotes on

bootstrap-peers = “<place here no spaces,to separate>”

Set Consensus Configuration Options

sed -i 's/timeout-commit = ".*/timeout-commit = "25s"/g' $HOME/.celestia-app/config/config.toml
sed -i 's/peer-gossip-sleep-duration *=.*/peer-gossip-sleep-duration = "2ms"/g' $HOME/.celestia-app/config/config.toml

Set P2P Configuration Options

max_num_inbound_peers=40 
max_num_outbound_peers=10 
max_connections=50 

sed -i -e "s/^use-legacy *=.*/use-legacy = false/;\
s/^max-num-inbound-peers *=.*/max-num-inbound-peers = $max_num_inbound_peers/;\
s/^max-num-outbound-peers *=.*/max-num-outbound-peers = $max_num_outbound_peers/;\
s/^max-connections *=.*/max-connections = $max_connections/" $HOME/.celestia-app/config/config.toml

above is the recommended settings since 0.0.6 release, these can be changed manually by

sudo nano $HOME/.celestia-app/config/config.toml

Other things recommended to change- from the 0.5.3 Release use-legacy = false pex = true peer-gossip-sleep-duration=”2ms”

For lower disk space usage, recommend setting up pruning using the configurations below.

pruning_keep_recent="100"
pruning_interval="10"

sed -i -e "s/^pruning *=.*/pruning = \"custom\"/;\
s/^pruning-keep-recent *=.*/pruning-keep-recent = \"$pruning_keep_recent\"/;\
s/^pruning-interval *=.*/pruning-interval = \"$pruning_interval\"/" $HOME/.celestia-app/config/app.toml

for pruning "100-0" you should disable snapshots to avoid conflict with 100-blocks pruning and 1500-blocks snapshot-interval

sed -i 's/snapshot-interval *=.*/snapshot-interval = 0/g' $HOME/.celestia-app/config/app.toml

Reset Before Starting the Node

celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app

Config Client

celestia-appd config chain-id $CELESTIA_CHAIN

creates an application CLI configuration file, needed for wallet later

celestia-appd config keyring-backend test

Syncing from Genesis can take a long time, depending on your hardware. Using this method you can synchronize your Celestia node very quickly by downloading a recent snapshot of the blockchain. If you would like to sync from the Genesis, then you can skip this part.

cd $HOME
rm -rf ~/.celestia-app/data
mkdir -p ~/.celestia-app/data
SNAP_NAME=$(curl -s https://snaps.qubelabs.io/celestia/ | \
    egrep -o ">mamaki.*tar" | tr -d ">")
wget -O - https://snaps.qubelabs.io/celestia/${SNAP_NAME} | tar xf - \
    -C ~/.celestia-app/data/

Takes about 10-15 mins to download

Set up celestia-appd as a background process.

sudo tee <<EOF >/dev/null /etc/systemd/system/celestia-appd.service
[Unit]
Description=celestia-appd Cosmos daemon
After=network-online.target
[Service]
User=$USER
ExecStart=$HOME/go/bin/celestia-appd start
Restart=on-failure
RestartSec=3
LimitNOFILE=4096
[Install]
WantedBy=multi-user.target
EOF

enable and start the process

sudo systemctl enable celestia-appd
sudo systemctl daemon-reload
sudo systemctl start celestia-appd

Confirm its running

systemctl status celestia-appd

Output the Logs

journalctl -u celestia-appd.service -f

To Check for Sync State

curl -s localhost:26657/status | jq .result | jq .sync_info

Allow to sync before continuing

If you need to create a wallet and connect to Mamaki Testnet network

Download Keplr and create wallet

Install Keplr for chrome, and follow the steps to ‘create new wallet’ remember to save your seed phrase.

Connect Keplr to Mamaki Network

https://aviaone.com/celestia-connect-wallet-keplr-testnet-mamaki.html if you have kerplr installed and active, you will be prompted to connect network, allow this

Request Test Tokens from the Faucet

find your address on the Keplr app after selecting the correct network for Celestia (Mamaki), copy your address from Keplr and request from the Celestia discord (LINK) on the ‘faucet’ channel

$request celestia1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Import Wallet

celestia-appd keys add $CELESTIA_WALLET --recover

Enter Seed

save address and valoper address (validator) as variables. The valoper address is the wallets validator address, which appears in different format but derived from the same seed.

CELESTIA_ADDR=$(celestia-appd keys show $CELESTIA_WALLET -a)
echo $CELESTIA_ADDR
echo 'export CELESTIA_ADDR='${CELESTIA_ADDR} >> $HOME/.bashrc

CELESTIA_VALOPER=$(celestia-appd keys show $CELESTIA_WALLET --bech val -a) 
echo $CELESTIA_VALOPER 
echo 'export CELESTIA_VALOPER='${CELESTIA_VALOPER} >> $HOME/.bashrc 
source $HOME/.bashrc

We can get our address by running the command below

celestia-appd keys show $CELESTIA_WALLET

to display wallets in stored within the node

celestia-appd keys list

To Delete old wallets

celestia-appd keys delete OLD_WALLET --keyring-backend=test

Double Check that you are Synced before continuing

curl -s localhost:26657/status | grep block_height

Check Balance, also confirm wallet set correctly

celestia-appd q bank balances $CELESTIA_ADDR

Check Variables

echo $CELESTIA_NODENAME $CELESTIA_CHAIN $CELESTIA_WALLET

Connect Validator

1TIA = 1,000,000 uTIA

celestia-appd tx staking create-validator \
 --amount=1000000utia \
 --pubkey=$(celestia-appd tendermint show-validator) \
 --moniker=$CELESTIA_NODENAME \
 --chain-id=$CELESTIA_CHAIN \
 --commission-rate=0.1 \
 --commission-max-rate=0.2 \
 --commission-max-change-rate=0.01 \
 --min-self-delegation="1" \
 --from=$CELESTIA_WALLET

This is for the first time creating validator, it will output a transaction is successful and you should be able to find in the block explorer to confirm its success.

Problems with this transaction may be a result of your node not being synced properly, double check, there’s additional ways to check sync under ‘Other commands’ section.

Download and save "$HOME/.celestia-app/config/priv_validator_key.json" to your PC!

This is important, to backup and recover your validator should you have a failure on this device. If you don’t know how to do this, there is a part on ‘Migration’ towards the end of this document, which describes the process on backing this up.

check validator

celestia-appd q staking validator $CELESTIA_VALOPER

Output active set

celestia-appd q staking validators --limit=3000 -oj \ | jq -r '.validators[] | select(.status=="BOND_STATUS_BONDED") | [(.tokens|tonumber / pow(10;6)), .description.moniker] | @csv' \ | column -t -s"," | tr -d '"'| sort -k1 -n -r | nl

Edit Avatar

celestia-appd tx staking edit-validator --identity "YOUR_KEYBASE_ID" --from $CELESTIA_WALLET

Change Moniker

celestia-appd tx staking edit-validator --from=$CELESTIA_WALLET --new-moniker <new_moniker_here> --chain-id mamaki --fees 500utia

Delegate to Validator (including your own)

example from docs

celestia-appd tx staking delegate celestiavaloper1q3v5cugc8cdpud87u4zwy0a74uxkk6u43cv6hd <ammount>utia --from=$CELESTIA_WALLET --chain-id=mamaki

Block Explorer

Main Project Information | Celestia (TIA) Blockchain Explorer

Fast, simple and secure blockchain solution to stake your crypto assets and earn yields. Stake with the best validator. High performance. Delivered.

https://celestia.explorers.guru

View Logs Methods

journalctl -u celestia-appd.service -f

journalctl -u celestia-appd -f -o cat

Check Sync Methods

curl -s localhost:26657/status | jq .result | jq .sync_info

curl -s localhost:26657/status | grep block_height

Latest block height: your nodes latest block height this should match the explorer

Max peer block height: the max height of peers you are connected to, should be close to your own if you are connected to peers

Unjail

when your validator misses signing for a period it could end up in ‘jail’ basically you receive a penalty slash and kicked out of the active set, your validator will still be active but not earning rewards or producing blocks, until you manually unjail

celestia-appd tx slashing unjail --from=$CELESTIA_WALLET --chain-id mamaki --fees=4000utia --keyring-backend=test

Should you wish to migrate device to another, for a variety of reasons such as hardware failure/ upgrades or expected downtime. I’ve had to do this recently myself, so I am documenting a process for reference to minimise downtime.

1. Backup Priv_validator_key.json

On the Old Device that you wish to retire Locate priv_validator_key.json it should be in here by default

cd .celestia-app/config
ls -la

copy to a backup folder, double check the username with, replace with yours echo $USER mkdir /home/<user>/backups sudo cp /home/<user>/.celestia-app/config/priv_validator_key.json /home/<user>/backups extract this file, the method I’m using is to copy the contents of the file carefully to an external device, assuming you are accessing the server via a local device change permissions sudo chown USER:USER /home/<user>/backups/priv_validator_key.json Open the file for editing, in order to copy sudo nano /home/<user>/backups/priv_validator_key.json copy the contents carefully to a .txt file locally, to load onto the New server later. NOTE: echo $CELESTIA_WALLET the variable set up in this device build, want to label to same in the next build. (keep CELESTIA_NODENAME consistent too) 2. Start Node & Sync New Server follow the steps for a validator up until Create wallet (Step 7) allow this node to fully sync, use snapshot (Step 5) to do this for a fast migration. 3. Replace the Priv_validator_key.json on New Server Stop the Node, IMPORTANT make sure you stop your node, before replacing the key sudo systemctl stop celestia-appd Open the priv_validator_key.json on the New Device for editing. In order to replace. sudo nano /home/<user>/.celestia-app/config/priv_validator_key.json replace the contents carefully with the old key data 4. Ensure our Old Node is Stopped To avoid slashing with possible double signing, head back to the Old Device and make sure we are shut down sudo systemctl stop celestia-appd confirm sudo systemctl status celestia-appd To be extra safe, having already backed up the important files, delete old wallet celestia-appd keys delete <your old wallet name> --keyring-backend=test celestia-appd keys list should display nothing This device can be shut down, and reinstalled. 5. Recover Wallet on New Server celestia-appd keys add $CELESTIA_WALLET --recover Double check celestia-appd keys list check this is your wallet address, good idea to double check the environment variables and wallet output the same 6. Restart node on New Server we don’t need to create a validator again, simply restart the service. sudo systemctl daemon-reload sudo systemctl start celestia-appd journalctl -u celestia-appd.service -f Upgrading Celestia - PENDING Latest image at time of writing 0.6.0, any updated binaries (see announcements on discord) can be replaced. Making Changes on a Running Node- PENDING should you wish to change any settings such as P2P configuration settings