Update to Bitcoin core 25.0 #48
Open
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.
Goal: update to bitcoin core 25.0
Overview
Updating to 25.0 should be only about updating env var
BITCOIN
, but that is not true bcs the URL for 25.0 public key fingerprints does not exist anymore, whereas it still available for pvs versions like 23.0 and 24.0From 25.0 keys will always be found in a separate repo as explained here by @achow101
Currently both standup scripts grab the
keys.txt
file from target URL version and then download keys from a key-server as we can see here. However an analogus file likekeys.txt
with all fingerprints is not found in this new repo, but instead all public keys can be found for each release in the corresponding version folder.On top of that in the
builder-keys
folder, it seems like we can find all updated public keys, so apperently there is no need to download public keys from a key-server as they can all be found in this folderSolution
In this pull request keys are not downloaded from a key-server anymore, but instead first we download the new repo and second import keys from the
builder-keys
folderDoubt/Question
Couldn't figure out how to use
wget
to download the new repo from github, iegit
is installed here. Is this a problem ? asking this bcs adding another software on a machine, where we run a node, might introduce some vulnerability. I don't think this is the case asgit
is a well know piece of software, but again no experience on this matterTODO
LinodeStandUp.sh
StandUp.sh
LinodeStandUp.sh
by maintainerStandUp.sh
by maintainerNEXT STEP
If this pull gets merged, then this must be updated as example shows version 22.0 in
bitcoin-22.0-x86_64-linux-gnu.tar.gz
and thekeys.txt
file