1- Bitcoin Core integration/ staging tree
2- =====================================
1+ Darkcoin Core staging tree 0.11
2+ ===============================
33
4- http://www.bitcoin.org
4+ http://www.darkcoin.io
55
66Copyright (c) 2009-2014 Bitcoin Core Developers
77
8- What is Bitcoin?
8+ Copyright (c) 2014 Darkcoin Core Developers
9+
10+
11+ What is Darkcoin?
912----------------
1013
11- Bitcoin is an experimental new digital currency that enables instant payments to
12- anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate
13- with no central authority: managing transactions and issuing money are carried
14- out collectively by the network. Bitcoin Core is the name of open source
15- software which enables the use of this currency.
14+ Darkcoin is an experimental new digital currency that enables anonymous, instant
15+ payments to anyone, anywhere in the world. Darkcoin uses peer-to-peer technology
16+ to operate with no central authority: managing transactions and issuing money
17+ are carried out collectively by the network. Darkcoin Core is the name of open
18+ source software which enables the use of this currency.
1619
1720For more information, as well as an immediately useable, binary version of
18- the Bitcoin Core software, see http://www.bitcoin.org/en/download .
21+ the Darkcoin Core software, see http://www.darkcoin.io/downloads .
22+
1923
2024License
2125-------
2226
23- Bitcoin Core is released under the terms of the MIT license. See [ COPYING] ( COPYING ) for more
27+ Darkcoin Core is released under the terms of the MIT license. See [ COPYING] ( COPYING ) for more
2428information or see http://opensource.org/licenses/MIT .
2529
26- Development process
27- -------------------
28-
29- Developers work in their own trees, then submit pull requests when they think
30- their feature or bug fix is ready.
31-
32- If it is a simple/trivial/non-controversial change, then one of the Bitcoin
33- development team members simply pulls it.
34-
35- If it is a * more complicated or potentially controversial* change, then the patch
36- submitter will be asked to start a discussion (if they haven't already) on the
37- [ mailing list] ( http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development ) .
38-
39- The patch will be accepted if there is broad consensus that it is a good thing.
40- Developers should expect to rework and resubmit patches if the code doesn't
41- match the project's coding conventions (see [ doc/coding.md] ( doc/coding.md ) ) or are
42- controversial.
43-
44- The ` master ` branch is regularly built and tested, but is not guaranteed to be
45- completely stable. [ Tags] ( https://github.com/bitcoin/bitcoin/tags ) are created
46- regularly to indicate new official, stable release versions of Bitcoin.
47-
48- Testing
49- -------
50-
51- Testing and code review is the bottleneck for development; we get more pull
52- requests than we can review and test. Please be patient and help out, and
53- remember this is a security-critical project where any mistake might cost people
54- lots of money.
55-
56- ### Automated Testing
5730
58- Developers are strongly encouraged to write unit tests for new code, and to
59- submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: ` make check `
31+ Building process
32+ -----------------
6033
61- Every pull request is built for both Windows and Linux on a dedicated server,
62- and unit and sanity tests are automatically run. The binaries produced may be
63- used for manual QA testing — a link to them will appear in a comment on the
64- pull request posted by [ BitcoinPullTester] ( https://github.com/BitcoinPullTester ) . See https://github.com/TheBlueMatt/test-scripts
65- for the build/test scripts.
34+ ** compiling Darkcoin from git**
6635
67- ### Manual Quality Assurance (QA) Testing
36+ Use the autogen script to prepare the build environment.
6837
69- Large changes should have a test plan, and should be tested by somebody other
70- than the developer who wrote the code.
71- See https://github.com/bitcoin/QA/ for how to create a test plan.
38+ ./autogen.sh
39+ ./configure
40+ make
7241
73- Translations
74- ------------
42+ ** precompiled binaries**
7543
76- Changes to translations as well as new translations can be submitted to
77- [ Bitcoin Core's Transifex page ] ( https://www.transifex. com/projects/p/bitcoin/ ) .
44+ Precompiled binaries are available at github, see
45+ https://github. com/darkcoinproject/darkcoin-binaries
7846
79- Periodically the translations are pulled from Transifex and merged into the git repository. See the
80- [ translation process] ( doc/translation_process.md ) for details on how this works.
47+ Always verify the signatures and checksums.
8148
82- ** Important** : We do not accept translation changes as github pull request because the next
83- pull from Transifex would automatically overwrite them again.
8449
8550Development tips and tricks
8651---------------------------
@@ -103,7 +68,7 @@ to see it.
10368
10469** testnet and regtest modes**
10570
106- Run with the -testnet option to run with "play bitcoins " on the test network, if you
71+ Run with the -testnet option to run with "play darkcoins " on the test network, if you
10772are testing multi-machine code that needs to operate across the internet.
10873
10974If you are testing something that can run on one machine, run with the -regtest option.
@@ -112,7 +77,7 @@ that run in -regest mode.
11277
11378** DEBUG_LOCKORDER**
11479
115- Bitcoin Core is a multithreaded application, and deadlocks or other multithreading bugs
80+ Darkcoin Core is a multithreaded application, and deadlocks or other multithreading bugs
11681can be very difficult to track down. Compiling with -DDEBUG_LOCKORDER (configure
11782CXXFLAGS="-DDEBUG_LOCKORDER -g") inserts run-time checks to keep track of what locks
11883are held, and adds warning to the debug.log file if inconsistencies are detected.
0 commit comments