Rings Network
A P2P network for the sovereign age.
Rings is a browser-native, structured peer-to-peer network for applications that need their own network layer instead of a server-owned data path. Browser tabs and native daemons can join the same overlay, discover peers by DID, and exchange messages over direct WebRTC datachannels routed by a Chord DHT.
Features
One network layer across browser and native peers.
Browser-native peers
Rings runs in browsers through WebAssembly and web_sys, and on native hosts through the same Rust node stack. WebRTC datachannels carry direct peer traffic without an application server in the data path.
DID identity and cryptography
Peers use decentralized identifiers backed by selectable signature schemes, bridging browser, daemon, and wallet identity workflows without binding the network to one key system.
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, Chord, WebRTC, and DID.
Rings separates application behavior, protocol state, overlay routing, transport, and identity. Applications address peers and namespaces while the lower layers establish direct connectivity and route authenticated messages across the structured overlay.
The interactive browser node adds wallet login, SDP and HTTP connectivity, topology inspection, onion proxy requests, and custom messages when JavaScript and WebAssembly are available.