Skip to content

Upgrade bitcoin backend to Core 31.2 - #1

Open
peachbits wants to merge 3 commits into
masterfrom
btc-31.2
Open

peachbits wants to merge 3 commits into
masterfrom
btc-31.2

Conversation

@peachbits

Copy link
Copy Markdown

Bitcoin Core 29.x reached end of life on 2026-10-27. Core's disclosure policy publishes Medium and High severity bugs two weeks after the last affected release line goes end of life. For the bugs fixed in 30.0, that's around 2026-11-10. 29.5 doesn't have those fixes, so this goes straight to 31.2.

Changes

  • Upgrade bitcoin node to v29.4 (228c74e): the earlier 29.4 bump, which never reached master.
  • Upgrade bitcoin node to v31.2 (9d6434d): version, binary_url and SHA256 for all five bitcoin configs. The x86_64 and arm64 hashes match the release SHA256SUMS.
  • Drop obsolete bitcoind options (d623a89): removes mempoolfullrbf (dropped in Core 29.0) and deprecatedrpc=estimatefee (Core has no estimatefee RPC left to re-enable). It keeps deprecatedrpc=warnings, because this Blockbook still parses warnings as a string. Upstream removed that option only after fix(btc): accept array-form "warnings" from Bitcoin Core 25.0+ trezor/blockbook#1633 taught the parser the array form.

Blockbook doesn't need a rebuild:

  • For BTC it gets fee estimates from the mempool.space provider and falls back to estimatesmartfee. It never calls estimatefee.
  • The other RPCs it uses only gained fields in 30.x and 31.x.

No reindex either: the only 30.0 migration is for coinstatsindex, which these nodes don't enable.

Deployed

  • btc-eu1 (Debian 12) since 2026-10-29 21:50Z. It ran for 26 hours with btc-wusa1 still on 29.2 as the control:
    • It matched wusa1's height in every sample.
    • It logged no bitcoind errors and had no crashes.
    • estimatesmartfee repopulated after Core discarded the 29.x fee data.
    • A kernel-update reboot during the soak showed both services come back on their own.
  • btc-wusa1 (Debian 11) since 2026-10-31 00:31Z. New blocks reach Blockbook over ZMQ within 1 to 2 seconds.

Both boxes were patched in place:

  1. Check out this branch.
  2. Build the backend deb.
  3. apt-get install it.
  4. Restart backend-bitcoin, then blockbook-bitcoin.

Building on Debian 11

The deb's libc dependency comes from the build image, not the host. wusa1's cached blockbook-build images are Debian 12, so the first build declared libc6 (>= 2.34) and apt refused it on bullseye. No binary in the package needs more than GLIBC_2.30, and building with a Debian 11 image gave libc6 (>= 2.30). The 31.2 deb also pulls in libfontconfig1 for the bundled bitcoin-gui.

Brings the backend to a release with Bitcoin Core #33106, which lowered
the default -minrelaytxfee and -incrementalrelayfee to 0.1 sat/vB. Nodes
older than 28.3 and 29.1 still refuse transactions under 1 sat/vB. Edge's BTC
boxes run 28.0.0 (btc-wusa1, end of life since 2026-04-19 and exposed to
CVE-2024-52911) and 29.0.0 (btc-eu1).

29.4 rather than upstream's 29.2 also picks up the regular chainstate
compaction from #35465, which targets chainstates created by pre-29
nodes like btc-wusa1's, plus the 29.3 validation and P2P fixes. Same
tarball layout and config surface as 29.2. No reindex required. Testnet
configs share the binary, so they move with mainnet.

sha256 verified against bitcoincore.org SHA256SUMS, six guix.sigs builder
attestations, and a local download of both tarballs.
mempoolfullrbf was removed in Core 29.0, and Core no longer has an
estimatefee RPC for deprecatedrpc=estimatefee to re-enable.

Keep deprecatedrpc=warnings: this blockbook still parses the warnings
field as a string. Upstream dropped it only after trezor#1633
taught the parser the array form.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant