cd $HOMErm-rfcelestia-nodegitclonehttps://github.com/celestiaorg/celestia-node&&cdcelestia-nodegitcheckouttags/v0.20.2makebuildmakeinstallcelestiaversion#Semantic version: v0.20.2#Commit: b24d47fe29d2b244d501194956412cb7bb60f30f
Don't forget to save the catalog with keys!!!.celestia-light/keys
Update
systemctlstopcelestia-light
cd $HOMErm-rfcelestia-nodegitclonehttps://github.com/celestiaorg/celestia-node&&cdcelestia-nodegitcheckouttags/v0.16.0makebuildmakeinstallmakecel-keycelestiaversion#Semantic version: v0.16.0#Commit: 6744f648649ebb5fee1b27faf7aca96ecf4519b2
For Light nodes there is no concept of double signature and if suddenly there is a need to transfer node ID to a new server, then it does not matter to us whether the old server is working or not available. The main thing is that we have a copy of two files located at /root/.celestia-light-mocha-4/keys/
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 Light
Stop Light on the new server and replace the two files in /root/.celestia-light-mocha-4/keys/
Be sure to give the necessary rights chmod 600 /root/.celestia-light-mocha-4/keys/*
Restart Light on the new server and wait for full synchronization
Stop the old server
Useful commands
Find out Light node id
# first, let's generate an authorization tokenAUTH_TOKEN=$(celestialightauthadmin)echo $AUTH_TOKEN# we get the peerId of our nodecurl-XPOST \-H"Authorization: Bearer $AUTH_TOKEN" \-H'Content-Type: application/json' \-d'{"jsonrpc":"2.0","id":0,"method":"p2p.Info","params":[]}' \http://localhost:26658
# another way to get Node IDcelestiap2pinfo--node.store~/.celestia-light/
Working with wallets
# show wallet addresscel-keylist--node.typelight--keyring-backendtest# check balancecelestiastatebalance--node.store~/.celestia-light/# restore walletcel-keyaddlight_wallet--keyring-backendtest--node.typelight--recover