Documentation · Releases · Prometheus

Prometheus

v0.7.10 — Prometheus

What landed

• Tunnelee + Tunneler dual-role: hub-driven SSH/frp tunneling lets a CGNAT-bound home box host a fully-peering chainweb node via a small public Tunneler VPS.
• Hierarchical node groupings — Tunnelees nest under their parent Tunneler in /hub/nodes, with category permissions and a node-type legend that match the new ontology.
• Install-wizard rehaul: topology-aware checks, host fingerprinting, HDD-exclusion gate, drive-benchmark fresh-confirm, segregated-container prep, and locked mandatory flags.
• Server-wide DNS hostnames promoted to a first-class node attribute, with Let’s Encrypt cert issuance and inheritance flowing end-to-end through install + convert.
• Per-node terminal tab, in-app confirm modals, and the Tunnelee enrollment one-liner — operator UX caught up with the new architecture.
• Library + bootstrap upgrades: NOPASSWD-aware bootstrap, sudoers self-repair, and a port-leak fix that landed alongside the renew button on the Tunneler side.

Operator notes

Prometheus is the wave that made the home operator a first-class StoaChain peer. Most prospective operators live behind CGNAT — Telekom fibre, mobile broadband, double-NAT residential — and cannot accept inbound connections directly. The Tunnelee/Tunneler split solves that by pairing a small public-IP VPS (the Tunneler, running frps + an SSH endpoint) with the operator's home box (the Tunnelee), so chainweb peering, RPC traffic, and Stoicism scoring all flow through a stable public endpoint while the actual node runs on the operator's hardware. The wave also rebuilt the install wizard around topology-aware checks, started the segregated-container groundwork that Medusa later finished, and promoted server-wide DNS hostnames to a first-class node attribute. Net effect: a laptop, a home server, or a Raspberry Pi can now participate in StoaChain on equal economic footing with a datacenter VPS.

Patch log