Releases: monolythium/monarch-cli
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
v0.7.0
Multi-Chain Support
Monarch CLI now supports managing nodes for multiple Cosmos SDK chains via a remote chain registry.
New features:
--experimentalflag — enables experimental chains (Cosmos Hub)--chainflag — 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 joinauto-installs both monod AND oxidepm when missingmonarch installdetects outdated monod and upgrades instead of skipping- Gzip genesis auto-decompression (needed for Cosmos Hub mainnet)
minimum-gas-pricesset 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 --experimentalBreaking Changes
None. All existing Monolythium commands work identically.
Full Changelog: v0.6.4...v0.7.0
v0.6.4
v0.6.3
Changes
- Validator sync gate:
monarch validator registerandmonarch validator setupnow 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 selfWhat'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
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
.exportedmarker after successful restore - Restores
cosmos_modefromrelay→validatorinecosystem.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
.exportedmarker 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/monarchFull 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_powerand block time directly from the RPC/statusendpoint. Validators are correctly detected asBONDEDwithout needing the LCD. -
Process stats without OxidePM: When the node runs via systemd or directly (not managed by OxidePM), the collector now uses
pgrep+psto 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/monarchOr 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 exportmonarch 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 chartsmonarch 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 sizesmonarch 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 selfFull Changelog: v0.5.0...v0.6.0
v0.5.0
What's New
Human-Readable Validator Info
- Tokens:
100000000000000000000000→100,000 LYTH - Commission:
0.100000000000000000��10%
New Command: monarch init
One-time node initialization. Refuses to run on already-initialized nodes unless --force is used. With --force, requires typing "destroy" to confirm — prevents accidental key destruction.
monarch start — Clean Separation
start now ONLY starts the process. Zero key manipulation, zero initialization, zero file modifications. If the node isn't set up, it tells you to run monarch join.
Validator Status Fix
Fixed validator lookup that was comparing operator addresses against consensus addresses (could never match). Now matches by consensus pubkey with bech32 signing_infos query for missed blocks.
Key Import Fix
monarch keys validator import now prompts for the file path interactively when called without args.
Boot Persistence — User Services
enable-boot / disable-boot auto-detect root/sudo access. Falls back to user-level systemd services via loginctl enable-linger — no sudo needed.
Operator Safety Notes
Every dangerous command now has explicit warnings with safety levels (SAFE/CAREFUL/DANGER).
Module Path
Updated from mono-experimental/monarch to monolythium/monarch-cli.
Full Changelog
Full Changelog: v0.4.1...v0.5.0
v0.4.1
What's New
Validator Setup UX
- Post-registration flow now asks before each action (start, save, boot persistence) instead of doing it automatically
- Missing blocks / jailing warning before starting validator process
- Balance check before registration
- Detailed explanations for every prompt (commission rate, self-bond, keyring password)
- Backup status check with offer to create if missing
Cosmos SDK v0.53 Compatibility
monod cometinstead ofmonod tendermintregister-validatorwith burn + create-validator JSON- Removed
--gas-pricesconflict with executor--fees
Other
- "Getting Started" section at top of interactive menu (
monarch first-time,monarch help) - Module renamed from
mono-experimental/monarchtomonolythium/monarch-cli - Clean tx output (hash + Monoscan URL only, no raw YAML)
- Auto-detect network from genesis for Monoscan URLs
monarch first-timeonboarding guide for new operators