Developers
Use this section to build or operate against CoNET. Read the architecture in dependency order: L0 cloud resources, Layer Minus privacy routing, L1 shared state, and DLE L2 specialized ledgers. Application protocols and user-facing products are documented separately.
A change to an L0 wire contract must update both the architecture and developer tracks in the same task.
Maturity labels
This section uses the book-wide labels defined on Home: Production reference, Implemented capability, Under development, Normative design, and Design study. A runnable command is not by itself proof of production availability or an audit.
Tracks
| Track | What you build or operate | Maturity | Start here |
|---|---|---|---|
| Layer Minus development | A client using POST /post, mailbox receive, Chat, UDP, or another encrypted application envelope |
Implemented capability | L0 development |
web3:// applications |
Wallet-addressed request/response or persistent application streams | Under development | Protocol |
Linux web3:// runtime |
Publish or open services with conet-l0d |
Under development | conet-l0d |
| L1 node | A permissionless geth + Prysm full node and optional validator | Production reference | Run an L1 node |
| L1 mining | Guardian / LayerMinus participation and verified mining gossip | Implemented capability | Participate in mining |
| L1 ERC-20 ingress | Implement the specified admission path for a foreign ERC-20 through TreasuryBridgeV3; deployed Treasury references are documented separately | Normative design | Bring an ERC-20 into CoNET |
| L2 development | Implement or review the CoNET-DLE specifications; lab evidence is separate from production | Normative design | L2 development |
Choose the right track
- Understand contributed infrastructure resources: start with L0.
- Forward ciphertext by wallet or OpenPGP key ID over those resources: use Layer Minus and L0 development.
- Build a wallet-addressed application: implement the
web3://protocol. - Host that application on Linux or open it from a Linux client: use
conet-l0d. - Implement the client on Windows, macOS, Android, iOS, or in a browser:
implement the same
web3://locator, caller-signed request, encrypted response correlation, and rendering contract in client code. - Run geth and Prysm: use Run an L1 node. The public P2P path is
independent of
web3://. A laboratory overlay that keeps those same clients and dials remotes asweb3://<wallet>:<port>is recorded in L1 overlay lab. - Join DePIN mining: use Participate in mining.
- Move an ERC-20 into CoNET: use Treasury ERC-20 ingress.
- Implement a parallel ledger: use L2 development; do not treat the lab explorer as a production DLE SDK.
Reusable constants
| Item | Value |
|---|---|
| CoNET L1 | chainId 224422 |
| Primary RPC | https://rpc1.conet.network |
| Backup public RPC | https://publicrpc.conet.network |
| Explorer | https://mainnet.conet.network |
| AddressPGP | 0x684b0ac760cEE9c9b85de36d69746420648Cf9e2 |
| GuardianNodesInfoV6 | 0xBC6b53065b5647261396d002bDBA0d3396E0722f |
| TreasuryBridgeV3 | 0xa208982212978550594A7FEEB70a61665d129003 |
Do not use deprecated https://rpc.conet.network. Do not invent an SI
hostname; use existing Guardian domains from the live registry.
Public source
CoNET infrastructure, protocols, clients, contracts, SDKs, and documentation are developed in public repositories. Use the Open source repository index to find the source owner for each component before opening an issue or submitting a change.