Building on bitcoin

Wonder

1. Why does a single line of code change in Bitcoin Core require months of discussion before it reaches a stable release?
2. How do developers test consensus-critical logic without risking real funds or breaking the main network?
3. What is the difference between a descriptor and a PSBT, and why are both essential for modern wallet development?

Explore

1. Bitcoin Core provides two primary environments for testing: regtest and signet. Regtest allows developers to mine blocks instantly with no proof-of-work requirement, making it ideal for unit tests and rapid iteration on consensus rules. Signet (BIP 325) is a public test network whose blocks must also carry a signature from designated signers, so it keeps steady block times and cannot be flooded by hashrate; it suits testing against other people’s software without real money.
2. The Remote Procedure Call (RPC) interface exposes Bitcoin Core’s internal state to external scripts. Developers use RPC commands to manipulate chains, inspect transactions, and trigger mining in regtest. This programmatic access is fundamental for building wallet software that needs to interact with a node’s data structures directly, bypassing the graphical user interface entirely.
3. Descriptors define how keys are derived into spending conditions, while Partially Signed Bitcoin Transactions (PSBTs) facilitate multi-party signing workflows. BIP 174 standardized the PSBT format, allowing different entities—hardware wallets, mobile devices, or servers—to add signatures to a transaction without exposing private keys. This separation of key management from transaction construction is critical for secure multisig setups.
4. The Bitcoin Dev Kit (BDK) and Lightning Dev Kit (LDK) abstract away the complexity of node management for application developers. BDK is a Rust library for descriptor-based wallets that can read the chain from Bitcoin Core, an Electrum server or an Esplora API, while LDK provides a lightweight implementation of the Lightning Network protocol suitable for mobile devices. These libraries lower the barrier to entry for building bitcoin-native applications without requiring deep systems programming knowledge.
5. Public review is the backbone of Bitcoin’s security model. Changes proposed via pull requests undergo rigorous scrutiny from a global community of developers. The PR Review Club facilitates this by organizing regular sessions where contributors analyze diffs line-by-line. This collective intelligence catches subtle bugs and ensures that consensus changes are thoroughly understood before adoption, a process distinct from the rapid release cycles common in other software ecosystems.
6. Start a private chain: run bitcoind -regtest -daemon, create a wallet with bitcoin-cli -regtest createwallet dev, and mine 101 blocks to one of its addresses with generatetoaddress so the first coinbase matures. Build a payment with walletcreatefundedpsbt, read it with decodepsbt, then sign and broadcast it with walletprocesspsbt and sendrawtransaction. Mine one more block and watch it confirm.

Key facts

Exercise nine, six, three, one

Fact check

Dates, figures and claims checked against the published sources listed below.

• Bitcoin Core, CONTRIBUTING.md and developer documentation
• BIP 174: Partially Signed Bitcoin Transactions
• BIP 380: Output Script Descriptors
• BDK (Bitcoin Dev Kit) official documentation
• LDK (Lightning Dev Kit) official documentation