Genesis

Locked

The canonical machine-readable source is chains/testnet-69420.toml. These docs pin registry commit d9e0f9ff0f7d10fc779ad3ffc11860e68d01ecdf.

Registered testnet 69420 identity

Field	Binding value used by these docs
Network	`testnet-69420`
Chain ID	`69420`
Genesis hash	`0xe22733f4d7e013b93f0f825667fcf852cbf7ad1ca31a42a1bfcf1ab6d79c89a3`
`genesis.toml` SHA-256	`5e5e6e0301bf742e2b7e81794ac20ca3fb5f39fdadf54230e1e0c625f9bf2cbb`
Runtime release	`v0.4.0-testnet`
Runtime commit	`da04f8f5e8391811f80e8d0511dff74311f4e811`
Runtime binary SHA-256	`259c67c1c7fc8bc3f8ca22c82953ea7dc54a9e2ceaa02d0fe0879ab5192f8227`
Topology	Four clusters × ten operator positions; 7-of-10; two relays

This is a value-less, wipeable development network. A reset creates a new network identity even if chain ID remains 69420. Do not store value, carry balances across lineages, or connect automatically after a genesis mismatch.

Verification rule

Fetch the registered profile through an independently authenticated channel.
Compare the full genesis hash and genesis file digest.
Compare runtime release, commit, binary digest, and dirty-build flag through lyth_runtimeProvenance and release artifacts.
Stop on any mismatch; do not fall back to chain ID alone.
Separately check finalized-state freshness, round progression, sync lag, and peer-health bands; identity agreement does not prove liveness.

The documentation gate performs the corresponding safe read-only RPC probes. It does not download or execute an operator binary.

Superseded lineages

Earlier testnet genesis hashes and releases are historical and must not be presented as the registered identity. Detailed cutover incident notes belong in versioned release history, not in the current network-identity contract.

Mainnet

Chain ID 69422 is reserved only. There is no announced mainnet genesis or running public mainnet.