📢 Announcing a new #ordisrespector initiative: ready-made executables for Bitcoin Core v0.21 and up.

If you can simply replace your bitcoind executable from your node, you can run a clean mempool.

Should you trust my binaries, though? Read on 🧵

https://github.com/BcnBitcoinOnly/ordisrespector-binaries

My first focus was showing folks how they could build Bitcoin Core themselves in a trustless manner.

Sharing binaries lowers the difficulty to run #ordisrespector much further but it's ickier because it requires trusting me. Fortunately, there's a catch.

https://minibolt.info/guide/bonus/bitcoin/ordisrespector.html

As it so happens Bitcoin Core has infrastructure to build its binaries deterministically (this is actually quite rare).

In layman terms this means that another person building the same version on a different machine gets the same results, byte per byte.

https://github.com/bitcoin/bitcoin/tree/master/contrib/guix

This system is what the Bitcoin Core devs use to build the official binaries distributed on the website.

In this repo they upload the hashes they got for each build and they sign them to put their weight behind them. All SHA256SUM files are equal.

https://github.com/bitcoin-core/guix.sigs

My repo distributes #ordisrespector bitcoind binaries for all supported OSes and architectures, and I also generated a signed SHA256SUM file for each version.

The following is the PGP key ID I used to sign them:

34BE269FE4268497E45588A884C9BB18153758B4

https://github.com/BcnBitcoinOnly/ordisrespector-binaries/releases/tag/24.0.1

A separate readme documents how to do this kind of #ordisrespector build.

Ideally other technically proficient and well-known members of the Bitcoin community will follow this guide and submit their own signatures to boost the trust on these binaries.

https://github.com/BcnBitcoinOnly/ordisrespector-binaries/blob/master/Guix-Guide.md

#[0] not telling you what to do but I believe this material would be excellent for one of your sweet hooker-bot tutorials 🙂

That's all for now from my end.

Run a clean mempool if you want, and keep making noise. These are makeshift solutions, the #ordisrespector patch must end up properly merged into Bitcoin Core as an opt-in bitcoin.conf option. It's your right as a node runner.

Thanks for reading!