zeekayandHanzo Dev
5eaf0304b0
KEYGEN has been dead on the hanzo-mpc fleet — every request answered 503 "peers not ready" while /healthz reported `signing_quorum: true` beside `ready: false`, and the counters said `ready=5 expected=4` in a THREE node fleet. Both halves of that arithmetic were wrong. SELF WAS COUNTED TWICE. A StatefulSet renders one command for every replica, so the natural spelling hands each node the whole ensemble — including itself. `peerMap[nodeID] = listenAddr` adds self by id, and the matching `--peer` then adds it AGAIN under a synthetic `peer-N` id (an unprefixed address gets a positional id by construction, so it can never match a real node id, and filterSelf — which compares ids — could never see it). Three nodes therefore reported four expected members. mpcd now drops a --peer that names this node, matched by address: equal to --listen, or a host whose FIRST DNS LABEL equals the node id (compared whole, so mpc-node-10 is never mpc-node-1). AND THE GATE WAS AN EQUALITY. `readyCount == len(peers)+1` reads an OVERSHOOT as not-ready, so once the count passed the expected total nothing could bring it back — permanently, across restarts. Signing survived only because it already used >=. A readiness gate must fail closed on too few, never on too many; both sites are >= now, so the double-count could not have wedged keygen even before the fix above. Verified by exercising isSelfAddr over the fleet's real addresses: the live 3-node template on mpc-node-0 keeps 2 peers, expected total 3. Co-authored-by: Hanzo Dev <[email protected]>
mpcd — MPC Daemon
mpcd is a threshold-signature daemon. It speaks ZAP wire protocol over
TLS 1.3 directly between peers — no NATS, no Consul, no PostgreSQL in the
critical path. The daemon is the same binary in every deployment shape;
the operating mode is selected entirely by flags.
Operating modes
There is exactly one start command (mpcd start) and the topology is
determined by the --peer and --threshold flags:
| Topology | Flags | Use |
|---|---|---|
| Standalone (1-of-1 self-loop) | --threshold 1 (no --peer) |
Smoke tests, dev sandbox |
| Networked t-of-n cluster | --threshold t --peer ... (n−1 peers) |
Production |
In all cases mpcd runs the consensus-embedded transport
(pkg/transport). The "consensus" here is local PoA membership over the
node's own Ed25519 identities — it is intentionally not the Lux mainnet
chain, because key shares must never leave the cluster.
Standalone (1-of-1)
mpcd start \
--node-id solo \
--listen :9999 \
--api :9800 \
--data /var/lib/mpcd \
--threshold 1
Starts mpcd with itself as the only quorum member. /healthz will report
signing_quorum: true immediately. Keygen and signing of fresh wallets
require ≥2 parties — CGGMP21 and FROST cannot produce shares with a
single party — so this mode exists only for boot-up smoke tests, e2e
harness fixtures, and verifying TLS / membership / API plumbing. For real
signing, run a multi-node cluster.
Networked (t-of-n)
# Node 0
mpcd start --node-id node0 --listen :9999 --api :9800 \
--data /data/node0 --threshold 2 \
--peer [email protected]:9999 --peer [email protected]:9999
# Node 1
mpcd start --node-id node1 --listen :9999 --api :9800 \
--data /data/node1 --threshold 2 \
--peer [email protected]:9999 --peer [email protected]:9999
# Node 2 — same pattern
The daemon expects the cluster size n = len(peers) + 1 and rejects start
when threshold > n. See pkg/transport/registry.go::HasSigningQuorum for
the quorum arithmetic.
Smoke test
go test -tags=integration ./cmd/mpcd/... -count=1 -timeout 90s
standalone_test.go builds mpcd, runs it with --threshold 1 on free
ports and a fresh data directory, polls /healthz until quorum holds,
and asserts the response shape. It does not exercise keygen — see e2e/
for that.