-
Notifications
You must be signed in to change notification settings - Fork 34
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
26 0 version of bitcoin #91
Conversation
Add sjors key
Looks like the sha256sums do not match. # https://bitcoincore.org/bin/bitcoin-core-26.0/
% grep "bitcoin-26.0.tar.gz" SHA256SUMS
ab1d99276e28db62d1d9f3901e85ac358d7f1ebcb942d348a9c4e46f0fcdc0a1 bitcoin-26.0.tar.gz
# From releases page https://github.com/bitcoin/bitcoin/releases/tag/v26.0
% sha256sum bitcoin-26.0.tar.gz
3eb7c1e35de9415f82737e48cdc6f0e7f4b75973cb123996662c1650f6d544cf bitcoin-26.0.tar.gz |
From https://github.com/bitcoin/bitcoin/releases/tag/v26.0 Change the source download url to https://bitcoincore.org/bin/bitcoin-core-26.0/ and it works. |
# Download checksums | ||
ADD https://bitcoincore.org/bin/bitcoin-core-$VERSION/SHA256SUMS ./ | ||
|
||
# Download source code from same website as github is probably deterministicly built |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this comment needs fixing. GitHub might be deterministic, but it doesn't match our source tarballs, which are also deterministic. This comment seems to imply that our tarballs are not deterministic?
Release 26-0 version of bitcoind containers