The future of online communications.
C C++ M4 CMake Shell Makefile Other
Pull request Compare This branch is 259 commits ahead of irungentoo:master.
Latest commit 5ad3c98 Jan 16, 2017 @iphydf iphydf Make building `DHT_bootstrap` in cmake optional.
It's enabled by default.
Failed to load latest commit information.
auto_tests Set up autotools build to build against vanilla NaCl. Jan 8, 2017
build Fix include paths Jan 2, 2016
cmake Add soversion to library files to generate proper symlinks Jan 8, 2017
dist-build Removed unnecessary parameters Aug 25, 2014
docs Rebuild apidsl'd headers in cmake. Oct 2, 2016
m4 Build system now automatically enables epoll support in TCP server Jul 18, 2014
other Fix NaCl build: tar was called incorrectly. Jan 8, 2017
super_donators Added my pixfile! Dec 12, 2015
testing Fixed FreeBSD build failure due to undefined MSG_NOSIGNAL. Jan 13, 2017
toxav Use after free reported in #278 occurs because toxav_kill() Dec 20, 2016
toxcore Release v0.1.4. Jan 12, 2017
toxdns Wrap all sodium/nacl functions in crypto_core.c. Dec 22, 2016
toxencryptsave Clarify that the pass key `new` function can fail. Jan 12, 2017
.gitignore Revert "Revert "Portability fixes"" Jan 6, 2017
.travis.yml Don't use `git.depth=1` anymore. Jan 7, 2017
CMakeLists.txt Make building `DHT_bootstrap` in cmake optional. Jan 16, 2017
COPYING Removed the unused autotools files Oct 5, 2015
DONATORS If we receive a packet from a node we are searching for, ping it. Dec 8, 2015 docs(INSTALL): Bring back autotools instructions Jan 5, 2017 Fixed make dist. Jun 25, 2015 Update readme, moved the roadmap to a higher position Oct 17, 2016 Fix file modes Oct 14, 2015
circle.yml Add CircleCI Support Jan 3, 2017 Release v0.1.4. Jan 12, 2017 Build system fixes. Dec 18, 2014 Move -ltoxcore to be the first linked library Dec 12, 2016 Add spec file for rpm generation Mar 3, 2015

Project Tox

Current build status: Build Status Current Coverage: Coverage Status

Website | Wiki | Blog | FAQ | Binaries/Downloads | Clients | Compiling

IRC Channels: Users: #tox@freenode, Developers: #toktok@freenode

Toxcore Development Roadmap

This Roadmap is somewhat tentative, but should give you a good idea of where we're going, and where we've been.

Currently unsorted, the following is intended to function as a discussion guide to developers/contributors.

In Progress

  • Toxcore
    • 100% unit testing
    • Make ToxAV stateless
    • Allow a single toxcore instance to handle multiple keypairs (or 'clients')
    • Consistent naming scheme throughout toxcore
    • Make toxcore stateless
  • Messenger
    • Improve group chat implementation
    • Improve A/V implementation
    • Multiple device support


  • Create Toxcore
  • Create DHT
  • Create Onion
  • Implement Crypto
  • Create Messenger


What is Tox?

Tox is a fully encrypted, censor resistant, private, distributed network library with a focus on personal communications.

No, really, what's Tox?

It's a VERY secure Instant Messenger that supports Text, Audio/Video calls, group chats, audio group chats, and file transfers. There's dozens, but our advantage is we put security first, from day 1. We didn't decide to add it in after.

What are your goals with Tox?

We want Tox to be as simple as possible while remaining as secure as possible.


The Complex Stuff:


Tox must use UDP simply because hole punching with TCP is not as reliable. However, Tox does use TCP relays as a fallback if it encounters a firewall that prevents UDP hole punching.

Connecting & Communicating

Every peer is represented as a byte string (the public key [Tox ID] of the peer). By using torrent-style DHT, peers can find the IP of other peers by using their Tox ID. Once the IP is obtained, peers can initiate a secure connection with each other. Once the connection is made, peers can exchange messages, send files, start video chats, etc. using encrypted communications.