Bitcoin Core 25.1 guide covering compact-block downloads, stale fee estimates, invalid addresses, REST shutdown, wallet migration safeguards and verification.
This guide explains Bitcoin Core 25.1 release in plain English. It summarises the important changes, who they affect and what should be checked before an upgrade.
Bitcoin Core 25.1 release: The release updates parallel compact-block downloads and returns unconditionally after a failed compact-block read. Observe block download continuity and peer churn after rollout.
A node operator is checking Bitcoin Core 25.1 release. Re-test any procedure previously exercised on Core 25.0. Confirm the exact packaged build and supported operating system instead of generalising source-build changes.
The release updates parallel compact-block downloads and returns unconditionally after a failed compact-block read. Observe block download continuity and peer churn after rollout.
Core avoids serving a stale fee estimate in the cited case. Applications must still treat estimates as time-sensitive inputs and apply their own age, range and fallback rules.
Invalid Bech32 address handling was fixed, the deploymentinfo REST crash was corrected and server shutdown can proceed after a remote client disconnects.
Address-book migration fixes were added and invalid scripts are no longer allowed through wallet migration. Re-test any procedure previously exercised on Core 25.0.
Top-level-only descriptor functions are not returned as subdescriptors, and wallet conflict marking now checks uninitialised and inconsistent heights.
The release includes macOS Xcode 15 and Qt dependency fixes. Confirm the exact packaged build and supported operating system instead of generalising source-build changes.
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.
Bitcoin Core 25.1 release: The release updates parallel compact-block downloads and returns unconditionally after a failed compact-block read.
The release updates parallel compact-block downloads and returns unconditionally after a failed compact-block read.
Core avoids serving a stale fee estimate in the cited case. Applications must still treat estimates as time-sensitive inputs and apply their own age, range and fallback rules.
Invalid Bech32 address handling was fixed, the deploymentinfo REST crash was corrected and server shutdown can proceed after a remote client disconnects.
Core 25.1 is especially important for operators using wallet migration or REST automation. Its fixes should be proven with negative tests, not just a successful restart and matching chain height.
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Bitcoin Core 31.1 guide covering the private-broadcast IP leak fix, proxy reconnections, chainstate compaction, BDB migration and settings-write safety.
Bitcoin Core 30.3 guide covering excessive chainstate I/O, regular compaction, wallet bump and coin-selection fixes, PSBT, MuSig2 and build maintenance.
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.