abb6ae2ec5
483d158f538c3d7c1cac30d2b299bc10b256972e doc: update manual pages for v30.2rc1 (fanquake)
747a863f5b6f45f6a4bb8ad6811ef800cf4afb58 build: bump version to v30.2rc1 (fanquake)
cc3cdbe9214f80ab43b66af121fb78abcb9e2d1d doc: update release notes for v30.2rc1 (fanquake)
c4082a45e64d81dda5ec093a8ba3b6dad4b946a8 wallettool: do not use fs::remove_all in createfromdump cleanup (Ava Chow)
185ca0e391aea530db37dd5bbc0e150286083ea9 test: coverage for migration failure when last sync is beyond prune height (furszy)
bc71372c0e3b552fff174772ef9e5c65177405c3 wallet: migration, fix watch-only and solvables wallets names (furszy)
bef4b1fdee1f386662855fb66409c323eee4bae4 wallet: improve post-migration logging (furszy)
ac940ac2ca6d427970b7ebbd8227154cf0159875 test: restorewallet, coverage for existing dirs, unnamed wallet and prune failure (furszy)
8e5c02a77f1b18ae37829200f96ef3fa1cc91246 test: add coverage for unnamed wallet migration failure (furszy)
ac4d0956ccccb43082991d89a8601c39d490d3a5 wallet: fix unnamed wallet migration failure (furszy)
454ac8e7db0f8b2c000b1d2e943bde95dff0127d wallet: RestoreWallet failure, erase only what was created (furszy)
Pull request description:
Backports:
* #34156
* #34215
ACKs for top commit:
darosior:
ACK 483d158f538c3d7c1cac30d2b299bc10b256972e
willcl-ark:
tACK 483d158f538c3d7c1cac30d2b299bc10b256972e
janb84:
ACK 483d158f538c3d7c1cac30d2b299bc10b256972e
w0xlt:
ACK 483d158f53
marcofleon:
lgtm ACK 483d158f538c3d7c1cac30d2b299bc10b256972e
Tree-SHA512: b43485a8745a663d3a031113a6a266af699b3e70b77f72a0e69ea1986adcaa0ee0d4ce51aacd0fde91611cb4bdba9b6be52e5dca59ff8b12135715b8b1ed5ef2
Bitcoin Core integration/staging tree
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/license/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 tested on Windows, Linux, and macOS. The CI must pass on all commits before merge to avoid unrelated CI failures on new pull requests.
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.