Skip to content


Switch branches/tags
This branch is 10 commits ahead of projectinterzone:master.

Latest commit



Failed to load latest commit information.
Latest commit message
Commit time

Interzone Core staging tree

master: Build Status

Copyright (c) 2009-2015 Bitcoin Core Developers

Copyright (c) 2014-2015 Dash Core Developers

Copyright (c) 2017-2018 Interzone Developers

What is Interzone?

Interzone is an experimental new digital token that enables anonymous, instant transfers to anyone, anywhere in the world. Interzone uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Interzone 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 Interzone client, 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.


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

By using Interzone, the Interzone Network, or the Interzone Client you are accepting 100% liability and responsibility for your ITZ and ITZ network connections. The project team for Interzone does not market or warranty Interzone and will make no claims or promises for future use or value. By utilizing the ITZ client, you acknowledge that this is experimental software and that you are realizing the risks and rewards inherent in using crypto-tokens.

Building process

compiling Interzone 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.


No packages published


  • C++ 68.8%
  • C 14.0%
  • M4 4.6%
  • Python 4.5%
  • Makefile 2.9%
  • Shell 1.8%
  • Other 3.4%