Skip to main content

​
celestia-node (DA) upgrade

1

Stop node & fetch latest release

# Stop your service (example name)
sudo systemctl stop celestia-light || true
sudo systemctl stop celestia-full || true
sudo systemctl stop celestia-bridge || true

# Update from source
cd $HOME/celestia-node || { cd $HOME; rm -rf celestia-node; git clone https://github.com/celestiaorg/celestia-node.git; cd celestia-node; }
git fetch --all --tags
git checkout $(git describe --tags --abbrev=0)
make node-install

celestia version
2

Restart & verify

sudo systemctl start celestia-light || true
sudo systemctl start celestia-full || true
sudo systemctl start celestia-bridge || true

journalctl -u celestia-light -f -o cat || true

​
celestia-app (consensus) upgrade with Cosmovisor

1

Install/verify Cosmovisor

# As per Cosmos SDK tooling (see official docs)
go install cosmossdk.io/tools/cosmovisor/cmd/cosmovisor@v1.6.0
cosmovisor version
2

Prepare the new binary

# Build or download new celestia-appd and place under the target upgrade dir
# Example layout:
mkdir -p $HOME/.celestia-app/cosmovisor/upgrades/<UPGRADE_NAME>/bin
cp $(which celestia-appd) $HOME/.celestia-app/cosmovisor/upgrades/<UPGRADE_NAME>/bin/
3

Schedule the upgrade

Use your chain’s governance proposal (if applicable) or the advised block height/time from Celestia release notes. Cosmovisor will switch binaries automatically when the upgrade triggers.
4

Monitor & rollback plan

journalctl -u cosmovisor -f -o cat
# If needed, stop services and revert to the previous binary placed under `genesis/bin`.
Always confirm the target version / upgrade height from the official release notes and the network announcements before scheduling upgrades.