Tox

Summary

Tox is a peer-to-peer messaging protocol implemented by a core library and client applications. Contacts exchange a Tox ID, rather than registering with a central messaging server. The official FAQ describes default end-to-end encryption and direct communication between contacts.

How it works

Bootstrap nodes help a client find the distributed hash table. Tox uses that network for discovery and libsodium cryptography for encrypted communication. Bootstrap infrastructure is a discovery dependency, not a central account service.

Trust model / threat model

The FAQ is explicit: Tox does not hide your IP address from friends you communicate with. An encrypted peer-to-peer connection is not an anonymity network. Check whom you add, protect your local identity keys, and compare Jami and the messenger comparison.

Readiness

Experimental. The canonical c-toxcore repository calls it an experimental cryptographic network library, says it has not received a formal independent cryptographic audit, and says its security model is not fully specified. Available clients do not remove that limitation.

Limits

Client behaviour and the underlying protocol are separate things to evaluate. Do not choose Tox on the assumption that removing a central server hides communication relationships or provides an independently validated security design.

Primary sources

• Tox FAQ: identities, discovery, encryption and IP exposure.
• Canonical Tox core and its security warning.