254e990ce5
b70b4a2Trivial: Fix typo (Marty Jones)702fd2e[copyright] add MIT license headers to .sh scripts where missing (isle2983)a60d7cc[copyright] Add missing copyright headers (isle2983)ea2a6be[copyright] add MIT License copyright header to remaining Python files (isle2983)9a903f9[copyright] add MIT License copyright header to zmq_sub.py (isle2983)084cae9UndoReadFromDisk works on undo files (rev), not on block files. (Pavel Janík)e34374e[qa] wallet: Check legacy wallet as well (MarcoFalke)d31ac72Specify Protobuf version 2 in paymentrequest.proto (fanquake)5e15fceMinor change in section name (Anders Øyvind Urke-Sætre)0e2c6bd[Doc] Target protobuf 2.6 in OS X build notes. (Michael Ford)da94272[qa] walletbackup: Sync blocks inside the loop (MarcoFalke)42ea51anet: No longer send local address in addrMe (Wladimir J. van der Laan)ea51b0fBerkeley DB v6 compatibility fix (Alexey Vesnin)0a35573[doc] - clarify statement about parallel jobs in rpc-tests.py (isle2983)752fbaecontrib: Make fix-copyright-headers.py more portable (MarcoFalke)486650a[doc] Fix typos in comments, doxygen: Fix comment syntax (MarcoFalke)c18a9ca[qa] pull-tester: Don't mute zmq ImportError (MarcoFalke)9556745init: Fix typo in help message for -whitelistforcerelay (Wladimir J. van der Laan)4f84082Set jonasschnellis dns-seeder filter flag (Jonas Schnelli)863ae74[doc] Update git-subtree-check.sh README (MarcoFalke)c493f43Trivial: Fix two VarInt examples in serialize.h (Christian Barcenas)cb07f19CDB: fix debug output (crowning-)75d5484Add copyright header to wallet_text_fixture.cpp (Wladimir J. van der Laan)305d8acUse __func__ to get function name for output printing (MarcoFalke)464dedd[Wallet] Trivial cleanup of HD wallet changes (Jonas Schnelli)b17a3f9document return value of networkhashps for getmininginfo RPC endpoint (Jameson Lopp)a27cdd8[qa] abandonconflict: Use assert_equal (MarcoFalke)befe654various typos (leijurv)4e5fc31Fix a type error that would not compile on Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) (Jeremy Rubin)156e305Corrected JSON typo on setban of net.cpp (Sev)fa5b249Bugfix: Allow building libbitcoinconsensus without any univalue (Luke Dashjr)8b0bdd3configure: Allow building bench_bitcoin by itself (Luke Dashjr)749c8a5[doc] typos, READMEs, comments (Justin Camarena)fc34928Do diskspace check before import thread is started (Pieter Wuille)3b354d2Add extra message to avoid a long 'Loading banlist' (Pieter Wuille)30eac2dUse a signal to continue init after genesis activation (Pieter Wuille)9b00979Update README.md (Chris Stewart)8bb1efd[qa] Rework hd wallet dump test (MarcoFalke)a7aa3ccEnable size accounting in mining unit tests (Suhas Daftuar)bea02dc[qa]: enable rpcbind_test (whythat)e111904[qa]: add parsing for '<host>:<port>' argument form to rpc_url() (whythat)69d1cd2net: Ignore `notfound` P2P messages (Wladimir J. van der Laan)f70be14[QA] Add walletdump RPC test (including HD- & encryption-tests) (Jonas Schnelli)1f21d16prepend license statement to indirectmap (Kaz Wesley)03b0196Fix obvious assignment/equality error in test (Jeremy Rubin)8a7d7ffupdate name of file bitcoin.qrc (Gaurav Rana)147003cAdd configure check for -latomic (Anthony Towns)091cdebClear witness with vin/vout in CWallet::CreateTransaction() (Suhas Daftuar)8e03382[Qt][CoinControl] fix UI bug that could result in paying unexpected fee (Jonas Schnelli)6b07362Fix SIGHASH_SINGLE bug in test_framework SignatureHash (Johnson Lau)a114a02p2psegwit.py transaction is rejected due to premature witness not size (instagibbs)3606b6bUpdate p2p-segwit.py to reflect correct AskFor behavior (instagibbs)733760aUpdate btcdrak signing key (BtcDrak)c6a6291add witness address to address book (instagibbs)
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
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.