π₯οΈFull node (Shwap)
In this guide, we install the Full node on a separate server and use data from Consensus Full Node!
Server preparation
apt update && apt upgrade -yapt install curl build-essential git wget jq make gcc tmux htop nvme-cli pkg-config libssl-dev libleveldb-dev tar clang bsdmainutils ncdu unzip libleveldb-dev lz4 -yInstall GO
ver="1.23.1" && \
wget "https://golang.org/dl/go$ver.linux-amd64.tar.gz" && \
sudo rm -rf /usr/local/go && \
sudo tar -C /usr/local -xzf "go$ver.linux-amd64.tar.gz" && \
rm "go$ver.linux-amd64.tar.gz" && \
echo "export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin" >> $HOME/.bash_profile && \
source $HOME/.bash_profile && \
go versionufw allow 2121 comment full_nodeIMPORTANT - you must use XFS file system. Please do not use ext4, but migrate to XFS/ZFS
Node installation
cd $HOME
rm -rf celestia-node
git clone https://github.com/celestiaorg/celestia-node && cd celestia-node
git checkout tags/v0.21.9
make build
make install
celestia version
#Semantic version: v0.21.9
#Commit: 3d8fb74bc073fb23303dcfc2804ab85ce316fa24Initializing the full
--core.ip use the address of our remote RPC node
--p2p.network use the chain id of our network
--core.port use the gRPC port from our RPC node
--keyring.keyname use the name of the wallet we created
Create a service file
Don't forget to save the catalog with keys!!! .celestia-full/keys
Update
Node transfer
Please note that we do not necessarily need to change the keyring-test wallet Let's look at the most suitable option for saving the Node ID, assuming that the old server is working:
Start a new server and fully sync the Full
Stop Full on the new server and replace the two files in
/root/.celestia-full-mocha-4/keys/Be sure to give the necessary rights
chmod 600 /root/.celestia-full-mocha-4/keys/*Restart Full on the new server and wait for full synchronization
Stop the old server
Useful commands
Find out Full node id
Working with wallets
Status
Delete
Last updated