Files
zeekay 033f6bdd28 configs: materialise Q/Z shards for Lux primary networks
Q-Chain and Z-Chain are opt-in (per the builder refactor), but every
Lux-derived primary network bakes them. Make the intent explicit: ship
qchain.json + zchain.json shards alongside cchain.json so the chain set
is data-visible rather than implied by a builder default.

Downstreams (<tenant> etc.) that want P+X only simply don't ship these
shards in their config tree. No env, no flag — the shard set is the
network's identity.

The placeholder content {"version":1,"message":"Lux Chain Genesis"} is
the same string the old loadSpecialtyChainGenesis fallback substituted;
materialising it here keeps the on-wire genesis bytes stable across the
refactor.
2026-05-12 14:02:43 -07:00

2 lines
44 B
JSON

{"version":1,"message":"Lux Chain Genesis"}