Chain identity

Evidence level: Production reference. Values below describe the active CoNET L1 and must be checked against an active endpoint when used operationally.

Canonical network

The chain ID is necessary for signing and replay-domain separation, but it is not sufficient to identify a healthy chain tip. Two endpoints can report the same chain ID while exposing different state.

RPC authority

Use only these general-purpose CoNET L1 endpoints:

1. https://rpc1.conet.network — primary
2. https://publicrpc.conet.network — backup

https://rpc.conet.network is deprecated and unreliable. It has been observed out of sync or divergent from the active network. Do not use it for block height, contract code, balances, transaction submission, deployment verification, or incident diagnosis.

Applications should fail over from the primary endpoint to the backup only after treating the failed response as untrusted. A timeout, malformed response, or unavailable RPC must not be converted into a zero balance or an empty on-chain result.

What L1 anchors

CoNET L1 is the canonical layer for:

• proof-of-stake block production and finality;
• native CNET balances and transaction fees;
• canonical CoNET assets such as conet-USDC and GBToken;
• protocol registries, identity, routing, node, and treasury contracts; and
• application contracts that explicitly target chainId 224422.

Individual contract addresses can change through deployment or upgrade procedures. Verify an address against current deployment records and its code on the active RPC, then inspect it at the canonical Explorer.

Source anchors

• RPC and Explorer — endpoint table and eth_chainId check
• Assets — active asset identifiers
• Resources — service and repository index

Next

Validators →