Devnet-0 launch checklist

1.1 — Operator readiness

• □ Read the Devnet-0 overview and validator runbook
• □ Confirm you can allocate time for upgrades/incidents
• □ Decide who owns this validator (team / individual)
• □ Set up a support / alert email or channel

1.2 — Hardware & hosting

• □ Choose a cloud provider or bare-metal host
• □ Reserve a machine with 4–8 cores, 16–32 GB RAM
• □ Ensure NVMe SSD (1 TB+ preferred)
• □ Confirm bandwidth and latency are acceptable

1.3 — Access & security

• □ Enable SSH key auth; disable password logins
• □ Create a dedicated non-root user for the node
• □ Restrict SSH to your IPs or VPN where possible
• □ Document where keys and credentials live

2.1 — System prep

• □ Update OS packages and security patches
• □ Install core tools (tmux, curl, jq, htop, etc.)
• □ Set timezone to UTC for logs and monitoring
• □ Configure basic firewall (allow p2p/RPC as needed)

2.2 — Quantara node binary

• □ Download the Devnet-0 node binary or Docker image
• □ Verify checksum / signature from release notes
• □ Store the binary in a dedicated directory
• □ Record exact version + git hash in your docs

The release artifacts and spec signing & verification docs will list canonical binaries, hashes, and verification steps.

3.1 — Controller & stash

• □ Generate a controller account for day-to-day actions
• □ Generate a stash account for bonded funds (even on devnet)
• □ Store mnemonics offline in an encrypted password manager
• □ Verify SS58 prefix = 73

3.2 — Session keys

• □ Use the node or tooling to generate session keys
• □ Record keys in a secure internal document
• □ Test sign/verify for at least one key pair
• □ Confirm keys are wired to the correct node

3.3 — Access to QTR (devnet)

• □ Request test QTR via faucet or coordinator
• □ Confirm balances via wallet + explorer
• □ Record the minimum bond / stake requirements
• □ Keep extra QTR for transaction fees and testing

4.1 — First start

• □ Start the node in non-validator mode first
• □ Confirm logs show healthy networking and sync
• □ Compare block height with reference RPC / explorer
• □ Configure as a systemd service for auto-restarts

4.2 — Promote to validator

• □ Submit extrinsics to set session keys
• □ Bond funds and signal intent to validate
• □ Wait for inclusion in the active validator set
• □ Confirm authoring & finality on explorer / logs

5.1 — Metrics & dashboards

• □ Expose Prometheus metrics from the node
• □ Add core panels (height, peers, CPU, RAM, disk)
• □ Visualize block production and finality lag
• □ Save a snapshot URL of your main dashboards

5.2 — Logs

• □ Configure log rotation for node logs
• □ Ship logs to a central sink (optional but ideal)
• □ Tag logs with node/cluster identifiers
• □ Verify you can search incidents by time range

5.3 — Alerts

• □ Set alerts for node down / no blocks / low peers
• □ Set alerts for disk nearing capacity
• □ Route alerts to a channel you actually monitor
• □ Test at least one alert end-to-end

6.1 — Rebuild-from-scratch drill

• □ Pretend you lost the node completely
• □ Provision a fresh machine from your notes
• □ Restore configs, keys, and monitoring
• □ Measure how long full recovery takes

6.2 — Key rotation drill

• □ Rotate session keys using documented steps
• □ Verify new keys are active and old are retired
• □ Update internal docs with new fingerprints
• □ Confirm no alerts are firing post-rotation