Bitcoin Core v30.0 release candidate is available

The finalization of the release notes is underway and can be reviewed on GitHub at this link. This update addresses an overflow bug that importantly does not affect the muhash value, maintaining its consistency across different versions. Despite initial considerations, the final code version will not include a migration function. Instead, a simpler solution has been recommended for tackling the specified issue: utilizing an updated index from a fast machine and transferring it to the index/coinstatsindex/ directory on a slower node, provided that the slow node's last block precedes the last block of the copied index. This method aims to bypass the need for complex migration scripts or manual intervention.

The necessity for a more efficient solution arises from the significant time and resources required to rebuild Coinstatsindex on pruned nodes, particularly those with low-power CPUs. The rebuilding process is akin to an Initial Block Download (IBD), which is inherently slow and challenging, especially in environments susceptible to power failures. A proposed solution includes creating a migration script that ensures the synchronization of muhash values with a recent, accurate version. This approach leverages the consistency of muhash values across versions to facilitate a smoother and quicker update or migration process for Coinstatsindex on systems with limited hardware capabilities or in operational environments prone to interruptions.

Moreover, the latest release candidate, v30.0rc1, of Bitcoin Core is now available for download at bitcoincore.org, with its source code accessible under a signed tag on GitHub at this link. Community members are encouraged to review the changes, submit feedback, issues, or comments via the GitHub issues page at this link. Release candidates like v30.0rc1 play a critical role in the software development lifecycle by undergoing thorough testing to identify and rectify any critical problems before transitioning to a final release version. This process is instrumental in ensuring the upcoming major version release's stability and reliability before its official integration into the Bitcoin Core software suite.