Bitcoin Core integration/staging tree
Go to file
Luke Dashjr 0388afe69d Let autoconf detect presence of EVP_MD_CTX_new
Fixes LibreSSL compatibility
2017-01-04 18:37:37 +00:00
.github Mention reporting security issues responsibly 2016-11-10 14:41:40 +01:00
.tx tx: change slug to bitcoin.qt-translation-013x 2016-06-28 11:49:30 +02:00
build-aux/m4 [build-aux] Boost_Base serial 27 2016-10-17 11:43:24 +08:00
contrib Merge #8996: Network activity toggle 2016-11-11 11:16:40 +01:00
depends [depends] Set OSX_MIN_VERSION to 10.8 2016-11-09 18:55:04 +08:00
doc Developer docs about existing subtrees. 2016-12-02 14:34:20 +00:00
qa Merge #9309: [qa] Wallet needs to stay unlocked for whole test 2016-12-10 18:47:36 +01:00
share [copyright] copyright header style uniform 2016-11-06 10:12:50 -07:00
src Let autoconf detect presence of EVP_MD_CTX_new 2017-01-04 18:37:37 +00:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore remove obsolete run-bitcoind-for-test.sh 2016-12-04 15:44:41 -05:00
.travis.yml Squashed 'src/leveldb/' changes from 20ca81f..a31c8aa 2016-12-01 16:14:45 -08:00
autogen.sh Add MIT license to autogen.sh and share/genbuild.sh 2016-09-21 23:01:36 +00:00
configure.ac Let autoconf detect presence of EVP_MD_CTX_new 2017-01-04 18:37:37 +00:00
CONTRIBUTING.md Add copyright/patent issues to possible NACK reasons 2016-10-13 19:47:43 +02:00
COPYING Update license year range to 2016 2016-01-17 23:38:11 +05:30
INSTALL.md Update INSTALL landing redirection notice for build instructions. 2016-10-06 12:27:23 +13:00
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes 2015-12-14 02:11:10 +00:00
Makefile.am Merge #8568: new var DIST_CONTRIB adds useful things for packagers from contrib 2016-11-07 13:06:47 +01:00
README.md Squashed 'src/leveldb/' changes from 20ca81f..a31c8aa 2016-12-01 16:14:45 -08:00

Bitcoin Core integration/staging tree

Build Status

https://bitcoincore.org

What is Bitcoin?

Bitcoin is an experimental 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 https://bitcoin.org/en/download, or read the original whitepaper.

License

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

Development Process

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

The contribution workflow is described in CONTRIBUTING.md.

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #bitcoin-core-dev.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, 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. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Translations

Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also subscribe to the mailing list.