Pre-order
Overall ranking
Equihash
·
ZEC
Overall rank#1of 100AvailableAll: #2 / 831
Pre-OrderFree Shipping
Hashrate
525KSOL
Efficiency
4.73W/KSOL
Power
2483W
Earns/kWh
42.2p
This guide explains Bitcoin Core 22.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 22.0 was released on 13 September 2021 with material network, wallet and operational changes. It added I2P connectivity, removed Tor v2 address support, adopted Bech32m handling for witness version one, introduced experimental external-signer integration and expanded descriptor-wallet tooling.
- Why it matters: Bitcoin Core 22.0 combined transport, address, wallet and signer changes. A safe operator upgrade verifies artefacts, tests each affected boundary and proves both forward operation and rollback before touching the production node.
- 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 22.0 release in simple English
Bitcoin Core 22.0 release: Version 22.0 changed the naming scheme by dropping the leading zero, raised the minimum supported macOS version to 10.14 and remained compatible with older wallet formats subject to migration time.
Simple example
A node operator is checking Bitcoin Core 22.0 release. Test rollback with copied data before scheduling the production window. Verify release signatures and hashes, stop cleanly, snapshot data and configuration, deploy the pinned binary, start under observation and reconcile chain, peers, indexes, wallets and RPC contracts.
Key terms in plain English
- 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.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- Taproot:
- A Bitcoin upgrade that added new signature and script options for spending outputs.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Release boundary
Version 22.0 changed the naming scheme by dropping the leading zero, raised the minimum supported macOS version to 10.14 and remained compatible with older wallet formats subject to migration time.
Network changes
The release added native I2P SAM support, ignored Tor v2 addresses, added NAT-PMP port mapping and updated address reporting. Validate every configured reachability path independently.
Taproot and addresses
Address-accepting RPCs require Bech32m for witness version one and above. Taproot descriptor import was gated on activation for the selected network, preventing premature mainnet assumptions.
Wallet changes
Experimental external-signer support arrived through new signer and display RPCs plus GUI and send integration. Listdescriptors exposed public descriptor inventory and ranged-wallet state.
RPC and policy
getpeerinfo fields changed, testmempoolaccept gained experimental package testing, listbanned gained duration fields and several deprecated address fields required a compatibility flag for one final release.
Upgrade method
Verify release signatures and hashes, stop cleanly, snapshot data and configuration, deploy the pinned binary, start under observation and reconcile chain, peers, indexes, wallets and RPC contracts.
Rollback
Keep the previous executable and immutable backups, but do not assume every peers.dat or wallet change is backward-compatible. Test rollback with copied data before scheduling the production window. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is the main point of Bitcoin Core 22.0 release?
Bitcoin Core 22.0 release: Version 22.0 changed the naming scheme by dropping the leading zero, raised the minimum supported macOS version to 10.14 and remained compatible with older wallet formats subject to migration time.
For Bitcoin Core 22.0 release, what should a beginner know about release boundary?
Version 22.0 changed the naming scheme by dropping the leading zero, raised the minimum supported macOS version to 10.14 and remained compatible with older wallet formats subject to migration time.
For Bitcoin Core 22.0 release, what should a beginner know about network changes?
The release added native I2P SAM support, ignored Tor v2 addresses, added NAT-PMP port mapping and updated address reporting.
For Bitcoin Core 22.0 release, what should a beginner know about taproot and addresses?
Address-accepting RPCs require Bech32m for witness version one and above. Taproot descriptor import was gated on activation for the selected network, preventing premature mainnet assumptions.
Conclusion
Bitcoin Core 22.0 combined transport, address, wallet and signer changes. A safe operator upgrade verifies artefacts, tests each affected boundary and proves both forward operation and rollback before touching the production node.
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.