Bitcoin Core v30.0 release candidate is available

Implementation
1

Binaries for Bitcoin Core version v30.0rc1 are available from:

Source code can be found under the signed tag

This is a release candidate for a new major version release.

Preliminary release notes for the release can be found here: v30.0 Release Notes Draft · bitcoin-core/bitcoin-devwiki Wiki · GitHub

There is also a testing guide here: 30.0 Release Candidate Testing Guide · bitcoin-core/bitcoin-devwiki Wiki · GitHub

Please put your issues or comments here: GitHub · Where software is built

Release candidates are test versions for releases. When no critical problems are found, this release candidate will be tagged as v30.0.

4 Likes
2

Rebuilding Coinstatsindex to the new power-failure-safe one on pruned nodes with very low-power CPU takes days (like any IBD would there).

Would it be possible to provide a migration script in case muhash is still in sync with some recent known one?

For example, does this (still in the old coinstatsindex) look good? Comparing to my another pruned node’s (running 29.1) output it is in sync.

$ bitcoin-cli gettxoutsetinfo muhash 915117
{
  "height": 915117,
  "bestblock": "000000000000000000005ebf9d74ec7ab39402801cfbfdb763ac43cf18e45fcd",
  "txouts": 168188922,
  "bogosize": 13176628835,
  "muhash": "c539860039f893733c0adf51bdb559905cbfd88896561b41d62705c488dd17f0",
  "total_amount": 19922013.67356559,
  "total_unspendable_amount": 230.07643441,
  "block_info": {
    "prevout_spent": 7521.85097974,
    "coinbase": 3.20043866,
    "new_outputs_ex_coinbase": 7521.77554107,
    "unspendable": 0.00000001,
    "unspendables": {
      "genesis_block": 0.00000000,
      "bip30": 0.00000000,
      "scripts": 0.00000001,
      "unclaimed_rewards": 0.00000000
    }
  }
}
3

The overflow bug didn’t happen on muhash, so that value should always be in sync. Unfortunately there is no migration function included, we experimented with one, but it didn’t make it into the final version of the code. I don’t think it’s worth the effort to write an external script that migrates the index.

What should work and seems much easier is taking an already synced, new version of the index (from a fast machine) and copying it into the `index/coinstatsindex/` location of your slow node. Just make sure that the slow node is ahead of the last block of the index.

1 Like
4

A third release candidate is now available: Index of /bin/bitcoin-core-30.0/test.rc3/ .

Release notes are being finalised in: [30.x] Finalise v30.0 by fanquake · Pull Request #33559 · bitcoin/bitcoin · GitHub.