6df70d30b1
- Fixed a few issues when calculating progress including some variables that should be limited to 1 (a and b). GetDenominatedBalance also seemed to be giving bad results so I rewrote it to be cleaner, not sure if that was a part of the problem. - Progress bar is only recalculated when all inputs in wallet have been confirmed (will stop the progress from jumping around) |
||
|---|---|---|
| .tx | ||
| contrib | ||
| depends | ||
| doc | ||
| qa | ||
| share | ||
| src | ||
| .gitattributes | ||
| .gitignore | ||
| autogen.sh | ||
| configure.ac | ||
| COPYING | ||
| INSTALL | ||
| Makefile.am | ||
| pkg.m4 | ||
| README.md | ||
Darkcoin Core staging tree 0.11
Copyright (c) 2009-2014 Bitcoin Core Developers
Copyright (c) 2014 Darkcoin Core Developers
What is Darkcoin?
Darkcoin is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. Darkcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Darkcoin 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 Darkcoin Core software, see http://www.darkcoin.io/downloads.
License
Darkcoin 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 Darkcoin from git
Use the autogen script to prepare the build environment.
./autogen.sh
./configure
make
precompiled binaries
Precompiled binaries are available at github, see https://github.com/darkcoinproject/darkcoin-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.
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 darkcoins" 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 -regest mode.
DEBUG_LOCKORDER
Darkcoin 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.