Celestia
Celestia Data Availability node monitoring
It embedded bot credentials, trusted unverified heights and installed a permanent service without safe update or recovery. It is not published as executable automation.
Use supported Celestia telemetry first. Any BonyNode adapter must protect secrets, verify chain identity, bound requests and distinguish unavailable data from a healthy zero.
Official Celestia node documentation
Node type
Read-only diagnostics
These checks do not install, initialize, restart, upgrade or delete services or nodes.
NODE_SERVICE="celestia-bridge"
MONITOR_SERVICE="monitoring-bridge"
NODE_STORE="$HOME/.celestia-bridge-mocha-4"
command -v celestia >/dev/null || { echo "celestia binary is not installed" >&2; exit 1; }
celestia version
sudo systemctl status "$NODE_SERVICE" --no-pager || true
sudo systemctl status "$MONITOR_SERVICE" --no-pager || true
sudo journalctl -u "$MONITOR_SERVICE" -n 100 --no-pager
celestia header sync-state --node.store "$NODE_STORE"Required contract before automation can return
- Release/network compatibility; verified network identity; bounded numeric heights and balances; protected API tokens; explicit timeouts, retries and health checks.
Reversible decommission
This stops scheduling without deleting the script, secrets, state or unit files.
set -euo pipefail
SERVICE="monitoring-bridge"
UNIT="/etc/systemd/system/$SERVICE.service"
SCRIPT="$HOME/$SERVICE.sh"
sudo systemctl stop "$SERVICE"
sudo systemctl disable "$SERVICE"
sudo systemctl daemon-reload
echo "Monitoring is stopped and disabled. Nothing was deleted."
echo "Retained unit: $UNIT"
echo "Retained script: $SCRIPT"
echo "After review, restore with: sudo systemctl enable --now $SERVICE"