This guide explains Bitcoin Core 0.21.0 release in plain English. It summarises the important changes, who they affect and what should be checked before an upgrade.
TL;DR
- What it is: Bitcoin Core 0.21.0 introduced anchor connections, optional BIP 157 compact-filter serving, Signet, wtxid relay, experimental descriptor wallets and new index and testing RPCs. It also included Taproot validation rules without mainnet activation.
- Why it matters: Bitcoin Core 0.21.0 added substantial network and wallet capabilities. Safe adoption keeps experimental descriptor storage, compact-filter service, Signet, relay changes and inactive consensus code within their exact boundaries.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Bitcoin Core 0.21.0 release in simple English
Bitcoin Core 0.21.0 release: This is the correctly dated release that added P2P BIP 157 serving when both blockfilterindex and peerblockfilters are enabled.
Simple example
A node operator is checking Bitcoin Core 0.21.0 release. Budget index resources and verify advertised service and request limits. Protect file ownership and test shutdown, corruption and recovery behaviour.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Taproot:
- A Bitcoin upgrade that added new signature and script options for spending outputs.
Network resilience
anchors.dat retained two block-relay-only peers across clean restarts to reduce eclipse opportunities. Protect file ownership and test shutdown, corruption and recovery behaviour.
Compact-filter serving
This is the correctly dated release that added P2P BIP 157 serving when both blockfilterindex and peerblockfilters are enabled. Budget index resources and verify advertised service and request limits.
Signet and relay
The release added default and custom Signet support and negotiated wtxid transaction relay. Keep network-specific data, ports and configuration isolated and update peer parsers.
Descriptor wallets
Descriptor wallets were experimental, optional and not default. They used explicit output descriptors, different watch-only and import semantics and an SQLite database backend.
Wallet compatibility
Legacy wallets continued unchanged, while many legacy import/export RPCs were disabled for descriptor wallets. External tools reading Berkeley DB files could not assume SQLite compatibility.
Taproot boundary
BIP 340 to 342 validation was included but mainnet activation had not occurred. Describe code availability separately from active consensus and use Signet for historical testing.
How specialists test it
Node operators test the release on a representative non-production system. They check startup, normal operation, failure handling and restart before changing a live node. Connected wallets, monitoring and mining services should also be checked.
Frequently asked questions
What is the main point of Bitcoin Core 0.21.0 release?
Bitcoin Core 0.21.0 release: This is the correctly dated release that added P2P BIP 157 serving when both blockfilterindex and peerblockfilters are enabled.
For Bitcoin Core 0.21.0 release, what should a beginner know about network resilience?
anchors.dat retained two block-relay-only peers across clean restarts to reduce eclipse opportunities.
For Bitcoin Core 0.21.0 release, what should a beginner know about compact-filter serving?
This is the correctly dated release that added P2P BIP 157 serving when both blockfilterindex and peerblockfilters are enabled.
For Bitcoin Core 0.21.0 release, what should a beginner know about signet and relay?
The release added default and custom Signet support and negotiated wtxid transaction relay.
Conclusion
Bitcoin Core 0.21.0 added substantial network and wallet capabilities. Safe adoption keeps experimental descriptor storage, compact-filter service, Signet, relay changes and inactive consensus code within their exact boundaries.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.