Mainnet cut over 2026-09-09 09:01 UTC. The spec (sha256 81f048c0…, id "mainnet", genesis 0xfb5487c0…) is committed under asset/chainspec/ and the deploy env carries the spec path, its checksum, the expected genesis and the seven foundation bootnodes, so push-triggered deploys reproduce the hand cutover exactly and validate asserts the genesis from now on. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5
Chain spec files the node deploy can run from (CHAINSPEC_URL / the
chainspec_url input as a repo path, e.g. asset/chainspec/mainnet.json).
Commit only a file verified against the publisher's checksum, and record that
checksum in CHAINSPEC_SHA256 so the deploy re-verifies it; the started node's
genesis hash is asserted separately against EXPECTED_GENESIS.