mirror of https://github.com/hanzoai/hips.git synced 2026-11-03 00:32:50 +00:00

Files

T

zeekayandHanzo Dev 7a9dcac628 What each runtime implements of the Hanzo corpus

An audit read the code and found the proposal that specifies it. Go reaches
all 122 capability proposals and 64 of the 121 other Standards Track ones;
Rust has 35, mostly the operator and the CLI; C++ has three, because the
complete original C++ in the estate is a ZAP handler, a bot nothing specifies,
and authored kernels inside forked CUDA and Metal crates.

    | | shipped | partial | none | not assessed |
    | Go   | 146 | 33 | 1 |  80 |
    | C++  |   1 |  2 | 0 | 257 |
    | Rust |  10 | 25 | 1 | 224 |

The large "not assessed" columns are the point rather than a gap. The model and
training specs are Python, the frontend and design-system proposals are
TypeScript, and recording `none` against those would read as a search that
came up empty when the honest statement is that the runtime was never the
question. Governance, Meta and Process are not graded at all.

Six proposals are Final with nothing found in Go and are left unwritten rather
than demoted: 0065, 0089, 0098, 0103, 0521 and 0902. HIP-0521 answers itself,
its own section reading "Not yet implemented". Three of the others name a
canonical Go file in consensus/protocol/auth that nobody wrote, in a package
where the four neighbouring proposals' files all exist with tests beside them.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-05 19:18:13 -07:00

1.9 KiB

Raw Permalink Blame History

hip, title, author, type, category, status, implementation-rust, created

hip	title	author	type	category	status	implementation-rust	created
0413	MPC CRD	Hanzo Platform Team	Standards Track	Operator	Final	partial	2026-05-19

HIP-0413: MPC CRD

Abstract

The MPC CRD describes a Multi-Party Computation cluster (luxfi/mpc). It runs an n-of-m threshold signing network for cross-chain wallets and operator-controlled keys. The reconciler emits a StatefulSet of replicas peers and a headless Service for peer discovery; optionally adds a dashboard Deployment and a cache Deployment.

Specification

Group + version

hanzo.ai/v1, plural mpcs, shortname hmpc.

Spec fields

Field	Type	Description
`image`	ImageSpec	`luxfi/mpc` (or hanzo-vendored equivalent)
`replicas`	int	total peers (n)
`threshold`	int	signing threshold (m, where m ≤ n)
`p2pPort`	int	peer-to-peer port
`apiPort`	int	API port
`resources`	ResourceRequirements	requests/limits
`dashboard`	MPCDashboardSpec	optional dashboard Deployment
`cache`	MPCCacheSpec	optional cache Deployment
`ingress`	IngressSpec	optional Ingress

Example CR

apiVersion: hanzo.ai/v1
kind: MPC
metadata:
  name: hanzo-mpc
  namespace: hanzo
spec:
  image:
    repository: ghcr.io/hanzoai/mpc
    tag: 1.2.9
  replicas: 5
  threshold: 3
  p2pPort: 7000
  apiPort: 8080
  dashboard:
    enabled: true
    image: ghcr.io/luxfi/mpc-dashboard:1.1.3

Generated K8s resources

StatefulSet (peer cluster)
Headless Service (peer discovery)
ClusterIP Service (API)
Optional Dashboard Deployment + Service
Optional Cache Deployment + Service

Operator reconciler

~/work/hanzo/operator/src/controllers/mpc.rs.

HIP-0084 (Pulsar M-DKG)

Status

Implemented in hanzoai/operator v0.3.0+. CR hanzo-mpc active with 5 replicas, threshold 3.

1.9 KiB Raw Permalink Blame History