CoNET

From infrastructure to applications

CoNET is a wallet-addressed infrastructure stack. Three infrastructure layers supply cloud resources, shared state, and specialized ledgers. Layer Minus uses the L0 cloud to route OpenPGP-encrypted application traffic by wallet-linked identity. Application protocols and products then combine only the capabilities they need.

Plane Responsibility Start here
L0 — Decentralized Cloud Permissionless forwarding, ciphertext storage, service hosting, contributed CPU/GPU capacity, and GB metering L0 overview
Layer Minus — Privacy Protocol Wallet/OpenPGP-addressed routing, zero-trust entry and mailbox roles, and HTTP(S)-shaped encrypted transport on L0 Layer Minus · How to use it
L1 — CoNET Blockchain EVM state, identity registries, validators, canonical assets, Treasury, and settlement (chainId 224422) L1 overview · Run an L1 node
L2 — CoNET-DLE Specialized parallel application-ledger classes with explicit archive, finality, availability, and settlement rules L2 overview · DLE explorer

Open source

CoNET is developed in public open-source repositories. Protocol, infrastructure, client, contract, SDK, and documentation source links are collected in the Open source repository index. Individual hosted deployments may also depend on private operator configuration and secrets that are not part of the public source.

L0 cloud resources
        │
        ▼
Layer Minus privacy routing ───────┐
                                   │
L1 shared state and settlement ────┼──► application protocols ───► applications
                                   │
DLE L2 specialized ledgers ────────┘

This is a dependency map, not a mandatory pipeline. SilentPass focuses on privacy-oriented Internet access, CoNET Chat on relationship-private wallet communication, and Beamio on consumer, merchant, and POS workflows.

Where things stand (November 2026)

Area Status Read
CoNET L1 Production, chainId 224422. Osaka / Fulu active since 2026-10-18; the official Geth release runs current blocks L1 overview · Run an L1 node
Cross-chain settlement The Treasury cross-chain bridge is paused. The two-way AAC bridge between CoNET and Base is approved, not yet live: nothing is deployed, and deployment needs an independent audit and a separate approval Two-way AAC · Treasury
GB The previous GBToken is no longer recognised and its services have stopped; GB issuance from node metering is paused. The new GB design is not deployed; its rules are decided and parts are implemented locally. Cross-chain service for the current wCNET has stopped while the bridge is paused. 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. New GB design · Assets
DAO and treasury The DAO, the next-generation treasury and NodeRegistryV2 are implemented and tested locally, pending acceptance; nothing is deployed. Key bridge addresses are frozen at initialisation and the contracts cannot be upgraded DAO and treasury · Node registry V2
CoNET-DLE Normative design; the lab explorer is paused. The 30-day lab assessment was partial success, not qualified; production archive signing and asset ingress are not enabled L2 overview · Lab honesty track
Order-book exchange Whitepaper draft for an exchange that runs inside DLE; not implemented Exchange whitepaper

Design drafts and whitepapers

These documents describe designs. Rules marked as decided or approved are operator decisions, not DAO approval, and none of the designs below is deployed. Deployment needs an independent audit and a separate approval.

Wallet-addressed applications

web3:// is an application protocol using Layer Minus on L0 infrastructure. It defines wallet-addressed locators, exact identity resolution, caller-signed requests, correlated encrypted responses, persistent application streams, and client security rules without adding another L0 wire command.

Linux servers and clients can use the conet-l0d runtime. Windows, macOS, Android, iOS, and browser applications implement the same web3:// contract in browser or native client code. See the protocol contract for interoperable URI and envelope rules.

Privacy boundary

Layer Minus does not remove TCP/IP from the Internet and does not promise absolute anonymity. OpenPGP protects application plaintext, while role separation reduces the need for one intermediary to observe both endpoints. An entry can still observe the connecting client, a mailbox can observe route activity, and traffic timing and size remain metadata. Ordinary HTTP-shaped transport can reduce dependence on a distinctive custom carrier or TLS handshake, but it is not guaranteed to be indistinguishable from all Web traffic.

How to read this book

Status and evidence

Evidence level Meaning
Production reference Live chain, endpoint, contract, or public application entry
Implemented capability Present in source, but not necessarily enabled in every deployment
Under development Active implementation or integration work
Normative design Controlled by a specification; deployment status is separate
Design study Non-normative application or economic proposal

A production reference is not by itself an audit, uptime guarantee, or claim that every feature is enabled. Historical imported documentation is not the source of truth for this book.

results matching ""

    No results matching ""