The Tao blockchain core reference protocol.
Switch branches/tags
Nothing to show
Clone or download
Failed to load latest commit information.
build Initial commit. Aug 28, 2016
contrib MocOS fixes Sep 29, 2018
doc Update Aug 22, 2018
html5 HTML5 wallet framework Oct 27, 2018
share Windows build fixes. Feb 22, 2018
src Taking back TAO Oct 12, 2018
.travis.yml Travis CI fix Sep 26, 2018
CHANGELOG Initial commit. Aug 28, 2016
COPYING Initial commit. Aug 28, 2016
INSTALL Changed 'tao-daemon' to 'taod' Sep 17, 2016
README Initial commit. Aug 28, 2016 Travis CI fix Sep 26, 2018 MocOS fixes Sep 29, 2018
contributors.txt Initial commit with contributors Aug 28, 2016

Tao Core integration/staging tree Travis-CI

What is the Tao Blockchain?

The Tao Blockchain is an experimental smart contract platform protocol that enables instant payments to anyone, anywhere in the world in a private, secure manner. Tao uses peer-to-peer blockchain technology developed by Bitcoin to operate with no central authority: managing transactions, execution of contracts, and issuing money are carried out collectively by the network. Tao Core is the name of open source software which enables the use of this protocol.

For more information, see, or read the original whitepaper.

Building the wallet

A simple guide for building the linux wallet is located here

Autonode Generator

To automatically setup and install Linux Tao nodes, run the following command as root.

wget -O ; sudo bash


Tao Core is released under the terms of the MIT license. See COPYING for more information or see

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Tao Core.

The contribution workflow is described in

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer Slack can be found at


Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.