zeekayandHanzo Dev 7783b86136 configs: drop pqcryptoConfig, which no node has ever dispatched
Zoo mainnet and testnet activated pqcryptoConfig. No precompile registers that
key - not in the suite, not in the EVM - and luxd refuses an activation for a
configKey it has never seen, so this line alone would stop a Zoo node at genesis.

It is the old unified LP-4200 PQCrypto key from before that block was split into
mlkem, mldsa, slhdsa, p3q, pulsar, corona, hqc and magnetar. Zoo already
activates all eight, so nothing is lost by removing the name they replaced.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-10 18:58:55 -07:00
2026-09-08 15:28:19 -07:00
2026-09-08 15:28:19 -07:00
2026-09-03 11:04:58 -07:00
2026-09-08 15:28:19 -07:00
2026-09-08 15:28:19 -07:00
2026-02-14 05:27:03 -08:00
2026-09-08 15:28:19 -07:00
2026-03-26 22:45:36 -07:00

Zoo Universe — retired

Read-only from here. Canonical: https://git.hanzo.ai/zoo/universe

This tip is an ancestor of canonical main, so no commit reachable from this branch is unique to it — the canonical repo is a strict superset. Nothing was lost by stopping here.

Two universes for one org is a split brain: a push lands somewhere real, reports success, and never reaches a cluster, because CD reconciles the other one (deploy/applicationset.yaml names the canonical URL). One repo per org means that failure cannot happen.

S
Description
Declared state for the zoo fleet: one values file per service, one ApplicationSet
Readme
1.2 MiB
Languages
TypeScript 70.1%
Shell 21.5%
Makefile 8.4%