iCash Core staging tree 0.11
Copyright (c) 2009-2015 Bitcoin Core Developers
Copyright (c) 2014-2015 iCash Core Developers
What is iCash?
iCash is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. iCash uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. iCash Core is the name of open source software which enables the use of this currency.
For more information, as well as an immediately useable, binary version of the iCash Core software, see http://www.icashpay.io/downloads.
compiling iCash from git
Use the autogen script to prepare the build environment.
./autogen.sh ./configure make
Precompiled binaries are available at github, see https://github.com/icashproject/icash-binaries
Always verify the signatures and checksums.
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 icashs" 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.
iCash 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.