Reticulum

P2P Protocols

Cryptography-based networking stack for building local and wide-area networks over any available medium — LoRa, packet radio, serial lines, WiFi, Ethernet, internet, and free-space optical links. A complete replacement for IP networking built directly on cryptographic principles: all packets are encrypted by default, routing depends on cryptographic entropy, and the protocol cannot function without encryption. Provides end-to-end encryption, initiator anonymity (no source addresses on packets), autoconfiguring multi-hop transport, forward secrecy, and unforgeable delivery acknowledgements. Designed to operate from 5 bits/second to 500 Mbps .

Fully P2P Community Low capture risk

Details

License Public Domain
Dev Status Released
Owner Mark Qvist (independent developer, computer engineer, 'unsignedmark'); protocol designed and implemented 2014–2022; announced departure from development December 2025; protocol is public domain, reference implementation open source
Country Not disclosed
Start Year 2014
Stack Python 3, PyCA/cryptography, pyserial
Funding VC, Community, Donations
Last Investigated Jan 15, 2026

Affordances

End-to-end encrypted Works offline / mesh Self-hostable

P2P Protocol Attributes

P2P Architecture Heterogeneous mesh (two node types: Regular Nodes and Transport Nodes; Transport Nodes route traffic between network segments; any node can be configured as Transport Node; self-configuring multi-hop routing; no source addresses — initiator anonymity; supports any mixture of physical mediums simultaneously)
Overlay Network Yes (medium-agnostic overlay that can span LoRa radio, packet radio, serial, WiFi, Ethernet, TCP/IP, UDP/IP, I2P, and custom interfaces simultaneously; can tunnel over internet while maintaining independent addressing; designed to interconnect thousands of independent networks into 'Hypernet')
Content Addressing Cryptographic addressing (destinations identified by truncated hashes of public keys — 128-bit addresses derived from Ed25519 identity keys; globally unique without coordination; not content-addressed but identity-addressed)
Local-First Yes (operates under arbitrary network partition; designed for high-latency, low-bandwidth, intermittent connectivity; no central servers required; LXMF supports delay-tolerant message delivery via propagation nodes; store-and-forward architecture)
E2EE Yes (all communication encrypted by default — encryption is not optional, it is fundamental to routing; X25519 ECDH key exchange; AES-256-CBC; forward secrecy via ephemeral per-packet and per-link keys; HMAC-SHA256 authentication; initiator anonymity — no source addresses)
CRDTs Lib No (networking stack layer; no CRDT implementation)
Byzantine Fault Tolerance Resilient but no formal BFT (cryptographic path verification prevents spoofing/tampering; unforgeable delivery acknowledgements; Transport Nodes use cryptographic signatures to verify routes; resilient to open and trustless networks but no consensus mechanism)
Signature Ed25519 (all identities based on 512-bit EC keysets; signatures used for path verification, delivery acknowledgements, and identity authentication; cryptographic proofs fundamental to routing)
Permissions Cryptographic identity-based (access determined by knowledge of destination hash / public key; virtual network segmentation on all interface types; link-level authentication; no role-based access control at protocol level — left to application layer)
Semantic Web Compatability No
Smart Contract No
Protocol Stack Position Application-layer (built on TCP/IP)
Asset / Value Embedding None — Reticulum is a cryptographic networking stack and protocol specification with no native token or economic incentive layer. Node participation is cooperative; the project is maintained by Mark Qvist under a custom license with no tokenomics.
Protocol Maturity / Standardization Proprietary Open Standard (protocol dedicated to public domain 2016; defined entirely by reference implementation and manual rather than formal specification document; wire-format and API considered stable; no standards body involvement; custom Reticulum License for implementation; single-author design 2014–2022 with growing community)