The Gonka community is reviewing one of its most ambitious governance proposals yet: an $80,000 Community Pool spend to build Gonka Node Manager, a unified tool for automated node deployment, updates, and monitoring.
The Problem
Running a Gonka node today is a manual process. Experienced operators spend several hours per node on CLI-based installation and configuration. Less experienced participants often need one to two days — or give up entirely. Every software update requires SSH access and server-level changes. There's no built-in monitoring or health visibility.
This friction filters out potential operators. The result: operational power concentrates among a narrow group of technically advanced users, slowing organic decentralization.
What Node Manager Does
The proposed system has three core components:
Control Plane (Web UI + API) — a dashboard where operators manage their nodes, view status, and trigger deployments. No SSH required for day-to-day operations.
Node Agent — a lightweight daemon installed once per host. It manages local Docker Compose stacks and communicates outbound only. The operator's server never opens inbound management ports.
Stack Bundles — verified deployment definitions containing services, ports, health checks, and references to official Gonka images. Updates flow through these bundles automatically.
Key Workflows
- Bootstrap: Add a node in the UI → install agent on server → node is operational
- Updates: Automated via stable release path, no manual intervention
- ML attachment: ML nodes connect to network nodes with automatic firewall rules and connectivity validation
- Warm key management: Keys generated locally on node, only public keys exposed, cold-key signing stays with the operator
Security Model
The design is explicitly non-custodial. The Control Plane never stores SSH credentials or uses SSH to reach nodes. The agent executes only approved, predefined operations — no arbitrary remote commands. Stack bundles are verified before application. Cold keys never leave the operator's control.
Why It Matters
Gonka's Proof of Compute consensus depends on a healthy, diverse set of node operators. Every barrier to entry works against decentralization. Node Manager doesn't change the protocol — it removes the operational overhead that prevents people from participating in it.
The $80,000 budget covers MVP development: deployment automation, basic monitoring, and the warm key workflow. If the governance vote passes, this becomes the first community-funded infrastructure tool in Gonka's history.
The proposal is tracked in GitHub Issue #810.