Files
genesis/configs/devnet/securityProfile.json
zeekay ed111ee8f3 genesis: pin StrictPQ profile against [email protected] hashes
Production e2e PQ wire-up:
  mainnet, testnet, local, localnet → StrictPQ (0x01)
  devnet                            → Permissive (0x02) for dev workflows

Replaces the v1.22.87-era ForkClassicalCompatUnsafe (0x80) pins which
collide with v1.23.15's tightened registry (profiles collapsed to 3
canonical bundles; 0x80 is no longer in ProfileByID's switch). The
luxfi/node v1.26.17 build resolves these pins at boot and stamps the
profile through to every wire-level gate (peer handshake, mempool,
validator scheme, EVM contract auth, C-Chain plugin config).

Verified live at boot:
  SECURITY PROFILE: STRICT
  PROFILE HASH:     cf3f2cd7b54cfc2c…
  POST-QUANTUM:     true
  NIST-FRIENDLY:    true
  CLASSICAL SNARKS: forbidden
  BLS FALLBACK:     forbidden

Hashes computed via consensus.ChainSecurityProfile.ComputeHash() — when
consensus rolls, regenerate pins via the same path (a CI guard against
silent profile drift is the next layer).
2026-05-12 13:11:50 -07:00

5 lines
141 B
JSON

{
"profileHashHex": "b06630a5f335e139ccbc2ff23fcd9fcdd2d9b390a92407507f95a295aea6905662c8c9dac98764661f9bc292da799e95",
"profileID": 2
}