Resources
Operational references, public endpoints, source repositories, and maturity boundaries for CoNET.
Public endpoints
| Purpose | Endpoint |
|---|---|
| CoNET L1 primary RPC | https://rpc1.conet.network |
| CoNET L1 backup public RPC | https://publicrpc.conet.network |
| Explorer / Blockscout | https://mainnet.conet.network |
| Alternate Explorer entry | https://scan.conet.network |
| Beamio application/API origin | https://beamio.app |
Merchant OS onboarding website / file lookup (Cluster read; optional files JSON) |
POST https://beamio.app/api/onboardingBusinessLookup |
| Merchant OS onboarding Card Setup assets (Cluster read) | POST https://beamio.app/api/onboardingBusinessCardSetup |
| Agent / referrer registry read (Cluster) | GET https://beamio.app/api/agentReferrerRegistry |
| Agent / referrer registry write (Cluster → Master; EIP-712 ops) | POST https://beamio.app/api/agentReferrerRegister |
| IPFS fragment service | https://ipfs.conet.network |
| Base RPC used by active Treasury and institutional-multisig paths | https://base-rpc.conet.network |
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
| Contract | Address |
|---|---|
| AddressPGP | 0x684b0ac760cEE9c9b85de36d69746420648Cf9e2 |
| GuardianNodesInfoV6 | 0xBC6b53065b5647261396d002bDBA0d3396E0722f |
| EpochMiningInfo | 0x648f1a17269627C3d465fEa40b3C229f7CacE5cA |
| TreasuryBridgeV3 | 0xa208982212978550594A7FEEB70a61665d129003 |
| ChatIndexRegistry | 0x1511Caa71081C84d8a591490D1b83879088EED72 |
| BeamioAgentReferrerRegistry (UUPS proxy; canonical) | 0x40f1B57280f9195AfEf2B4433CEc8f79d4b58b9A |
| BeamioAgentReferrerRegistry implementation | 0xb3535499aBAA9369681e092eAA8d84555eB3fbDe |
| GBToken (no longer recognised; services stopped) | 0xC3EF02DaE632b4C10abB66e07d92a387c10838D8 |
Canonical CoNET-USDC for CoNET L1 application settlement:
0x5209865D404aA5646eDe5B91CD4218909eA72eDA
(6 decimals). 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. The sole Treasury is TreasuryBridgeV3 at the address
above, and its cross-chain bridge is paused; legacy USDC factory addresses and older Treasury addresses are
deprecated.
The GBToken above is no longer recognised and its services have stopped. The new GB design is described in GB purchase, metering, fees and settlement; it is approved, not yet live, and deployment needs an independent audit and a separate approval. The earlier GB token whitepaper is superseded.
Verify current code and state on the active RPC before relying on a historical deployment note.
Application and developer guides
| Goal | Guide |
|---|---|
| Understand decentralized cloud resources | L0 |
| Understand privacy routing | Layer Minus |
| Build with Layer Minus | L0 development |
| Build a wallet-addressed application | web3:// Application Protocol |
Use the Linux web3:// runtime |
conet-l0d |
Implement a browser/native web3:// client |
web3:// application |
| Understand the two-way AAC bridge | Two-way AAC bridge (approved, not yet live) · earlier AAC design |
| Understand GB fees and settlement | GB purchase, metering, fees and settlement · Mailbox storage billing |
| Understand node registry V2 | Node registry V2 (approved, not yet live) |
| Understand third-party tokens and subscriptions | Third-party tokens and subscriptions (approved, not yet live) |
| Understand DAO voting and the next-generation treasury | DAO and the next-generation treasury (approved, not yet live) |
| Run an L1 node | Run an L1 node |
| Confirm the period-18 checkpoint | Confirm the period-18 checkpoint |
| Participate in mining | L1 mining |
| Build against DLE specifications | L2 development |
| Read the CoNET Chat product thesis | CoNET Chat |
| Read the privacy-first decentralized AI design study | Landing · Whitepaper |
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.
| Project | Repository |
|---|---|
| CoNET SI | CoNET-project/CoNET-SI |
| LayerMinus / mining client | CoNET-project/CoNET-DL |
Linux web3:// runtime |
CoNET-project/CoNET-L0D |
Browser web3:// client |
CoNET-project/web3Url |
| CoNET DLE | CoNET-project/CoNET-DLE |
| AAC Rust reference gateway | CoNET-project/bridgeAAC |
| CoNET execution-client BLS patch (pre-Prague replay only) | CoNET-project/patch-geth |
| Documentation | CoNETProject/docs |
Maturity
| Capability | Evidence level |
|---|---|
| L0 decentralized resource plane | Implemented capability |
| Layer Minus encrypted entry/mailbox forwarding | Implemented capability |
| L1 chain, RPC, Explorer, validators, and assets | Production reference |
| CoNET Chat delivery, receipt, presence, and encrypted-history components | Implemented capability |
web3:// locator, Linux runtime, caller-signed gateway, and early browser client |
Under development |
| AAC proof-driven cross-chain settlement | Production read-only Shadow v0.33.13 (switched 2026-10-16; audit fixes H1, H2, M1–M6); Obstacles 1–5 Accepted (2026-10-14); Phases B–E recorded (2026-10-15); sourceInitiateOpen is true on Base and CoNET. Checked execution clients run patch-geth; a 0.01 Base USDC receipt in period 1884 is covered and settled |
| CoNET-DLE specifications | Normative design; lab evidence is separate from production |
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:
- query
eth_chainIdand expect 224422; - query the active RPC rather than a deprecated endpoint;
- compare contract code and state with Explorer when appropriate; and
- distinguish a successful RPC response from proof of an application action.
For L0 or web3://:
- verify exact wallet/tag and AddressPGP identity;
- verify the configured entry and mailbox route;
- verify the versioned request or session ID;
- verify the response request ID, nonce, expiry, and encrypted return path, or verify bidirectional session data; and
- verify the origin application's result.