Networks Registry
| Environment | Intended role | Assumption to record |
|---|---|---|
| Anvil | Primary deterministic development and exploit laboratory | fork block, chain ID, accounts, timestamp/base-fee controls |
| Ethereum Sepolia | Application and tooling testnet | current endpoints, faucets, explorer, confirmation policy |
| Ethereum Hoodi | Protocol/validator testing where relevant | current client support and purpose |
| Base Sepolia | L2 application contrast, chain ID 84532 at this snapshot | L1 relationship, sequencer status, bridge/finality behavior |
| Controlled OP Stack environment | Rollup lifecycle and failure simulation | exact releases, proposer/batcher/sequencer ownership |
Public testnets are mutable infrastructure, not permanent fixtures. Before every deployment, verify chain ID from at least two authoritative paths, active network status, explorer and source-verification support, RPC method compatibility, faucet provenance, finality semantics, native token, and deprecation notices. Holesky is intentionally not a default because it is deprecated in the consulted Ethereum documentation.
Never infer safety from a familiar network name. Client, wallet, RPC, explorer, bridge, and deployed-contract addresses must all agree.