48aa0e98d0
ac599c4a9ctest: Test MuSig2 in the wallet (Ava Chow)68ef954c4cwallet: Keep secnonces in DescriptorScriptPubKeyMan (Ava Chow)4a273edda0sign: Create MuSig2 signatures for known MuSig2 aggregate keys (Ava Chow)258db93889sign: Add CreateMuSig2AggregateSig (Ava Chow)bf69442b3fsign: Add CreateMuSig2PartialSig (Ava Chow)512b17fc56sign: Add CreateMuSig2Nonce (Ava Chow)82ea67c607musig: Add MuSig2AggregatePubkeys variant that validates the aggregate (Ava Chow)d99a081679psbt: MuSig2 data in Fill/FromSignatureData (Ava Chow)4d8b4f5336signingprovider: Add musig2 secnonces (Ava Chow)c06a1dc86fAdd MuSig2SecNonce class for secure allocation of musig nonces (Ava Chow)9baff05e49sign: Include taproot output key's KeyOriginInfo in sigdata (Ava Chow)4b24bfeab9pubkey: Return tweaks from BIP32 derivation (Ava Chow)f14876213amusig: Move synthetic xpub construction to its own function (Ava Chow)fb8720f1e0sign: Refactor Schnorr sighash computation out of CreateSchnorrSig (Ava Chow)a4cfddda64tests: Clarify why musig derivation adds a pubkey and xpub (Ava Chow)39a63bf2e7descriptors: Add a doxygen comment for has_hardened output_parameter (Ava Chow)2320184d0edescriptors: Fix meaning of any_key_parsed (Ava Chow) Pull request description: This PR implements MuSig2 signing so that the wallet can receive and spend from imported `musig(0` descriptors. The libsecp musig module is enabled so that it can be used for all of the MuSig2 cryptography. Secnonces are handled in a separate class which holds the libsecp secnonce object in a `secure_unique_ptr`. Since secnonces must not be used, this class has no serialization and will only live in memory. A restart of the software will require a restart of the MuSig2 signing process. ACKs for top commit: fjahr: tACKac599c4a9crkrux: lgtm tACKac599c4a9ctheStack: Code-review ACKac599c4a9c🗝️ Tree-SHA512: 626b9adc42ed2403e2f4405321eb9ce009a829c07d968e95ab288fe4940b195b0af35ca279a4a7fa51af76e55382bad6f63a23bca14a84140559b3c667e7041e
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.