3caee16946
0e2a5e448ftests: dumping and minimizing of script assets data (Pieter Wuille)4567ba034ctests: add generic qa-asset-based script verification unit test (Pieter Wuille)f06e6d0345tests: functional tests for Schnorr/Taproot/Tapscript (Pieter Wuille)3c226639ebtests: add BIP340 Schnorr signature support to test framework (Pieter Wuille)206fb180ec--- [TAPROOT] Tests --- (Pieter Wuille)d7ff237f29Activate Taproot/Tapscript on regtest (BIP 341, BIP 342) (Pieter Wuille)e9a021d7e6Make Taproot spends standard + policy limits (Pieter Wuille)865d2c37e2--- [TAPROOT] Regtest activation and policy --- (Pieter Wuille)72422ce396Implement Tapscript script validation rules (BIP 342) (Johnson Lau)330de894a9Use ScriptExecutionData to pass through annex hash (Pieter Wuille)8bbed4b7acImplement Taproot validation (BIP 341) (Pieter Wuille)0664f5fe1fSupport for Schnorr signatures and integration in SignatureCheckers (BIP 340) (Pieter Wuille)5de246ca81Implement Taproot signature hashing (BIP 341) (Johnson Lau)9eb590894fAdd TaggedHash function (BIP 340) (Pieter Wuille)450d2b2371--- [TAPROOT] BIP340/341/342 consensus rules --- (Pieter Wuille)5d62e3a68brefactor: keep spent outputs in PrecomputedTransactionData (Pieter Wuille)8bd2b4e784refactor: rename scriptPubKey in VerifyWitnessProgram to exec_script (Pieter Wuille)107b57df9fscripted-diff: put ECDSA in name of signature functions (Pieter Wuille)f8c099e220--- [TAPROOT] Refactors --- (Pieter Wuille) Pull request description: This is an implementation of the Schnorr/taproot consensus rules proposed by BIPs [340](https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki), [341](https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki), and [342](https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki). See the list of commits [below](https://github.com/bitcoin/bitcoin/pull/19953#issuecomment-691815830). No signing or wallet support of any kind is included, as testing is done entirely through the Python test framework. This is a successor to https://github.com/bitcoin/bitcoin/pull/17977 (see discussion following [this comment](https://github.com/bitcoin/bitcoin/pull/17977#issuecomment-682285983)), and will have further changes squashed/rebased. The history of this PR can be found in #19997. ACKs for top commit: instagibbs: reACK0e2a5e448fbenthecarman: reACK0e2a5e4kallewoof: reACK0e2a5e448fjonasnick: ACK0e2a5e448falmost only looked at bip340/libsecp related code jonatack: ACK0e2a5e448fmodulo the last four commits (tests) that I plan to finish reviewing tomorrow fjahr: reACK0e2a5e448fachow101: ACK0e2a5e448fTree-SHA512: 1b00314450a2938a22bccbb4e177230cf08bd365d72055f9d526891f334b364c997e260c10bc19ca78440b6767712c9feea7faad9a1045dd51a5b96f7ca8146e
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 usable, 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 (see doc/build-*.md for instructions) and tested, but it is not guaranteed to be
completely stable. Tags are created
regularly from release branches to indicate new official, stable release versions of Bitcoin Core.
The https://github.com/bitcoin-core/gui repository is used exclusively for the development of the GUI. Its master branch is identical in all monotree repositories. Release branches and tags do not exist, so please do not fork that repository unless it is for development reasons.
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.