Repository navigation
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
mempoolfullrbf(dropped in Core 29.0) anddeprecatedrpc=estimatefee(Core has noestimatefeeRPC left to re-enable). It keepsdeprecatedrpc=warnings, because this Blockbook still parseswarningsas 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:
estimatesmartfee. It never callsestimatefee.No reindex either: the only 30.0 migration is for coinstatsindex, which these nodes don't enable.
Deployed
estimatesmartfeerepopulated after Core discarded the 29.x fee data.Both boxes were patched in place:
apt-get installit.backend-bitcoin, thenblockbook-bitcoin.Building on Debian 11
The deb's libc dependency comes from the build image, not the host. wusa1's cached
blockbook-buildimages are Debian 12, so the first build declaredlibc6 (>= 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 gavelibc6 (>= 2.30). The 31.2 deb also pulls in libfontconfig1 for the bundled bitcoin-gui.