mirror of https://github.com/bitcoin/bitcoin.git synced 2025-03-05 14:06:27 -05:00

Bitcoin Core integration/staging tree

bitcoin c-plus-plus cryptocurrency cryptography p2p

Find a file

merge-script 94ca99ac51 Merge bitcoin/bitcoin#31666 : multi-peer orphan resolution followups `7426afbe62` [p2p] assign just 1 random announcer in AddChildrenToWorkSet (glozow) `4c1fa6b28c` test fix: make peer who sends MSG_TX announcement non-wtxidrelay (glozow) `2da46b88f0` pass P2PTxInvStore init args to P2PInterface init (glozow) `e3bd51e4b5` [doc] how unique_parents can be empty (glozow) `32eb6dc758` [refactor] assign local variable for wtxid (glozow) `18820ccf6b` multi-announcer orphan handling test fixups (glozow) `c4cc61db98` [fuzz] GetCandidatePeers (glozow) `7704139cf0` [refactor] make GetCandidatePeers take uint256 and in-out vector (glozow) `6e4d392a75` [refactor] rename to OrphanResolutionCandidate to MaybeAdd* (glozow) `57221ad979` [refactor] move parent inv-adding to OrphanResolutionCandidate (glozow) Pull request description: Followup to #31397. Addressing (in order): https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1906077380 https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1881060842 https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1905994963 https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1905999581 https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1906001592 https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1905989913 https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1905920861 https://github.com/bitcoin/bitcoin/pull/31658#pullrequestreview-2551617694 https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1917559601 ACKs for top commit: instagibbs: reACK `7426afbe62` marcofleon: reACK `7426afbe62` mzumsande: Code Review ACK `7426afbe62` dergoegge: Code review ACK `7426afbe62` Tree-SHA512: bca8f576873fdaa20b758e1ee9708ce94e618ff14726864b29b50f0f9a4db58136a286d2b654af569b09433a028901fe6bcdda68dcbfea71e2d1271934725503		2025-02-04 10:10:29 +00:00
.github
.tx
ci	Merge bitcoin/bitcoin#31653 : lint: Call more checks from test_runner	2025-02-04 09:57:35 +00:00
cmake
contrib
depends
doc
share
src	Merge bitcoin/bitcoin#31666 : multi-peer orphan resolution followups	2025-02-04 10:10:29 +00:00
test	Merge bitcoin/bitcoin#31666 : multi-peer orphan resolution followups	2025-02-04 10:10:29 +00:00
.cirrus.yml
.editorconfig
.gitattributes
.gitignore
.python-version
.style.yapf
CMakeLists.txt
CMakePresets.json
CONTRIBUTING.md
COPYING
INSTALL.md
libbitcoinkernel.pc.in
README.md
SECURITY.md
vcpkg.json

README.md

Bitcoin Core integration/staging tree

https://bitcoincore.org

For an immediately usable, binary version of the Bitcoin Core software, see https://bitcoincore.org/en/download/.

What is Bitcoin Core?

Bitcoin Core connects to the Bitcoin peer-to-peer network to download and fully validate blocks and transactions. It also includes a wallet and graphical user interface, which can be optionally built.

Further information about Bitcoin Core is available in the doc folder.

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 during the generation of the build system) with: ctest. 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. These tests can be run (if the test dependencies are installed) with: build/test/functional/test_runner.py (assuming build is your build directory).

The CI (Continuous Integration) systems make 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.