7783b86136a3beb9cb214d65a4cc18796a51932e
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]>
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.
Description
Declared state for the zoo fleet: one values file per service, one ApplicationSet
1.2 MiB
Languages
TypeScript
70.1%
Shell
21.5%
Makefile
8.4%