Skip to content

bitnodes/bitnodespro

Repository files navigation

BitNodesPro Core staging tree

Copyright (c) 2009-2017 Bitcoin Core Developers

Copyright (c) 2014-2017 Dash Core Developers

Copyright (c) 2017-2018 BitNodes Project Developers

What is BitNodesPro?

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

License

BitNodesPro Core is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.

Building process

compiling BitNodesPro from git

Use the autogen script to prepare the build environment.

./autogen.sh
./configure
make

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.

debug.log

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 bitnodespro" 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.

DEBUG_LOCKORDER

BitNodesPro 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.