Topo

P2P Protocol

An event-sourced, end-to-end encrypted, batteries-included P2P protocol for building complex applications such as team chat. Defines a DAG-based event pipeline where commands produce signed, encrypted, hashed events that are transmitted peer-to-peer via QUIC, validated against mTLS trust state, topologically sorted for causal ordering, decrypted, and stored in SQLite for querying. Informed by and developed for the Quiet project. Self-described as a proof-of-concept, not for production use.

Comunidade
Links
Visitar Comunidade

Detalhes

Licença Apache-2.0 / MIT (Rust standard dual license inferred from Cargo.toml; contributing guidelines present) https://github.com/holmesworcester/topo
Status de Dev 🟢 Ativo
Detalhe do Status de Dev WIP (proof-of-concept; explicitly marked not for production use; stretch goal of simplicity not yet met per author)
Proprietário holmesworcester (GitHub handle); affiliated with TryQuiet / Quiet project
País Unconfirmed
Ano de Início 2026
Stack Rust
Financiamento Unconfirmed
Última Investigação 1 de jul. de 2026

Domínios de Caso de Uso

Platform Evolution & Sovereignty

P2P Protocol Atributos

Origins Chat / Messaging (designed as P2P backend for team chat; emerged from Quiet development)
Database SQLite (via rusqlite; events stored after decryption and topological sort)
Query Language Custom RPC (JSON method calls via topo rpc; structured request envelope with version field)
Data Formats Custom binary event format (signed, encrypted, hashed events over QUIC wire); JSON (RPC layer)
Collaborative Live Editing N/A (protocol spec; no application editing layer)
Rich Text Editing N/A
Mobile Support N/A
Web Support N/A
Native Apps N/A (CLI daemon only; no native app)
Terms Free / Open source
Funds Unconfirmed
Based On QUIC (transport); mTLS (peer authentication); SQLite (local storage); TLA+ (formal model for DAG and bootstrap transport logic)
P2P Architecture DAG-based causal broadcast (events form a directed acyclic graph; topological sort enforces causal ordering; peers sync via set reconciliation over QUIC with mTLS mutual authentication)
Overlay Network App-wide (workspace-scoped; peers are members of a named workspace; no global DHT)
Content Addressing Yes (events are signed and hashed; content-addressed by cryptographic hash in the event pipeline)
Local-First Yes (SQLite local store is the primary data source; sync happens over QUIC between peers)
E2EE Yes (end-to-end encrypted by design; events encrypted before transmission, decrypted only on receiving peer after pipeline validation)
CRDTs Lib N/A (custom event DAG; no CRDT library identified)
Byzantine Fault Tolerance No (set reconciliation sync; no explicit BFT consensus mechanism documented)
Signature mTLS (mutual TLS for peer authentication; event signing implicit in hash-sign-encrypt pipeline)
Permissions mTLS-based (peers validated against event-sourced trust state; workspace invite flow controls membership)
Semantic Web Compatibility No
Smart Contract No
Protocol Stack Position Application-layer (built on QUIC over UDP / TCP/IP stack)
Asset / Value Embedding None
Protocol Maturity / Standardization Pre-specification (proof-of-concept with design documentation and TLA+ formal models; no standards body submission; author notes it is not yet simple enough)