Bitcoin Core mirror and no, I don't give a fuck about Monero.
Find a file
glozow c8c85ca16e
Merge bitcoin/bitcoin#26878: [24.x] Backports
784a754aa4 wallet, rpc: Update migratewallet help text for encrypted wallets (Andrew Chow)
debcfe313a tests: Tests for migrating wallets by name, and providing passphrase (Andrew Chow)
ccc72fecd7 wallet: Be able to unlock the wallet for migration (Andrew Chow)
50dd8b13df rpc: Allow users to specify wallet name for migratewallet (Andrew Chow)
648b06256d wallet: Allow MigrateLegacyToDescriptor to take a wallet name (Andrew Chow)
ab3bd457cd i2p: use consistent number of tunnels with i2pd and Java I2P (Vasil Dimov)
29cdf42226 i2p: lower the number of tunnels for transient sessions (Vasil Dimov)
5027e93b6a i2p: reuse created I2P sessions if not used (Vasil Dimov)
a62c541ae8 wallet: reuse change dest when recreating TX with avoidpartialspends (Matthew Zipkin)
64e7db6f4f Zero out wallet master key upon lock (John Moffett)
b7e242ecb3 Correctly limit overview transaction list (John Moffett)
cff67180b3 depends: fix systemtap download URL (fanquake)
7cf73dfed5 Add missing includes to fix gcc-13 compile error (MarcoFalke)
07397cdede addrdb: Only call Serialize() once (Martin Zumsande)
91f83dbeb1 hash: add HashedSourceWriter (Martin Zumsande)
5c824ac5e1 For feebump, ignore abandoned descendant spends (John Moffett)
428dcd51e6 wallet: Skip rescanning if wallet is more recent than tip (Andrew Chow)
cbcdafa471 test: wallet: check that labels are migrated to watchonly wallet (Sebastian Falbesoner)
342abfb3f4 wallet: fully migrate address book entries for watchonly/solvable wallets (Sebastian Falbesoner)

Pull request description:

  Backports:
  * https://github.com/bitcoin/bitcoin/pull/26595
  * https://github.com/bitcoin/bitcoin/pull/26675
  * https://github.com/bitcoin/bitcoin/pull/26679
  * https://github.com/bitcoin/bitcoin/pull/26761
  * https://github.com/bitcoin/bitcoin/pull/26837
  * https://github.com/bitcoin/bitcoin/pull/26909
  * https://github.com/bitcoin/bitcoin/pull/26924
  * https://github.com/bitcoin/bitcoin/pull/26944
  * https://github.com/bitcoin-core/gui/pull/704
  * https://github.com/bitcoin/bitcoin/pull/27053
  * https://github.com/bitcoin/bitcoin/pull/27080

ACKs for top commit:
  instagibbs:
    ACK 784a754aa4
  achow101:
    ACK 784a754aa4
  hebasto:
    ACK 784a754aa4, I've made backporting locally and got a diff between my branch and this PR as follows:

Tree-SHA512: 8ea84aa02d7907ff1e202e1302b441ce9ed2198bf383620ad40056a5d7e8ea88e1047abef0b92d85648016bf9b3195c974be3806ccebd85bef4f85c326869e43
2023-02-27 18:09:31 +00:00
.github doc: Remove label from good first issue template 2020-08-24 09:31:24 +02:00
.tx Adjust .tx/config for new Transifex CLI 2022-10-28 17:49:27 +08:00
build-aux/m4 build: sync ax_boost_base from upstream 2022-09-04 10:10:16 +01:00
build_msvc fs: work around u8path deprecated-declaration warnings with libc++ 2022-08-19 08:58:56 +01:00
ci Merge bitcoin/bitcoin#26880: [24.x] ci: replace Intel macOS CI job 2023-01-12 13:14:04 +01:00
contrib contrib: Fix capture_output in getcoins.py 2022-10-11 09:19:58 +08:00
depends depends: fix systemtap download URL 2023-02-20 17:15:38 +00:00
doc doc: adjust release notes for 24.0.1 2022-12-06 12:39:24 +00:00
share doc: Generate example bitcoin conf for 24.0rc2 2022-10-14 10:28:34 +08:00
src wallet, rpc: Update migratewallet help text for encrypted wallets 2023-02-27 14:15:15 +00:00
test tests: Tests for migrating wallets by name, and providing passphrase 2023-02-27 14:14:46 +00:00
.cirrus.yml Merge bitcoin/bitcoin#26880: [24.x] ci: replace Intel macOS CI job 2023-01-12 13:14:04 +01:00
.editorconfig ci: Drop AppVeyor CI integration 2021-09-07 06:12:53 +03:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore refactor: cleanups post unsubtree'ing univalue 2022-06-15 12:56:44 +01:00
.python-version Bump minimum python version to 3.6 2020-11-09 17:53:47 +10:00
.style.yapf test: .style.yapf: Set column_limit=160 2019-03-04 18:28:13 -05:00
autogen.sh scripted-diff: Bump copyright of files changed in 2019 2019-12-30 10:42:20 +13:00
configure.ac build: bump version to 24.0.1 final 2022-12-06 12:13:42 +00:00
CONTRIBUTING.md doc: Explain squashing with merge commits 2022-05-24 08:17:41 +02:00
COPYING doc: Update license year range to 2022 2022-01-03 04:48:41 +08:00
INSTALL.md doc: Added hyperlink for doc/build 2021-09-09 19:53:12 +05:30
libbitcoinconsensus.pc.in build: remove libcrypto as internal dependency in libbitcoinconsensus.pc 2019-11-19 15:03:44 +01:00
Makefile.am build: package test_bitcoin in Windows installer 2022-08-09 09:13:23 +01:00
README.md doc: Explain Bitcoin Core in README.md 2022-05-10 07:49:09 +02:00
REVIEWERS doc: empty REVIEWERS file 2022-07-30 09:05:07 +01:00
SECURITY.md doc: Add my key to SECURITY.md 2022-08-23 16:57:46 -04:00

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 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. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

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.