Bleeding edge, expect it to break.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
build-aux/m4 Merge remote-tracking branch 'bitcoin/0.12' into mergebtc12, fix/dashify Aug 26, 2016
contrib Inital Commit Sep 18, 2017
depends Interzone 1.4 w/Masternode Adjustments Sep 10, 2017
share Inital Commit Sep 18, 2017
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore update gitignore Apr 17, 2016
.travis.yml [Build] Re-include Windows/wine test into Travis build (#1137) Nov 8, 2016 Checkpoints Oct 4, 2017
INSTALL Inital Commit Sep 18, 2017 Initial Commit Sep 3, 2017 Initial Commit Sep 3, 2017 libbitcoinconsensus: Add pkg-config support Nov 20, 2014

testInterzone Core staging tree

Copyright (c) 2009-2015 Bitcoin Core Developers

Copyright (c) 2014-2015 Dash Core Developers

Copyright (c) 2017-2018 testInterzone Core Developers

What is testInterzone?

testInterzone is an experimental new digital token that enables anonymous, instant transfers to anyone, anywhere in the world. testInterzone uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. testInterzone Core is the name of open source software which enables the use of this token.

For more information, as well as an immediately useable, binary version of the testInterzone Core software, see

Interzone is a community based project and there are no "Core Developers" in the traditional sense. Anyone is invited to submit code improvements or features. Please see for more information on how to fork and submit pull requests.


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

Building process

compiling testInterzone from git

Use the autogen script to prepare the build environment.


Development tips and tricks

compiling for debugging

Run configure with the --enable-debug option, then make. Or run configure with CXXFLAGS="-g -ggdb -O0" or whatever debug flags you need.


If the code is behaving strangely, take a look in the debug.log file in the data directory; error and debugging message are written there.

The -debug=... command-line option controls debugging; running with just -debug will turn on all categories (and give you a very large debug.log file).

The Qt code routes qDebug() output to debug.log under category "qt": run with -debug=qt to see it.

testnet and regtest modes

Run with the -testnet option to run with "play testinterzones" on the test network, if you are testing multi-machine code that needs to operate across the internet.

If you are testing something that can run on one machine, run with the -regtest option. In regression test mode blocks can be created on-demand; see qa/rpc-tests/ for tests that run in -regtest mode.


testInterzone Core is a multithreaded application, and deadlocks or other multithreading bugs can be very difficult to track down. Compiling with -DDEBUG_LOCKORDER (configure CXXFLAGS="-DDEBUG_LOCKORDER -g") inserts run-time checks to keep track of what locks are held, and adds warning to the debug.log file if inconsistencies are detected.