Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£893.75
EST. MONTHLY
198
DAYS
EST. ROI
This guide explains Bitcoin Core 29.4 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 29.4 backports the chainstate storage fix to the 29.x branch. It corrects repeated large database rewrites that caused excessive disk reads and writes, regularly compacts chainstate and disables LevelDB seek compaction.
- Why it matters: Bitcoin Core 29.4 addresses storage wear and performance on the maintained 29.x branch. A successful upgrade is show by measured I/O improvement and unchanged validation and wallet results, not merely a restarted process.
- 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 29.4 release in simple English
Bitcoin Core 29.4 release: Affected nodes could repeatedly rewrite large parts of chainstate during normal operation. Compare device bytes written, IOPS, latency, queue depth and free space before and after upgrade.
Simple example
A node operator is checking Bitcoin Core 29.4 release. Document why the 29.x branch remains selected and its support horizon. Do not infer Core 30 wallet fixes or Core 31 cluster-mempool and private-broadcast behaviour.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Primary issue
Affected nodes could repeatedly rewrite large parts of chainstate during normal operation. Compare device bytes written, IOPS, latency, queue depth and free space before and after upgrade.
Compaction
The coins database now compacts regularly and the bundled LevelDB disables seek compaction. Plan temporary compaction I/O and distinguish healthy maintenance from the old rewrite loop.
Validation
The lifetime of precomputed transaction data is corrected. Exercise block connection, disconnection and reorganisation workloads and compare outcomes with a reference node.
Wallet sizing
Wallet estimation uses the outpoint when estimating input size. Test varied script types, watch-only information and funded-transaction fee calculations.
Build compatibility
The release updates SQLite CMake integration, SOURCE_DATE_EPOCH handling, newer Boost compatibility and CI infrastructure. Custom builds need pinned dependencies and repeatable artefact checks.
Branch decision
Document why the 29.x branch remains selected and its support horizon. Do not infer Core 30 wallet fixes or Core 31 cluster-mempool and private-broadcast 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 29.4 release?
Bitcoin Core 29.4 release: Affected nodes could repeatedly rewrite large parts of chainstate during normal operation.
For Bitcoin Core 29.4 release, what should a beginner know about primary issue?
Affected nodes could repeatedly rewrite large parts of chainstate during normal operation.
For Bitcoin Core 29.4 release, what should a beginner know about compaction?
The coins database now compacts regularly and the bundled LevelDB disables seek compaction.
For Bitcoin Core 29.4 release, what should a beginner know about validation?
The lifetime of precomputed transaction data is corrected. Exercise block connection, disconnection and reorganisation workloads and compare outcomes with a reference node.
Conclusion
Bitcoin Core 29.4 addresses storage wear and performance on the maintained 29.x branch. A successful upgrade is show by measured I/O improvement and unchanged validation and wallet results, not merely a restarted process.
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.