After adding an EVM network to your wallet, you can trace its Chain ID—the number that identifies the network in transactions—to a number its team chose and submitted to the public ethereum-lists/chains registry. No central authority issues it. The team configures its network to use the number; the registry records the choice for others to find.
That record helps you check a wallet entry against the network details you were given. Chainlist shows chain IDs alongside RPC endpoints, which wallets use to contact network nodes, and native currencies. Those details help you distinguish networks with similar names before you connect.
For a new L2, the team first looks for an unused chain ID, then opens a pull request to ethereum-lists/chains with the network’s metadata. The registry rejects an ID already taken; the first accepted pull request claims it. Once the entry is merged, directories such as Chainlist can display it. This process keeps IDs unique by convention: the registry checks submissions, while the network’s own configuration sets the ID its nodes use.
Take Base, which uses chain ID 8453. Ethereum mainnet uses 1, and Sepolia uses 11155111. When your wallet signs a Base transaction, it includes 8453 in the data being signed. EIP-155 introduced that chain specific signing so a transaction prepared for one network cannot simply be replayed on another with a different ID. A mainnet node expects 1, so it rejects the Base transaction.
Duplicate IDs remove that protection between the networks sharing them. Suppose another L2 also uses 8453. A signed Base transfer would pass that L2’s chain ID check; if the sender has the right nonce and enough funds there, the transaction could run there too. That is why checking for an unused number matters before a network launches, and why a familiar network name alone is insufficient when you add it to a wallet.
To verify a network’s actual ID, call eth_chainId on its RPC endpoint. The response is hexadecimal: Base returns 0x2105, which is 8453 in decimal. Compare that result with the chain ID in your wallet settings before signing. Repeating this check whenever you add an RPC endpoint helps catch a mismatched network entry and avoids sending a transaction to the wrong chain.