What: Meeting to Discuss Improving Node Operations
When: 17 June 2025 @ 7PM CEST
Where: https://element.zenon.chat/#/room/#sig-operations:hc1.chat
Agenda & Notes: Below
Ansible for Node Operations - GitHub - hypercore-one/orchestrator-ansible-deployment
Deployment Script - GitHub - coinselor/deployment
- Interactive TUI via gum
- Deploy – build a node from source
- Backup & Restore – Manually backup and restore the node, or schedule automatic backups.
- Service Control – Start, stop, and restart the node.
- Resync Node – Resynchronize the node from genesis.
- Analytics - Graphical dashboards for monitoring node performance and health via Grafana
Nostr Qube Manager - GitHub - hypercore-one/qube-manager
qube-manager acts as a decentralized action orchestrator using Nostr relays for communication and voting, enabling coordinated upgrades or reboots across a set of nodes by consensus.
- Configuration and Initialization: On startup, the program loads or creates a configuration file containing a list of Nostr relay URLs, public keys to follow, and a quorum value (the minimum number of votes required to act). It also manages cryptographic keys for signing and identifying itself.
- Connecting to Nostr Relays: The manager connects to each configured relay and subscribes to events from followed public keys. It’s specifically interested in messages of type
"upgrade"or"reboot". - Event Collection and Voting: As events are received, the program parses their content to determine the action type and version, and tallies which public keys have “voted” for each candidate action. Actions are keyed by their semantic version and (for reboots) a genesis URL.
- Selecting and Executing Actions: The program picks the latest versioned action that:
- Has not already been processed (history is tracked via a local file)
- Meets the configured quorum of votesIf an eligible action is found, the manager creates a “done” event, signs it with its private key, and publishes it to all relays.
- CLI Mode: There is also a CLI mode (
send-message) that allows an operator to manually send an upgrade or reboot message to the relays. - Logging and Persistence: All actions, history, and logs are stored locally. The manager supports both regular and verbose logging.