a05b8c82279bab1f357bd210d946320fbdd6ab19
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]>
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%