Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£893.41
EST. MONTHLY
198
DAYS
EST. ROI
This guide explains Bitcoin Core 30.3 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 30.3 fixes a chainstate issue that could repeatedly rewrite large database regions and cause excessive disk reads and writes during ordinary operation. It also corrects wallet fee-bumping and coin-selection paths, pruned-fund removal, PSBT validation, MuSig2 deserialization and a broad set of build and test problems.
- Why it matters: Bitcoin Core 30.3 repairs a potentially costly storage pattern and several custody-adjacent wallet paths. Operators should prove both the I/O improvement and every affected signing or fee workflow before wider deployment.
- 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 30.3 release in simple English
Bitcoin Core 30.3 release: Fixes cover conflicting transactions in removeprunedfunds, an unavailable combined bump-fee crash, a coin-selection amount treated as boolean and outpoint-based input-size estimation.
Simple example
A node operator is checking Bitcoin Core 30.3 release. Capture disk throughput, latency and write amplification before and after the canary. Regular chainstate compaction and disabled LevelDB seek compaction address repeated large rewrites.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- 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.
Chainstate I/O
Regular chainstate compaction and disabled LevelDB seek compaction address repeated large rewrites. Capture disk throughput, latency and write amplification before and after the canary.
Validation
The lifetime of precomputed transaction data is corrected. Re-run validation and reorganisation tests and compare accepted and rejected blocks and transactions.
Wallet
Fixes cover conflicting transactions in removeprunedfunds, an unavailable combined bump-fee crash, a coin-selection amount treated as boolean and outpoint-based input-size estimation.
PSBT and MuSig2
Bounds handling in PSBT signed-and-verified checks is corrected, and MuSig2 public keys are validated while deserializing public nonces and partial signatures.
Networking and miniscript
PCP or NAT-PMP unauthorised failures log less noisily, while and_v() miniscript properties are corrected. Revalidate log alerts and descriptor-policy tooling.
Build scope
many Qt, macOS, GCC, CMake, Guix and test fixes affect custom packages. Pin the toolchain and verify hashes and platform behaviour.
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 30.3 release?
Bitcoin Core 30.3 release: Fixes cover conflicting transactions in removeprunedfunds, an unavailable combined bump-fee crash, a coin-selection amount treated as boolean and outpoint-based input-size estimation.
For Bitcoin Core 30.3 release, what should a beginner know about chainstate I/O?
Regular chainstate compaction and disabled LevelDB seek compaction address repeated large rewrites.
For Bitcoin Core 30.3 release, what should a beginner know about validation?
The lifetime of precomputed transaction data is corrected. Re-run validation and reorganisation tests and compare accepted and rejected blocks and transactions.
For Bitcoin Core 30.3 release, what should a beginner know about wallet?
Fixes cover conflicting transactions in removeprunedfunds, an unavailable combined bump-fee crash, a coin-selection amount treated as boolean and outpoint-based input-size estimation.
Conclusion
Bitcoin Core 30.3 repairs a potentially costly storage pattern and several custody-adjacent wallet paths. Operators should prove both the I/O improvement and every affected signing or fee workflow before wider deployment.
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.