Assets
GB. The GBToken below is no longer recognised and its services have stopped. The new GB design is summarised in GB purchase, metering, fees and settlement and is not yet live. The GB token whitepaper and GB AMM whitepaper are superseded and kept for reference.
Evidence level: Production reference. Contract addresses identify current CoNET L1 assets; economic policy and upgrade authority require separate review.
This page identifies the principal assets referenced by CoNET L1 documentation. It is an asset map, not a tokenomics specification.
All assets below are associated with CoNET L1, chainId 224422.
| Asset | Type | Protocol use |
|---|---|---|
| CNET | Native asset | Pays L1 gas and participates in protocol staking or bond mechanisms where a contract explicitly requires it |
| wCNET | Canonical ERC-20, 18 decimals | 1:1 wrapped native CNET on CoNET. Bridge mint and burn went through TreasuryBridgeV3; Base holds a separate unwrap-disabled representation. Cross-chain service has stopped while the Treasury cross-chain bridge is paused |
| conet-USDC | Canonical ERC-20 | Status to be verified. It will be replaced by a newly deployed contract (decided, not yet live); the switch-over plan will be announced. The current contract will not be upgraded. USD-denominated settlement and accounting asset used by CoNET contracts |
GBToken (GB) |
ERC-20, 9 decimals | No longer recognised; services stopped. GB balance and transfer asset for DePIN service and bandwidth-related flows |
Canonical contracts
| Component | Address |
|---|---|
| TreasuryBridgeV3 proxy (sole Treasury) | 0xa208982212978550594A7FEEB70a61665d129003 |
| ConetTreasuryPeer v4 (module, not a Treasury) | 0x6093871d8a3EE6EaADc9869451D1693973cFBCC0 |
| conet-USDC | 0x5209865D404aA5646eDe5B91CD4218909eA72eDA |
| wCNET | 0x5a2D096968fC85861d8FDC7CE9A747Fe4bcb87D5 |
| GBToken | 0xC3EF02DaE632b4C10abB66e07d92a387c10838D8 |
The Treasury controls explicit cross-chain route and canonical-asset policy. A foreign ERC-20 does not become canonical merely because it has been wrapped or assigned matching metadata. See Decentralized cross-chain Treasury.
The Treasury cross-chain bridge is paused. The current two-way AAC bridge between CoNET and Base is approved but not yet live. The earlier AAC track specified proof-driven movement for canonical USDC, paid GB, wCNET, and unbound developer ERC-20s; AAC custody was never opened. It does not permit free GB or a developer token bound to a GB exchange rate to cross. Miner completion reverts VoteBridgeClosed. Base → CoNET proofs need the EIP-2537 precompiles, which CoNET has run natively since Prague (2026-10-18).
CoNET-USDC uses 6 decimals. Issued-NFT social exchange payouts must use this
canonical token; the legacy USDC factory address
0xfD0D7B0706AaB5E4351bcED37bC3C77ed6813907 is deprecated. In that exchange,
the user's AA burns Reward PT #13, while the merchant card escrow pays the
canonical USDC reward to the user's EOA.
ConetGB1155 is deprecated. It is a legacy accounting track and must not be used as the canonical GB wallet balance, transfer asset, or default integration target. The GBToken ERC-20 is no longer recognised either; balances do not carry over to the new GB, which is not yet deployed (new GB design).
GB and conet-USDC design status. The GBToken above is no longer recognised and its services have stopped; this page describes it as it was deployed. The current conet-USDC contract will be replaced by a newly deployed contract (decided, not yet live); the switch-over plan will be announced. The current contract will not be upgraded. The status of the current contract is to be verified. A proposed replacement design is described in the GB token whitepaper (draft): paid GB issued only by burning conet-USDC, free GB that is consume-only and non-transferable, and conet-USDC deployed as a new contract with no admin or upgrade authority. That design is not deployed and is not approved by the DAO. Its deployment waits for design discussion and an independent audit. Market structure and treasury operations for that design are described in the GB AMM whitepaper (draft).
Next-generation contracts (decided, not yet live). The new GB, wCNET and conet-USDC contracts will be deployed by the fixed AAC factory during initialisation. They cannot be upgraded, and their key authorisations are frozen when initialisation completes. No address exists yet, and deployment still needs an independent audit and a separate approval. The addresses above stay in place until a switch-over is announced. See GB purchase, metering, fees and settlement and Two-way AAC bridge.
Endpoint note
Read balances and token metadata from https://rpc1.conet.network, with https://publicrpc.conet.network as backup. https://rpc.conet.network is deprecated. The canonical Explorer is https://mainnet.conet.network.
Source anchors
- Resources — official services and source references
- Chain identity — network identity and RPC authority
- RPC and Explorer — query guidance
- Decentralized cross-chain Treasury — route, quorum, and asset-admission boundary
- AAC proof-driven cross-chain settlement — production read-only Shadow; Obstacles 1–5 Accepted (2026-10-14); custody still closed