Resources

Operational references, public endpoints, source repositories, and maturity boundaries for CoNET.

Public endpoints

https://rpc.conet.network is deprecated and may be on a divergent historical network. Do not use it as CoNET L1 truth.

Core L1 contracts

Canonical CoNET-USDC for CoNET L1 application settlement: 0x5209865D404aA5646eDe5B91CD4218909eA72eDA (6 decimals). The sole active Treasury is TreasuryBridgeV3 at the address above; legacy USDC factory addresses and older Treasury addresses are deprecated.

Verify current code and state on the active RPC before relying on a historical deployment note.

Application and developer guides

Source repositories

CoNET is developed as open source. The complete, categorized list of public infrastructure, protocol, application, contract, SDK, client, and documentation repositories is maintained in the Open source repository index.

Maturity

These labels are not security-audit, uptime, or anonymity guarantees.

Operational boundaries

• The public L1 node-joining path uses the documented geth and Prysm P2P interfaces and does not require conet-l0d.
• web3:// uses Layer Minus over existing L0 resources; it does not add a second network or SI command family.
• SilentPass provides wallet-authorized privacy egress to ordinary Internet services. It is not an L1 consensus transport.
• Do not create a new public domain or endpoint without prior DNS, TLS, and operator approval.
• Do not restart geth, beacon-chain, validator, Reth, or rollup-node infrastructure without explicit operator authorization.

Independent verification

For L1 reads:

1. query eth_chainId and expect 224422;
2. query the active RPC rather than a deprecated endpoint;
3. compare contract code and state with Explorer when appropriate; and
4. distinguish a successful RPC response from proof of an application action.

For L0 or web3://:

1. verify exact wallet/tag and AddressPGP identity;
2. verify the configured entry and mailbox route;
3. verify the versioned request or session ID;
4. verify the response request ID, nonce, expiry, and encrypted return path, or verify bidirectional session data; and
5. verify the origin application's result.