Current upgrade status
| Item | Current documented value |
|---|---|
| Upgrade module | Present |
| Active genesis upgrade plan | None documented |
| Existing app upgrade handler | v0.5.0-to-v0.6.0 |
| Plan query | ctmd query upgrade plan |
Release-specific runbook
| Phase | Operator action |
|---|---|
| Announcement | Record the upgrade name, target height, binary version, checksums or signatures, and deadline from the official release notice. |
| Preparation | Back up configs and keys, confirm disk headroom, check service health, and download the release binary. |
| Verification | Verify binary checksums or signatures when provided, then confirm ctmd version and ctmd version --long. |
| Execution | Follow the release-specific stop height, binary replacement, config migration, and restart instructions. |
| Post-upgrade | Confirm height progression, peer count, logs, RPC health, and application version. |
| Rollback | Roll back only when the release instructions say it is allowed for the observed failure mode. |
Operator reminders
- Take backups before replacing binaries or changing configs.
- Verify binary checksums or signatures when provided.
- Watch logs and peer health through the upgrade window.
- Coordinate validator-specific steps separately from full-node steps.
- Do not use
--unsafe-skip-upgradesexcept under explicit emergency coordination. - Security reports go to
[email protected]; do not open public issues for vulnerabilities.