sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-24 19:42:46 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
Dash - Reinventing Cryptocurrency
5,126 Commits 24 Branches 554 Tags 573 MiB
C++ 52.7%
C 24.2%
Python 10.5%
Assembly 3.3%
JavaScript 2.6%
Other 6.5%
490d6a3046
Go to file
Wladimir J. van der Laan 490d6a3046
Merge pull request #3545 
1cbbeb6 gitian: Add openssl to linux deps (Wladimir J. van der Laan)
64be7f7 gitian: Build boost dependency for linux (Wladimir J. van der Laan)
7eb99a8 gitian: Reduce build time for boost windows dependency (Wladimir J. van der Laan)
714cdec build: Pass BOOST_CPPFLAGS to sleep implementation test (Wladimir J. van der Laan)
0d40f5a build: Allow providing extra libs for Boost Chrono (Wladimir J. van der Laan)
e4b991e build: Auto-detect whether -DBOOST_TEST_DYN_LINK is needed (Wladimir J. van der Laan)
2014-01-18 16:02:31 +01:00
contrib Merge pull request #3545 2014-01-18 16:02:31 +01:00
doc Merge pull request #3545 2014-01-18 16:02:31 +01:00
qa qt5: fix --with-qt with no arguments 2014-01-10 16:30:33 -05:00
share qt: Update remaining "The Bitcoin Core Developers" 2014-01-14 11:19:52 +01:00
src Merge src/leveldb changes: temporarily revert to writing .sst files. 2014-01-18 14:32:29 +01:00
.gitattributes Build identification strings 2012-04-10 18:16:53 +02:00
.gitignore src/leveldb/Makefile is ignored? 2014-01-13 18:37:57 +08:00
autogen.sh autogen.sh: Stop passing --verbose to autoreconf 2013-11-27 17:29:00 -08:00
configure.ac Merge pull request #3545 2014-01-18 16:02:31 +01:00
COPYING Bump version numbers for 0.8 release 2013-01-30 14:19:09 -05:00
INSTALL Prettify some /Contrib READMEs 2013-10-21 20:07:31 -04:00
Makefile.am Fix port binding by listening on port $BASHPID 2013-10-28 03:43:09 -04:00
pkg.m4 autotools: switch to autotools buildsystem 2013-09-05 21:31:03 -04:00
README.md Fix heading in README.md 2013-12-17 11:51:49 +01:00

README.md

Bitcoin Core integration/staging tree

http://www.bitcoin.org

Copyright (c) 2009-2013 Bitcoin Core Developers

What is Bitcoin?

Bitcoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin 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 Bitcoin Core software, see http://www.bitcoin.org/en/download.

License

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

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the Bitcoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/coding.md) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Bitcoin.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check

Every pull request is built for both Windows and Linux on a dedicated server, and unit and sanity tests are automatically run. The binaries produced may be used for manual QA testing — a link to them will appear in a comment on the pull request posted by BitcoinPullTester. See https://github.com/TheBlueMatt/test-scripts for the build/test scripts.

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code. See https://github.com/bitcoin/QA/ for how to create a test plan.