Tox
P2P Protocol
Comunidade
Links
Detalhes
Licença Libre (GPL-3.0-or-later); https://github.com/TokTok/c-toxcore — reference implementation in C; Rust rewrite (toxcore-rs) in development
Status de Dev 🟢 Ativo
Detalhe do Status de Dev Released / Active (c-toxcore v0.2.22, February 2026; ongoing development under TokTok; no full third-party security audit completed)
Proprietário TokTok Project (community-maintained); originally created by irungentoo (pseudonymous) in 2013; ongoing development by TokTok collective
País International (distributed community; no single geographic home)
Ano de Início 2013
Stack C (c-toxcore reference implementation); Rust (toxcore-rs rewrite in development); NaCl/libsodium (cryptography); UDP + TCP transports
Financiamento Donations / Volunteer (TokTok collective; no institutional funding identified; community-driven)
Última Investigação 1 de jul. de 2026
P2P Protocol Atributos
Origins Privacy-focused messaging (created in 2013 as a decentralized, serverless alternative to Skype following NSA surveillance revelations; designed to replicate Skype functionality without central servers or corporate oversight)
Database N/A (stateless protocol; local friend list and key storage handled per-client implementation; no global database)
Query Language N/A (peer lookup via DHT node ID, not a query interface)
Data Formats Custom binary protocol (Tox packet format); NaCl encrypted payloads; Protocol Buffers considered but not adopted in current spec
Collaborative Live Editing N/A (messaging/AV protocol; no collaborative document editing)
Rich Text Editing N/A (plain text messaging; rich text is application-layer concern for clients)
Mobile Support Yes (Android and iOS clients: Antox, TRIfA, Antidote; Tox protocol runs on mobile)
Web Support No (no native browser implementation; protocol requires UDP socket access not available in browsers)
Native Apps Yes (qTox, uTox, Toxic CLI on Linux/macOS/Windows; TRIfA, Antox on Android; Antidote on iOS)
Terms Free / Open source (GPL-3.0-or-later); no commercial terms; client implementations vary by license
Funds Unknown / None disclosed (volunteer-funded open source project)
Based On Kademlia DHT (peer discovery); NaCl (cryptography); UDP/TCP transports; onion routing for IP privacy during friend requests
P2P Architecture DHT (Kademlia-variant for peer discovery; direct encrypted connections once peers located; UDP hole-punching for NAT traversal; TCP relay fallback)
Overlay Network Global (single global DHT network; all Tox nodes participate in same overlay)
Content Addressing No (peers addressed by 256-bit public key / Tox ID, not content hashes)
Local-First N/A (messaging protocol; local friend/key data stored per client but protocol is live-connection oriented)
E2EE Yes (NaCl crypto_box for all message encryption; xsalsa20 symmetric encryption + poly1305 authentication; keys are user identity)
CRDTs Lib N/A (messaging protocol; no shared mutable state requiring CRDTs)
Byzantine Fault Tolerance No (DHT provides eventual consistency; no formal Byzantine consensus mechanism)
Signature Curve25519 / Ed25519 (NaCl keypairs; 256-bit public key serves as Tox ID; friend requests use onion-routed signed introductions)
Permissions Key-based (contact requires knowing Tox ID / public key + explicit friend acceptance; no central permission authority)
Semantic Web Compatibility N/A (binary messaging protocol; no RDF or linked data features)
Smart Contract No
Protocol Stack Position
Asset / Value Embedding None — Tox is a serverless communications protocol with no native token or value layer.
Protocol Maturity / Standardization Community Standard (open protocol specification at zetok.github.io/tox-spec; multiple independent client implementations; not submitted to formal standards body; no third-party security audit completed as of 2026)