chore(deps): bump bitcoin to 30.2 - #53
Closed
storopoli wants to merge 4 commits into
Closed
Conversation
ErikBjare
approved these changes
Dec 21, 2025
Author
storopoli
changed the title
|
At least they bumped to v29 f31db59 |
Author
|
We are in v31 now |
|
Well yeah, but not this repo since they merged #50 and ignored this PR: https://github.com/dappnode/DAppNodePackage-bitcoin/commits/master/ |
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
2 participants
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.
Bumps Bitcoin Core to version 30.2. Arguments below.
Bitcoin version 30 is already the most popular version in the Bitcoin network. See Clark Moody's Dashboard:
Also according to Bitcoin Core End of Life Policy, Bitcoin Core developers will "maintain the major versions until their 'Maintenance End'"
which happens on to be support for two last major versions as stated in "we generally maintain the current and previous major release".
Hence the current version is not only outdated but INSECURE.
And the proposed version in #50 (29.0) is also vulnerable because it is behind at least 2 bug fix releases in 29.x because the latest version is 29.2.
Also next major release (31) will make 29.x end of life.