Files
mpc/Dockerfile
zeekayandHanzo Dev bbdfb8fc9f build via platform.hanzo.ai; wrap luxfi/mpc v1.17.15
Two things, both about this image tracking the thing it wraps.

1. Base bump v1.17.12 -> v1.17.15. This image's contract is that its version
   MIRRORS the upstream (hanzoai/mpc:X == luxfi/mpc:X), and all four MPC quorums
   — lux-bridge, lux-mpc, bridge-mpc, hanzo-mpc — now run v1.17.15. The wrapper
   was two patches behind the ring it wraps. v1.17.15 adds threshold +
   participants to the keygen response so a caller can VERIFY the t-of-n it
   asked for; v1.17.14 stopped pkg/threshold mutating the global scheme registry
   at import. LLM.md (AGENTS.md and CLAUDE.md symlink to it) updated in step.

2. GHA -> platform. The last image this repo published was 2026-07-15, and only
   from a hand-run workflow_dispatch: pushes do nothing, because Actions is
   disabled at the account level and GitHub answers a dispatch with 422 "Actions
   has been disabled for this user". Same migration as luxfi/kms (efed0f0) and
   luxfi/operator (1ba4349) — delete the workflows, declare the build in
   hanzo.yml, let platform run an in-cluster BuildKit Job on our own runners.

tag-pattern is {{git.tag}}, not {{git.branch}}: a `:main` tag cannot express
"mirrors upstream vX.Y.Z", and the hanzo-mpc StatefulSet pins an exact version.
Branch pushes publish nothing, which is right for a wrapper — it has nothing to
say between releases. Needs platform >= hanzoai/platform fdaf99a65, which added
{{git.tag}}; until that is rolled out, tag pushes here produce no image.

No deploy block: hanzo-mpc is a StatefulSet with no operator CR, so the deploy
leg has no .spec.image to patch. Rolling a threshold-signing quorum stays an
explicit, ordered step.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-25 23:42:45 -07:00

24 lines
1.3 KiB
Docker

# syntax=docker/dockerfile:1
#
# Hanzo MPC — sovereign wrapper over the canonical luxfi/mpc binary.
#
# Sovereign version tag MIRRORS the wrapped upstream: hanzoai/mpc:1.17.15 ==
# luxfi/mpc:1.17.15, which carries the CGGMP21 keygen-degree fix (luxfi/mpc
# 1e1d318): runNodeConsensus now wires --threshold into viper "mpc_threshold"
# so the keygen polynomial degree = threshold-1. hanzo-mpc runs --threshold=2 →
# degree 1 → genuine 2-of-3 (was degree 0 = 1-of-3: any single node could sign).
#
# Why wrap instead of source-build: luxfi/mpc is a PRIVATE repo, so the previous
# `git clone github.com/luxfi/mpc` build step cannot authenticate in the ARC
# buildkit sandbox. The pre-built image lives in GHCR (CI has pull access), and
# is the exact binary proven live on zoo-mpc (5/5). The Hanzo deployment drives
# explicit flags (--node-id/--listen/--api/--data/--threshold/--peer), so the
# upstream binary's compile-time defaults are overridden at runtime; org identity
# is runtime (keygen org_id=hanzo). Patch-pin only, never :latest.
#
# The in-repo cmd/mpcd source (Hanzo-branded mirror of luxfi cmd/mpcd, incl. the
# same threshold fix) is retained for local dev / parity; it is NOT what ships.
FROM ghcr.io/luxfi/mpc:v1.17.15
LABEL org.opencontainers.image.source="https://github.com/hanzoai/mpc"
ENV MPC_ORG=hanzo