zeekayandHanzo Dev a05b8c8227 chainconf: activate the precompiles the node links and never ran
Six precompiles were dispatchable and activated nowhere in the estate:
aiInference, aivmBridge, modelRegistry, starkfri, swap and v3. The cause was
upstream - luxfi/evm named its suite packages one by one and had drifted from the
suite, so those configKeys did not exist to be named and luxd would have rejected
an activation for them. The registry now imports the suite wholesale, so they do.

They take effect at 1790812800 (2026-10-01), not the existing 1766708400: that
date is December 2025 and already past, and swap, v3 and modelRegistry write
state when they activate, so backdating them onto a chain with accepted blocks
changes state roots under history.

Entries stay sorted by timestamp; precompileUpgrades must be monotonic.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-10 17:58:38 -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%