mirror of
https://github.com/luxfi/dex.git
synced 2026-09-24 00:26:31 +00:00
zeekayandHanzo Dev
518fdf778c
The chain-creation documents I pinned came from luxfi/genesis's dchain.json. That file created none of the three live D-Chains. The bytes in each fleet's CreateChainTx differ from it: mainnet and testnet carry no chainId at all and end with a newline (356 bytes); devnet puts chainId first in sorted order and has no trailing newline (375 bytes — the same length as the config file and not the same bytes, so a size check passes and proves nothing). Pinned now: all three documents verbatim, each keyed on its keccak256, recovered from the CreateChainTx and confirmed byte for byte against every pod's own /data/genesis.json dChainGenesis. Two independent sources. Two traps make the document opaque by necessity, which is how the VM already treats it — hashed raw, never parsed, never re-encoded. The trailing newline is load-bearing and present on only two of three. The em dash is the literal six characters —, so a JSON round trip changes both length and hash. TestGenesisLiveFleets now asserts the defect directly: not one live D-Chain has the genesis its own creation record implies. All three were born from the binary. Co-authored-by: Hanzo Dev <[email protected]>