zeekayandHanzo Dev
465317b703
The six precompiles that were linked and never activated now take effect at 1766708400 with everything else rather than at a second date of their own. This chainconf is a single activation timestamp. Backdating means a chain that already has blocks under the old set has to be reimported: swap, v3 and modelRegistry write state when they activate, so the state root at activation is not what the existing history recorded. That is the cost of one date instead of two, and it is paid by reimport. The node has to carry the keys before a chain may name them - luxd refuses an activation for a configKey it has never seen - so this config needs a luxd built after luxfi/evm started importing the suite registry. 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.