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.5 KiB

Raw Permalink Blame History

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

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

HIP-0419: Explorer CRD

Abstract

The Explorer CRD is a Service facade for luxfi/explorer, the block explorer UI + API. It reads indexed chain data from a backing Indexer and presents a web UI for blocks, transactions, accounts, and contracts.

Specification

Group + version

hanzo.ai/v1, plural explorers, shortname exp.

Spec fields

Same shape as Service (HIP-400). Conventionally:

image.repository: ghcr.io/luxfi/explorer
two containers in some deployments: API + frontend, or one image serving both
env: INDEXER_URL, RPC_URL

Example CR

apiVersion: hanzo.ai/v1
kind: Explorer
metadata:
  name: hanzo-explorer
  namespace: hanzo
spec:
  image:
    repository: ghcr.io/luxfi/explorer
    tag: 1.2.2
  replicas: 2
  env:
    - name: INDEXER_URL
      value: http://localhost:80
    - name: RPC_URL
      value: https://api.lux.network/mainnet/ext/bc/hanzo/rpc
  ingress:
    enabled: true
    hosts:
      - explore-hanzo.lux.network

Generated K8s resources

Deployment, Service, optional Ingress.

Operator reconciler

~/work/hanzo/operator/src/controllers/service.rs (via Explorer facade).

HIP-418 (Indexer CRD)
HIP-414 (Network CRD)

Status

Implemented in hanzoai/operator v0.3.0+. Primarily deployed on lux-k8s.

1.5 KiB Raw Permalink Blame History