Files
hips/HIPs/hip-0418-indexer-crd.md
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

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

HIP-0418: Indexer CRD

Abstract

The Indexer CRD is a Service facade for luxfi/indexer, the chain-data indexer that builds queryable SQL tables from raw EVM blocks. Used in combination with Explorer (HIP-419) to power block-explorer UIs.

Specification

Group + version

hanzo.ai/v1, plural indexers, shortname idx.

Spec fields

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

  • image.repository: ghcr.io/luxfi/indexer
  • env: RPC_URL, DATABASE_URL, CHAIN_ID
  • backing store: SQL CR

Example CR

apiVersion: hanzo.ai/v1
kind: Indexer
metadata:
  name: hanzo-indexer
  namespace: hanzo
spec:
  image:
    repository: ghcr.io/luxfi/indexer
    tag: v1.2.2
  replicas: 1
  env:
    - name: RPC_URL
      value: https://api.lux.network/mainnet/ext/bc/hanzo/rpc
    - name: DATABASE_URL
      valueFrom:
        secretKeyRef: { name: indexer-db, key: url }
    - name: CHAIN_ID
      value: "36963"

Generated K8s resources

Deployment, Service. Long-running indexer pod processes new blocks into SQL.

Operator reconciler

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

  • HIP-419 (Explorer CRD)
  • HIP-414 (Network CRD)

Status

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