Skip to main content
This page covers the operational lifecycle of a Quantum Chain node after it’s installed.

Startup

A typical systemd unit:

Health and readiness

Quantum Chain exposes the standard geth health endpoints: A simple liveness probe:

Metrics

Enable Prometheus-compatible metrics with:
Key metrics:

Logs

Logs are structured. Increase verbosity with:
Or per-module via --vmodule consensus=4,p2p=3.

Sync states

Backups

Snap and full sync nodes are stateless — you can wipe and resync. Archive nodes hold irreplaceable historical state; back them up with:
For online backups without stopping the node, use a copy-on-write filesystem (ZFS, btrfs).

Upgrades

Quantum Chain releases ship as tagged commits in this repository.
  1. Read the release notes for hard-fork activation blocks.
  2. Build the new binary on a staging node.
  3. Update validators within the upgrade window — sealers running an outdated binary after the fork height will produce blocks rejected by the network.
  4. Roll RPC nodes after validators.

Pruning

To reclaim disk on a --gcmode full node:
prune-state rewrites the trie and may take several hours.

Where to go next