v0.8.0

Full Changelog: v0.7.3...v0.8.0

v0.7.3 — peers update hotfix

Fixes

• monarch peers update: now reads the persistent_peers field from the registry. Previously it reported 0 persistent peers configured even when the registry had them, leaving new nodes unable to find peers when seed nodes were offline.

For existing testnet operators

If you're on v0.7.2 and stuck at 0 peers:

monarch stop
# upgrade monarch (amd64 example)
curl -L https://github.com/monolythium/monarch-cli/releases/download/v0.7.3/monarch-linux-amd64 -o ~/.local/bin/monarch && chmod +x ~/.local/bin/monarch
monarch peers update --network testnet
monarch start

Testnet peers registry was also updated (mono-core-peers@73fe97b) — the three previous seed nodes were offline; four live validators now serve as seeds.

v0.7.2

Transaction Failure Detection + Unjail Pre-checks

Tx failure detection:

• All transaction commands now check the on-chain result code
• Failed transactions show red FAILED with the actual error reason instead of a misleading success checkmark

Before: ✓ Transaction submitted     ← tx actually failed, operator doesn't know
After:  ✗ Transaction FAILED (code 7)
        Reason: validator's self delegation less than minimum; cannot be unjailed

Unjail pre-checks:

• Queries validator status before submitting — shows jailed state, self-delegation, and minimum bond
• Warns if self-delegation is below minimum instead of letting the tx fail silently

Key auto-detect:

• monarch validator unjail (and other tx commands) auto-detects the account key from keyring
• Asks keyring password once, reuses for both key lookup and transaction

Full Changelog: v0.7.1...v0.7.2

v0.7.1

Stall Detection

• monarch status detects stalled nodes — when catching up but last block >10min old, shows red STALLED warning with restart hint
• Sync percentage always shown — chain tip fetched from local consensus state (no external DNS dependency)

v0.7.0

Multi-Chain Support

Monarch CLI now supports managing nodes for multiple Cosmos SDK chains via a remote chain registry.

New features:

• --experimental flag — enables experimental chains (Cosmos Hub)
• --chain flag — select which chain to operate on (default: Monolythium)
• Remote chain registry — chain/network definitions fetched from monolythium/chain-registry, cached locally
• Generic binary install — auto-downloads chain binaries (gaiad, monod, etc.) from GitHub releases, supports both raw binaries and tar.gz archives
• monarch validator resign — safely unbond self-delegation and leave the active set

Improvements:

• monarch join auto-installs both monod AND oxidepm when missing
• monarch install detects outdated monod and upgrades instead of skipping
• Gzip genesis auto-decompression (needed for Cosmos Hub mainnet)
• minimum-gas-prices set automatically from chain registry
• State sync auto-configured when available (needed for Cosmos Hub)
• EVM chain ID only set for EVM-enabled chains
• Pre-release fallback when no stable GitHub release exists

Usage

# Monolythium (unchanged — no flags needed)
monarch join --network Testnet

# Cosmos Hub (experimental)
monarch join --chain "Cosmos Hub" --network Testnet --experimental

Breaking Changes

None. All existing Monolythium commands work identically.

Full Changelog: v0.6.4...v0.7.0

v0.6.4

Fixes

• Auto-install monod: monarch join and monarch init now detect a missing monod binary and install it automatically instead of failing
• Pre-release fallback: monarch install now finds pre-release versions when no stable release exists on GitHub

v0.6.3

Changes

• Validator sync gate: monarch validator register and monarch validator setup now check the node's sync status before allowing registration. If the node is still catching up or offline, registration is blocked with a clear error message. This prevents validators from getting jailed immediately after registering with an unsynced node.

Upgrade

monarch upgrade self

What's Changed

• feat: add Monarch Connect integration section to AI safety runbook by @NayiemW in #13
• merge dev into prod — AI safety runbook update by @NayiemW in #14

New Contributors

• @NayiemW made their first contribution in #13

Full Changelog: v0.6.2...v0.6.3

v0.6.2 — Safe validator key export/import

Fixes

Prevents the jailing scenario where monarch keys validator export → monarch start silently generates a wrong consensus key, causing missed blocks and slashing.

Import improvements

• Auto-backs up existing key instead of failing with "already exists"
• Detects identical key on double-import (skips unnecessary backup)
• Deletes .exported marker after successful restore
• Restores cosmos_mode from relay → validator in ecosystem.config.toml
• Verbose output for every step

Export improvements

• Detailed warnings about not starting without the key
• Clear instructions for both migration and same-server restore

Start safety check

• Detects .exported marker when no active key is present
• Prompts before starting with a wrong key — explains the risk
• Auto-cleans marker when active key already exists (after successful import)

Upgrade

monarch upgrade self
# or
curl -fsSL https://github.com/monolythium/monarch-cli/releases/download/v0.6.2/monarch-linux-amd64 -o ~/.local/bin/monarch && chmod +x ~/.local/bin/monarch

Full Changelog: v0.6.1...v0.6.2

v0.6.1 — Collector fallback fixes

Fixes

• Validator data from RPC: When the REST API (port 1317) is not enabled, the metrics collector now reads voting_power and block time directly from the RPC /status endpoint. Validators are correctly detected as BONDED without needing the LCD.

• Process stats without OxidePM: When the node runs via systemd or directly (not managed by OxidePM), the collector now uses pgrep + ps to get CPU%, memory usage, and uptime from the OS.

Upgrade

curl -fsSL https://github.com/monolythium/monarch-cli/releases/download/v0.6.1/monarch-linux-amd64 -o ~/.local/bin/monarch && chmod +x ~/.local/bin/monarch

Or via Monarch Connect: Setup → Tools → Upgrade button.

Full Changelog: v0.6.0...v0.6.1

v0.6.0 — Advanced Metrics Collection

What's New

monarch metrics — Advanced Metrics Collection

Time-series node monitoring with historical data and event detection.

Commands:

• monarch metrics enable — Guided setup with cron job + optional static file export
• monarch metrics collect — Collects 24 metrics every 60 seconds (height, peers, CPU/mem, disk, validator rank, tokens, missed blocks, delegators, rewards)
• monarch metrics query --since <ts> --json — Returns snapshots for Monarch Connect charts
• monarch metrics events --since <ts> --json — Detected events (jailing, rank changes, delegator changes, disk warnings, stale blocks, etc.)
• monarch metrics status — Show collection status and file sizes
• monarch metrics disable — Clean teardown

Event Detection (14 event types):
Jailed, unjailed, status changed, stale blocks, catching up, synced, high missed blocks, rank changed, tokens changed, delegator joined/left, process restarted, disk warning, disk critical.

Storage: ~42 KB/day, auto-rotated at 5 MB (keeps 7 days).

monarch logs-configure — Log Rotation Control

Configure OxidePM log rotation via CLI:

monarch logs-configure --max-size 100mb --max-files 10 --compress
monarch logs-configure --show

Optional: Static File Export

Export public validator metrics to JSON files for third-party tools:

monarch metrics enable  # choose option 2 during setup

Writes status.json, history.json, events.json — only on-chain public data, no server resources or IPs.

Upgrade

monarch upgrade self

Full Changelog: v0.5.0...v0.6.0