Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£857.29
EST. MONTHLY
206
DAYS
EST. ROI
This guide explains Bitcoin Core 0.19.1 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.19.1 was a minor maintenance release published on 9 March 2020. Its fixes touched wallet address-reuse classification, conflicted mempool transactions, PSBT validation, block-filter configuration, ZMQ notifiers and index shutdown.
- Why it matters: Bitcoin Core 0.19.1 corrected several small but operationally significant edges. A safe upgrade proves wallet classifications, transaction history, PSBT rejection, indexes and notifiers on the actual node workload.
- 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.19.1 release in simple English
Bitcoin Core 0.19.1 release: Treat 0.19.1 as a maintenance upgrade within the 0.19 family. Read the exact change log against deployed features instead of assuming every node receives the same benefit.
Simple example
A node operator is checking Bitcoin Core 0.19.1 release. The release fixed a fatal LevelDB error when blockfilterindex=basic was specified twice, corrected scantxoutset argument requirements and repaired multiple ZMQ notifier handling.
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.
- PSBT:
- A portable format for passing an unsigned or partly signed Bitcoin transaction between tools and signers.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Release scope
Treat 0.19.1 as a maintenance upgrade within the 0.19 family. Read the exact change log against deployed features instead of assuming every node receives the same benefit.
Wallet reuse fixes
The release corrected used-destination handling for known single-key and ScriptHash cases and reset a reused-transaction cache. Sites using avoid_reuse should retest classifications and available balances.
Transaction reporting
A listsinceblock issue involving conflicted mempool transactions was fixed. Reconcile replacement and conflict histories around the upgrade rather than trusting identical-looking totals.
PSBT hardening
Changes handled unspendable PSBTs and checked indexes and amounts within bounds. Test malformed, incomplete and watch-only workflows and keep the unsigned transaction identity fixed.
RPC and index fixes
The release fixed a fatal LevelDB error when blockfilterindex=basic was specified twice, corrected scantxoutset argument requirements and repaired multiple ZMQ notifier handling.
Platform and shutdown
Precompiled RISC-V binaries were added, macOS preallocation was corrected and indexes were stopped after the chain-state-flushed callback. Verify platform-specific start and clean shutdown.
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.19.1 release?
Bitcoin Core 0.19.1 release: Treat 0.19.1 as a maintenance upgrade within the 0.19 family.
For Bitcoin Core 0.19.1 release, what should a beginner know about release scope?
Treat 0.19.1 as a maintenance upgrade within the 0.19 family.
For Bitcoin Core 0.19.1 release, what should a beginner know about wallet reuse fixes?
The release corrected used-destination handling for known single-key and ScriptHash cases and reset a reused-transaction cache.
For Bitcoin Core 0.19.1 release, what should a beginner know about transaction reporting?
A listsinceblock issue involving conflicted mempool transactions was fixed. Reconcile replacement and conflict histories around the upgrade rather than trusting identical-looking totals.
Conclusion
Bitcoin Core 0.19.1 corrected several small but operationally significant edges. A safe upgrade proves wallet classifications, transaction history, PSBT rejection, indexes and notifiers on the actual node workload.
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.