91be5e3c1e
ff274d3[doc] Add hint about getmempoolentry to getrawmempool help. (Karl-Johan Alm)76f9cf9contrib: Update location of seeds.txt (Wladimir J. van der Laan)12adedfTrivial: remove extra character from comment (CryptAxe)d2ec969Fixed typo in documentation for merkleblock.h (Mikerah)3612219contrib/init/bitcoind.openrcconf: Don't disable wallet by default (Luke Dashjr)692dbb0[doc] Minor corrections to osx dependencies (fanquake)87a21d5Fix: make CCoinsViewDbCursor::Seek work for missing keys (Pieter Wuille)28b8b8b[wallet] Securely erase potentially sensitive keys/values (Thomas Snider)ff13f59[wallet] Make sure pindex is non-null before possibly referencing in LogPrintf call. (Karl-Johan Alm)e23cef0Fix some empty vector references (Pieter Wuille)6ad45b8Re-enable upnp support in contrib/debian (Matt Corallo)e9a0d89Build with QT5 on Debian-based systems using contrib/debian (Matt Corallo)2ea0358Bump minimum boost version in contrib/debian (Matt Corallo)c94e262Update contrib/debian to latest Ubuntu PPA upload. (Matt Corallo)96c7f2cAdd CheckQueue Tests (Jeremy Rubin)e207342Fix CCheckQueue IsIdle (potential) race condition and remove dangerous constructors. (Jeremy Rubin)ef810c4[trivial] Fix a typo (introduced two days ago) in the default fee warning (practicalswift)7abe7bbQt/Send: Give fallback fee a reasonable indent (Luke Dashjr)3e4d7bfQt/Send: Figure a decent warning colour from theme (Luke Dashjr)c5adf8f[Qt] Show more significant warning if we fall back to the default fee (Jonas Schnelli)ee1a60d[tests] update disconnect_ban.py test case to work with listbanned (John Newbery)d289b56[net] listbanned RPC and QT should show correct banned subnets (John Newbery)0422693[tests] disconnect_ban: remove dependency on urllib (John Newbery)98bd0c3[tests] disconnect_ban: use wait_until instead of sleep (John Newbery)bfd1cf6[tests] disconnectban test - only use two nodes (John Newbery)5bc75bb[tests] fix nodehandling.py flake8 warnings (John Newbery)c25d0a8Update release notes to include RPC error code changes. (John Newbery)f5efe82Return correct error codes in fundrawtransaction(). (John Newbery)4943d7aReturn correct error codes in setban(). (John Newbery)18c109dReturn correct error codes in removeprunedfunds(). (John Newbery)fe51c89Return correct error codes in blockchain.cpp. (John Newbery)3ad00b4Return correct error codes in bumpfee(). (John Newbery)71463a7[qa] Test prioritise_transaction / getblocktemplate interaction (Suhas Daftuar)d28d583Bugfix: PrioritiseTransaction updates the mempool tx counter (Suhas Daftuar) Tree-SHA512: fa3628527c8e176e438de992b9c5815cc2f3c296dbe5d81b592d17a907554e9c6af7eb595e96a2c345de399ba5326c07b4791a91b7b07f89dce0787c85891206
Bitcoin Core integration/staging tree
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.