629c7b029c
bcb27d7b0.python-version: Bump to 3.5.6 (MarcoFalke)af25a757eAdd comments to Python ECDSA implementation (John Newbery)715da91e9Set AA_EnableHighDpiScaling attribute early (Hennadii Stepanov)2800b3d5cgui: Fix open wallet menu initialization order (João Barbosa)e78007fc1Make and get the multisig redeemscript and destination in one function instead of two (Andrew Chow)d9fc969e7Pure python EC (Pieter Wuille)23ba460c1test: Add test that addmultisigaddress fails for watchonly addresses (MarcoFalke)13b3bb564test: Fixup creatmultisig documentation and whitespace (MarcoFalke)79745d175Replace remaining fprintf with tfm::format manually (MarcoFalke)beb09f09bscripted-diff: Replace fprintf with tfm::format (MarcoFalke)e29aa6e72Exceptions should be caught by reference, not by value. (Kristaps Kaupe)f88959ba7tinyformat: Add doc to Bitcoin Core specific strprintf (MarcoFalke)0023c9789rpc: bugfix: Properly use iswitness in converttopsbt (MarcoFalke)832eb4ff5Bugfix: test/functional/rpc_psbt: Correct test description comment (Luke Dashjr)966d8d084Bugfix: test/functional/rpc_psbt: Remove check for specific error message that depends on uncertain assumptions (Luke Dashjr)bb36ac82erpc: Switch touched RPCs to IsValidNumArgs (MarcoFalke)d24d0ec05Add example 2nd arg to signrawtransactionwithkey (Chris Moore)592016ba1fixup: Fix prunning test (João Barbosa)c80a498aeFix RPC/pruneblockchain returned prune height (Jonas Schnelli)b2398240fgui: Enable open wallet menu on setWalletController (João Barbosa)d1f261150Add test for GCC bug 90348 (Pieter Wuille)d80c558e0gui: Set progressDialog to nullptr (João Barbosa)7ed1a6019gui: Enable console line edit on setClientModel (João Barbosa)b55cbe82dqt: fix opening bitcoin.conf via Preferences on macOS; see #15409 (shannon1916)b6c1f9478Disallow extended encoding for non-witness transactions (take 3) (MarcoFalke)86031083cAdd test for superfluous witness record in deserialization (Gregory Sanders)5a58ddb6dFix missing input template by making minimal tx (Gregory Sanders)206f5ee87Disallow extended encoding for non-witness transactions (Pieter Wuille)3dbc7def0Show loaded wallets as disabled in open menu instead of nothing (MeshCollider)a635377b6Install bitcoin-wallet manpage. (Daniel Kraft)eb85ee62bDoc: remove text about txes always relayed from -whitelist (David A. Harding)890a92ebadoc: Mention blocksonly in reduce-traffic.md, unhide option (MarcoFalke)3460555f4test: Add test for p2p_blocksonly (MarcoFalke)8f215c7a2test: Format predicate source as multiline on error (MarcoFalke)9c1a607a0net: Rename ::fRelayTxes to ::g_relay_txes (MarcoFalke)5935f0126build with -fstack-reuse=none (MarcoFalke) Pull request description: Tree-SHA512: 5cd73a4319cb69c92b528239cf97c0ed5fcf2b9e8c7fe154e4679eeec95db433a0223d8dc574e4cdc96c1913cfdf160b10c42dcdbcb5bbc8fb743c07930ef9da
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://bitcoincore.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 and useful hints for developers can be found in doc/developer-notes.md.
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, written
in Python, that are run automatically on the build server.
These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py
The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, 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.