Tests failing due to Bitcoin Core v30 binaries missing

[0xB10C]

As part of https://bitcoincore.org/en/2026/01/05/wallet-migration-bug/, the Bitcoin Core v30 and v30.1 binaries have been removed. This will cause tests that use these binaries through the node package to fail:

error: failed to run custom build command for `corepc-node v0.11.0 (https://github.com/0xb10c/corepc?rev=022a23a81e859a5e6f0d8b3774e02f68b2f8a44b#022a23a8)`

Caused by:
  process didn't exit successfully: `/home/runner/work/peer-observer/peer-observer/target/debug/build/corepc-node-d88456b27e32f4f2/build-script-build` (exit status: 101)
  --- stdout
  download_filename: bitcoin-30.0-x86_64-linux-gnu.tar.gz
  filename:bitcoin-30.0-x86_64-linux-gnu.tar.gz version:30.0 hash:00964ae375084113b1162f2f493b9372421608af23539766e315a3cb0ee54248

  --- stderr

  thread 'main' (6540) panicked at /home/runner/.cargo/git/checkouts/corepc-0b6594124fe197fa/022a23a/node/build.rs:96:21:
  assertion `left == right` failed: url https://bitcoincore.org/bin/bitcoin-core-30.0/bitcoin-30.0-x86_64-linux-gnu.tar.gz didn't return 200
    left: 404
   right: 200

Opening this issue to track progress on this. Since v30.2 is being released soon, it's likely best to just wait until that's done and then switch to using it.

[TheBlueMatt]

The real issue is that they weren't being cached. Please for christ's sake do not hammer bitcoincore.org trying to download the same files on every CI run.

[tcharding]

Oooph, my bad. We should definitely be caching.

[tcharding]

As for the missing v30 binaries how about we just commit a binary for now until the next one is available? We only use for testing so the bug is meaningless to our CI here.

[TheBlueMatt]

I assume a 30.2 will be out like this week so might as well just wait a day and fix ci then.

[jamillambert]

The real issue is that they weren't being cached. Please for christ's sake do not hammer bitcoincore.org trying to download the same files on every CI run.

Files are now cached in #449

[0xB10C]

The real issue is that they weren't being cached. Please for christ's sake do not hammer bitcoincore.org trying to download the same files on every CI run.

Files are now cached in #449

Consumers of the node crate probably also download the binaries each time they run something in their CI. While somewhat unrelated to #449, any ideas for alternatives here? Mirror them somewhere else?

[TheBlueMatt]

Maybe someone should write a standard GitHub action that incorporates appropriate caching that we can push as a standard?