-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to Bitcoin core 25.0 #48
base: master
Are you sure you want to change the base?
Conversation
I personally would prefer that we don't use However, you should be able to |
hi @ChristopherA, managed to replace
Was wondering if you could elaborate a little bit more on the issue you mentioned about auth... as said very little experience here from my side and it would be nice to learn more about it |
hi @shannona, could you give me a feedback here ? thanks |
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