a339289c2e
d4a1ee8f1dFurther improve comments around recentRejects (Suhas Daftuar)f082a13ab7Disconnect peers sending wtxidrelay message after VERACK (Suhas Daftuar)22effa51a7test: Use wtxid relay generally in functional tests (Fabian Jahr)e481681963test: Add tests for wtxid tx relay in segwit test (Fabian Jahr)6be398b6fbtest: Update test framework p2p protocol version to 70016 (Fabian Jahr)e364b2a2d8Rename AddInventoryKnown() to AddKnownTx() (Suhas Daftuar)879a3cf2c2Make TX_WITNESS_STRIPPED its own rejection reason (Suhas Daftuar)c1d6a1003dDelay getdata requests from peers using txid-based relay (Suhas Daftuar)181ffadd16Add p2p message "wtxidrelay" (Suhas Daftuar)93826726e7ignore non-wtxidrelay compliant invs (Anthony Towns)2599277e9cAdd support for tx-relay via wtxid (Suhas Daftuar)be1b7a8916Add wtxids to recentRejects (Suhas Daftuar)73845211d1Add wtxids of confirmed transactions to bloom filter (Suhas Daftuar)606755b840Add wtxid-index to orphan map (Suhas Daftuar)3654937674Add a wtxid-index to mapRelay (Suhas Daftuar)f7833b5bd8Just pass a hash to AddInventoryKnown (Suhas Daftuar)4df3d139b7Add a wtxid-index to the mempool (Suhas Daftuar) Pull request description: We want wtxid relay to be widely deployed before taproot activation, so it should be backported to v0.20. The main difference from #18044 is removing the changes to the unbroadcast set (which was only added post-v0.20). The rest is mostly minor rebase conflicts (eg connman changed from a pointer to a reference in master, etc). We'll also want to backport #19569 after that's merged. ACKs for top commit: fjahr: re-ACKd4a1ee8f1dinstagibbs: reACKd4a1ee8f1dlaanwj: re-ACKd4a1ee8f1dhebasto: re-ACKd4a1ee8f1d, only rebased since my [previous](https://github.com/bitcoin/bitcoin/pull/19606#pullrequestreview-492763028) review: Tree-SHA512: 1bb8725dd2313a9a03cacf8fb7317986eed3d8d1648fa627528441256c37c793bb0fae6c8c139d05ac45d0c7a86265792834e8e09cbf45286426ca6544c10cd5
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 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.