Files
zeekay ef7da013c8 A chain that is not an EVM gets no EVM chain id
Nine letters carried one: A, B, D, F, G, K, M, Q and Z, running AIVM, BridgeVM,
DexVM, ThresholdVM, GraphVM, KeyVM, mpcvm, QuantumVM and ZKVM. An EVM chain id
is EIP-155 replay protection for a signed EVM transaction, and none of those
chains signs one. Only the C-Chain does. P and X carried none all along, which
is the shape the rest should have had.

Nothing read them. They appear in the network configs and in this test and
nowhere else in the estate.

localnet drops them, and a test now requires their absence, so no network minted
from here inherits the mistake.

mainnet, testnet and devnet keep theirs and always will. Their shard JSON goes
into a CreateChainTx verbatim, so the field is part of the chain's genesis bytes,
which decide its blockchain ID, which decides the network's genesis hash.
Removing it there would not tidy those networks — it would define different ones
that the running validators refuse to join. Frozen by arithmetic, not by taste,
and the pin says so where the next person will read it.
2026-09-07 18:04:04 -07:00

12 lines
269 B
JSON

{
"description": "Post-quantum consensus + signatures (Quasar)",
"kemScheme": "mlkem768",
"message": "Lux Q-Chain Genesis",
"name": "Q-Chain",
"networkId": 1337,
"signatureScheme": "mldsa65",
"timestamp": 1735689600,
"version": 1,
"vm": "QuantumVM"
}