Rings Network
A P2P network for the sovereign age.
Rings is a browser-native, structured peer-to-peer network that gives every browser tab and native daemon a sovereign network layer. Peers join a unified Chord DHT overlay, authenticate and discover each other by DID, exchange encrypted messages over direct WebRTC datachannels, and route private traffic through multi-hop Sphinx onion circuits.
Features
One network layer across browser and native peers.
Browser-native peers
Rings runs directly in browsers through WebAssembly and web_sys, and on native hosts through the same Rust node stack. Direct WebRTC datachannels carry peer-to-peer traffic across browsers and daemons.
DID identity and cryptography
Peers use decentralized identifiers backed by selectable signature schemes, connecting browser, daemon, and wallet identity workflows across secp256k1, secp256r1, ed25519, BLS, and bip137.
Structured peer routing
A Chord DHT provides peer discovery, successor and finger-table routing, message relay, stabilization, and network isolation for independent overlays.
Protocol runtime
Applications register namespace-scoped protocols. Pure state transitions stay separate from side effects performed by an interpreter through scoped capabilities.
Architecture
Applications over protocols, Sphinx onion privacy, Chord, WebRTC, and DID.
Rings layers application behavior, pure protocol state machines, multi-hop Sphinx onion circuits, Chord DHT routing, direct WebRTC transport, and DID identity. Applications address peers and namespaces while the lower layers establish direct connectivity, route authenticated messages, and protect metadata privacy.
The interactive browser node includes wallet login, SDP and HTTP connectivity, live Chord ring topology inspection, onion proxy routing, and custom namespace messaging right in your browser tab.