dash/README.md

84 lines
2.6 KiB
Markdown
Raw Normal View History

2014-12-12 13:05:25 +01:00
Darkcoin Core staging tree 0.11
===============================
2014-12-12 12:09:19 +01:00
http://www.darkcoin.io
2015-01-12 10:33:39 +01:00
Copyright (c) 2009-2015 Bitcoin Core Developers
2014-12-12 13:05:25 +01:00
2015-01-12 11:23:07 +01:00
Copyright (c) 2014-2015 Darkcoin Core Developers
2014-12-12 12:09:19 +01:00
What is Darkcoin?
----------------
2014-12-12 12:09:19 +01:00
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
2014-12-12 12:09:19 +01:00
the Darkcoin Core software, see http://www.darkcoin.io/downloads.
License
-------
2014-12-12 12:09:19 +01:00
Darkcoin Core is released under the terms of the MIT license. See [COPYING](COPYING) for more
information or see http://opensource.org/licenses/MIT.
2010-09-23 20:06:50 +02:00
2011-09-27 04:22:19 +02:00
2014-12-12 12:09:19 +01:00
Building process
-----------------
2014-12-12 12:09:19 +01:00
**compiling Darkcoin from git**
2014-12-12 12:09:19 +01:00
Use the autogen script to prepare the build environment.
2014-12-12 12:09:19 +01:00
./autogen.sh
./configure
make
2014-12-12 12:09:19 +01:00
**precompiled binaries**
2014-12-12 12:09:19 +01:00
Precompiled binaries are available at github, see
https://github.com/darkcoinproject/darkcoin-binaries
2014-12-12 12:09:19 +01:00
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**
2014-12-12 12:09:19 +01:00
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
2015-02-25 09:37:47 +01:00
that run in -regtest mode.
**DEBUG_LOCKORDER**
2014-12-12 12:09:19 +01:00
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.