Topo

Protocolo P2P

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 Website Sugerir uma correção

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 🔨 Em desenvolvimento
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
Órgão de Governança None (single developer; proof-of-concept stage)
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

Evolução de Plataformas e Soberania

Capacidades

Criptografado de ponta a ponta Armazenamento local-first

Protocolo P2P Atributos

Origens Chat / Messaging (designed as P2P backend for team chat; emerged from Quiet development)
Banco de Dados SQLite (via rusqlite; events stored after decryption and topological sort)
Linguagem de Consulta Custom RPC (JSON method calls via topo rpc; structured request envelope with version field)
Formatos de Dados Custom binary event format (signed, encrypted, hashed events over QUIC wire); JSON (RPC layer)
Edição Colaborativa em Tempo Real N/A (protocol spec; no application editing layer)
Edição de Texto Rico N/A
Suporte Móvel N/A
Suporte Web N/A
Aplicativos Nativos N/A (CLI daemon only; no native app)
Termos Free / Open source
Fundos Unconfirmed
Baseado Em QUIC (transport); mTLS (peer authentication); SQLite (local storage); TLA+ (formal model for DAG and bootstrap transport logic)
Arquitetura P2P 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)
Rede de Sobreposição App-wide (workspace-scoped; peers are members of a named workspace; no global DHT)
Endereçamento por Conteúdo 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)
Criptografia de Ponta a Ponta (E2EE) Yes (end-to-end encrypted by design; events encrypted before transmission, decrypted only on receiving peer after pipeline validation)
Biblioteca de CRDTs N/A (custom event DAG; no CRDT library identified)
Tolerância a Falhas Bizantinas No (set reconciliation sync; no explicit BFT consensus mechanism documented)
Assinatura mTLS (mutual TLS for peer authentication; event signing implicit in hash-sign-encrypt pipeline)
Permissões mTLS-based (peers validated against event-sourced trust state; workspace invite flow controls membership)
Compatibilidade com a Web Semântica No
Contrato Inteligente No
Posição na Pilha de Protocolo Application-layer (built on QUIC over UDP / TCP/IP stack)
Incorporação de Ativo / Valor None
Maturidade / Padronização do Protocolo Pre-specification (proof-of-concept with design documentation and TLA+ formal models; no standards body submission; author notes it is not yet simple enough)