posthuman - nodes
Celestia
Celestia websiteCelestia githubCelestia twitterCelestia discord

Celestia

type:
mainnet
chain id:
celestia
rpc:
https://rpc.celestia-mainnet.posthuman.digital
rest:
https://rest.celestia-mainnet.posthuman.digital
grpc:
https://grpc.celestia-mainnet.posthuman.digital
peer:
cd9f852141cd6f78e9443cea389911a6f0a5df72@8.52.247.252:26656
  • installation guide
  • state sync
  • bridge node setup
  • full node setup
  • light node setup
  • snapshots
  • one liner
  • contributions

šŸš€ Restore Celestia Node from Posthuman Snapshots

This guide explains how to restore your Celestia node using a snapshot from Posthuman.


šŸ›‘ Step 1: Stop Celestia Node

Before restoring, stop the Celestia process to prevent database corruption:

sudo systemctl stop celestia-appd

šŸ“Œ Step 2: Backup Validator State (IMPORTANT)

To avoid double signing issues, backup your validator state file:

cp $HOME/.celestia-app/data/priv_validator_state.json $HOME/.celestia-app/priv_validator_state.json.backup

šŸ—‘ Step 3: Remove Old Blockchain Data

Delete the old data to free space and prevent conflicts:

rm -rf $HOME/.celestia-app/data

šŸ“„ Step 4: Download & Extract the Latest Posthuman Snapshot

Note: Since Posthuman updates snapshots every 24 hours, use the latest one:

curl -L https://snapshots.celestia.posthuman.digital/data_latest.lz4 | lz4 -dc - | tar -xf - -C $HOME/.celestia-app

šŸ“‚ Step 5: Restore Validator State

Move back the backup validator state file:

mv $HOME/.celestia-app/priv_validator_state.json.backup $HOME/.celestia-app/data/priv_validator_state.json

ā–¶ļø Step 6: Restart Celestia Node & Monitor Logs

Now, restart the service and monitor its logs:

sudo systemctl restart celestia-appd sudo journalctl -u celestia-appd -fo cat

āœ… Done!

Your node should now sync from the restored Posthuman snapshot. šŸš€

POSTHUMAN Ā© Copyright 2025. All Rights Reserved.