Resonator
A semantic peer-to-peer protocol where all communication, state, and computation are RDF.
What is Resonator
Resonator is a protocol and a set of rules for building decentralized networks. Everything in Resonator is an RDF object — your state, your connections, your data pipelines — exchanged over end-to-end encrypted links via DHT, UDP broadcast, or static peer lists.
There is no server. There is no feed. You are either connected and can exchange, or not.
Architecture
Carrier — the transport layer. A compact C library wrapping the Tox protocol. Provides encrypted peer-to-peer tunnels with zero configuration. Wire protocol is RDF 1.1 Turtle.
Antenna — the processing layer. A Rust runtime embedding a full RDF triplestore and a JavaScript engine. Processes incoming RDF streams through a programmable DAG of script nodes, all queryable and hot-reloadable via SPARQL.
Bootstrap nodes — initial DHT discovery only. They carry no traffic and see no content after peers find each other.
Properties
- End-to-end encrypted — NaCl cryptography, automatic NAT traversal
- No accounts, no servers — your identity is a 2 KB keypair file
- Everything is RDF — communication, pipeline definitions, scripts, state
- Composable — Unix-style pipes, streams, and raw data transfer
- Programmable — JavaScript/Lua scripts run on RDF streams in real time
- Offline-first — nodes sync state when they reconnect