Celestia Node Upgrade Guide

Upgrading your Celestia node involves stopping the service, rebuilding the celestia-appd binary from the official source, and restarting the process. Following this sequence ensures that the local database remains compatible with the application version.

Prerequisites

Before proceeding with the upgrade, ensure your environment meets the following criteria:

• The go toolchain is installed and updated to the version required by the release.
• You have sudo privileges to manage the systemd service.
• The node is currently healthy and synchronized with the network.

Upgrade Procedure

1. Stop the Node Service

To prevent data corruption during the binary replacement, stop the running celestia-appd process.

sudo systemctl stop celestia-appd

2. Rebuild the Binary

Remove the existing source directory to ensure a clean build environment, then fetch the specified tag from the official repository.

cd $HOME
rm -rf celestia-app
git clone https://github.com/celestiaorg/celestia-app.git
cd celestia-app
# Replace v1.11.0 with the target version if different
git checkout tags/v1.11.0 -b v1.11.0
make install

3. Verify Version

Confirm the installation was successful and the binary is in your PATH by checking the version output.

celestia-appd version

4. Restart and Monitor

Restart the service and monitor the logs to ensure the node resumes block production or synchronization without errors.

sudo systemctl restart celestia-appd && sudo journalctl -u celestia-appd -f -o cat

Post-Upgrade Verification

After the service has restarted, verify that the node is successfully connected to peers and not stuck on a specific height.

Check	Command
Sync Status	`celestia-appd status 2>&1
Latest Block	`celestia-appd status 2>&1
Peer Count	`curl -s localhost:26657/net_info

Warning: If the node fails to start with “AppHash mismatch” or “Panic,” verify that you have checked out the correct tag required by the current network height.