I confirm reproducible build of #bitcoin core 26.1 on x86_64-linux-gnu.
```
sudo apt-get install guix
git clone 
cd bitcoin/
git checkout -b my v26.1
git log # must show commit 0b4aa31c34b239ec7da36760a2670792184c3ba8
env HOSTS='x86_64-linux-gnu' ./contrib/guix/guix-build
```
... wait for a while ...
```
$ sha256sum guix-build-26.1/output/x86_64-linux-gnu/bitcoin-26.1-x86_64-linux-gnu.tar.gz
a5b7d206384a8100058d3f2e2f02123a8e49e83f523499e70e86e121a4897d5b
```
The binary with the same hash can be downloaded from https://bitcoincore.org/bin/bitcoin-core-26.1/bitcoin-26.1-x86_64-linux-gnu.tar.gz
I'm not rushing to update to this version. First, I want to understand the changes they made to combat spam in the blocks. They look suspicious to me.
p2p: Don't process mutated blocks
p2p: Don't consider blocks mutated if they don't connect to known prev block
GitHub
GitHub - bitcoin/bitcoin: Bitcoin Core integration/staging tree
Bitcoin Core integration/staging tree. Contribute to bitcoin/bitcoin development by creating an account on GitHub.
GitHub
p2p: Don't process mutated blocks by dergoegge · Pull Request #29412 · bitcoin/bitcoin
This PR proposes to check for mutated blocks early as a defense-in-depth mitigation against attacks leveraging mutated blocks.
We introduce IsBlock...
GitHub
p2p: Don't consider blocks mutated if they don't connect to known prev block by instagibbs · Pull Request #29524 · bitcoin/bitcoin
Followup to #29412 to revert some of the behavior change that was likely unintentional.
Based on comments from #29412 (comment)
