network parameters.
Canonical network configuration belongs here so wallets, nodes and applications can verify they are connected to the intended environment and can distinguish testing infrastructure from production state.
required fields
Each public environment should publish the network name, environment label, chain ID, native currency name, symbol and decimals, genesis hash, supported RPC endpoints, explorer URL, environment status and the date or release that made the values canonical.
connection verification
Clients should verify more than an RPC hostname. The returned chain ID, genesis identity and published environment metadata should agree before an application treats a connection as canonical. A familiar hostname with mismatched chain identity should be treated as an error.
endpoint records
RPC and explorer entries should identify purpose, protocol, public availability and any published limits or restrictions. Multiple endpoints may serve the same environment, but they must resolve to the same canonical chain identity.
environment separation
Development, testnet and production parameters must be listed separately. Test assets, faucet resources, contract addresses and service identifiers must never be assumed to carry production meaning.
change control
Changes to canonical network identity require an explicit reference update. Endpoint additions can be additive, but changes affecting chain identity, genesis state or native asset metadata require clear migration or network-transition guidance.