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.

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.

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

• Architecture: System overview, then L0 → Layer Minus → L1 → L2.
• Application protocol: web3:// → protocol contract → Linux runtime.
• Products: Applications.
• L0 and Layer Minus implementation: L0 development, SI developer guide, and security limits.
• L1 operations: Run an L1 node, RPC and Explorer, and decentralization evidence.
• Public source: Open source repository index.
• Current endpoints and evidence: Resources.

Status and evidence

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.