de7c3587cddoc: Update add checksum instructions in tutorial (Ben Westgate)2a46e94a16doc: Update multisig-tutorial.md to use multipath descriptors (Ben Westgate) Pull request description: ### Summary Update `doc/multisig-tutorial.md` to use multipath descriptor format instead of separate external/internal descriptors. The tutorial now: - extracts a single `xpub_n` per participant - constructs a multipath `wsh(sortedmulti(...))` descriptor with `<0;1>` change index semantics - uses `getdescriptorinfo` to compute descriptor checksum - explains that `importdescriptors` expands the multipath descriptor into internal and external descriptors - update `/test/functional/wallet_multisig_descriptor_psbt.py` functional test / documentation to use multi-path descriptors --- ### Motivation A single multipath descriptor is the most convenient pattern for multisig; our documentation should use it. --- ### What changed - replaced extraction of `external_xpub_n` and `internal_xpub_n` with extraction of a single `xpub_n` - removed instructions to create and import separate external/internal descriptors - added instructions to build a multipath `wsh(sortedmulti(...))` descriptor and derive checksum with `getdescriptorinfo` - checksum field is parsed and appended as the multipath descriptor is not the canonical "desc" output - clarified that `importdescriptors` automatically expands multipath descriptors into internal and external forms - similar changes to the functional test: wallet_multisig_descriptor_psbt. --- ### Testing I have run the updated shell snippets and confirmed the multipath descriptor produces the same `listdescriptors` output after importing as the two descriptor method in bitcoin:master. --- ### Related issues / PRs This tutorial change references the multipath descriptor consolidation (see commit / PR referenced in the change). The commit message points to bitcoin#22838 as the upstream change that enables this behavior. --- ### Release note (for changelog) Documentation: update multisig tutorial and multisig functional test to use multipath descriptors ACKs for top commit: Sjors: utACKde7c3587cdkannapoix: Core review ACK:de7c3587cdachow101: ACKde7c3587cdrkrux: crACKde7c3587cdTree-SHA512: ca7275d8ad04922b3fa8d2a3084ff96aa2104265f1fc2f749814dd16776351ab692d67e7e643d08052f7492e3eaa1a9a4dfe3470163e57939a49f782d3df511a
Bitcoin Core
Setup
Bitcoin Core is the original Bitcoin client and it builds the backbone of the network. It downloads and, by default, stores the entire history of Bitcoin transactions, which requires several hundred gigabytes or more of disk space. Depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to several days or more.
To download Bitcoin Core, visit bitcoincore.org.
Running
The following are some helpful notes on how to run Bitcoin Core on your native platform.
Unix
Unpack the files into a directory and run:
bin/bitcoin-qt(GUI) orbin/bitcoind(headless)bin/bitcoin(wrapper command)
The bitcoin command supports subcommands like bitcoin gui, bitcoin node, and bitcoin rpc exposing different functionality. Subcommands can be listed with bitcoin help.
Windows
Unpack the files into a directory, and then run bitcoin-qt.exe.
macOS
Drag Bitcoin Core to your applications folder, and then run Bitcoin Core.
Need Help?
- See the documentation at the Bitcoin Wiki for help and more information.
- Ask for help on Bitcoin StackExchange.
- Ask for help on #bitcoin on Libera Chat. If you don't have an IRC client, you can use web.libera.chat.
- Ask for help on the BitcoinTalk forums, in the Technical Support board.
Building
The following are developer notes on how to build Bitcoin Core on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.
- Dependencies
- macOS Build Notes
- Unix Build Notes
- Windows Build Notes
- FreeBSD Build Notes
- OpenBSD Build Notes
- NetBSD Build Notes
Development
The Bitcoin repo's root README contains relevant information on the development process and automated testing.
- Developer Notes
- Productivity Notes
- Release Process
- Source Code Documentation (External Link)
- Translation Process
- Translation Strings Policy
- JSON-RPC Interface
- Unauthenticated REST Interface
- BIPS
- Dnsseed Policy
- Benchmarking
- Internal Design Docs
Resources
- Discuss on the BitcoinTalk forums, in the Development & Technical Discussion board.
- Discuss project-specific development on #bitcoin-core-dev on Libera Chat. If you don't have an IRC client, you can use web.libera.chat.
Miscellaneous
- Assets Attribution
- bitcoin.conf Configuration File
- CJDNS Support
- Files
- Fuzz-testing
- I2P Support
- Init Scripts (systemd/upstart/openrc)
- Managing Wallets
- Multisig Tutorial
- Offline Signing Tutorial
- P2P bad ports definition and list
- PSBT support
- Reduce Memory
- Reduce Traffic
- Tor Support
- Transaction Relay Policy
- ZMQ
License
Distributed under the MIT software license.