So here's the plan for selecting Bitcoin's new PoW algorithm: Nobody knows the new algorithm right now, and nobody will until we all know at the same moment. At 14:00 UTC August 11th, we will begin watching Bitcoin's Testnet4 chain for new blocks. The very next block found, look at the block hash. The last character will choose the new algorithm. (Note that testnet4 blocks are typically timestamped wrong!) As soon as I see that block, I will reveal the mapping showing which algorithm that character represents. Throughout the last 24+ hours, the community has discussed and made a short list of candidate algorithms. I compiled that list into a weighted (according to their suitability) set of options for the mapping list. You can prove I didn't rig it, by SHA256 hashing the mapping text file. It will match 71a7960874f3352f4ba600ce67bd6f8e96702565abea93021fa86349d99a45e8

~22 hours until signaling BIP110 becomes mandatory for Bitcoin miners. Mining blocks without signaling will then forfeit all block rewards!

Are you kidding me??? (Coldcard firmware update from Coinkite)

Quite a few people suggesting/using dice to mitigate the Coldcard vulnerability. Note that common dice are not designed to be cryptographically secure. If you are going to do this, you probably should buy precision casino dice. And even then, have another source of entropy.

I support BIP110 because Bitcoin is essential to the future of mankind and the last 8 months have proven it to be the best immediate solution to the critical injury inflicted by Core 30.

On Saturday, a troll made a false "consensus failure" report about Bitcoin Knots. To put it simply: if Core corrupts your data, Knots sometimes can't detect the corruption. Since Core is late updating to BIP110, it can in some case corrupt the database after activation. This is not a surprise nor a bug in Knots, much less a serious issue. Core also won't detect it; nor have most previous softforks guarded against it (eg, Taproot did not). The simple answer is: don't run software that corrupts your data. The deficiency in Core that can cause this corruption is only a risk starting in August. Upgrade to the latest Knots 29.3.knots20260508 before then. On Sunday, another fake "bug" was claimed by Murch. It's a complete fabrication. There is nothing to do. In both cases, there was zero disclosure to the project at all (much less responsible disclosure) - this is clearly a bad faith FUD campaign and will probably continue. If any real concerns were to surface, @Bitcoin Knots would post an announcement.

Removing rules is a hardfork. That includes scheduled rules like subsidy halvings, and yes, even BIP110. Rejecting BIP110 is a contentious hardfork attempt. And unlike softforks, hardforks need consensus to succeed. There is no consensus on rejecting BIP110.

With respect to BIP110: Knots 20260508: Yes Old Knots: Yeah, but ask miners' permission Core <=29: Yeah, but ask miners' permission Core 30+: Okay, iff miners agree LibreRelay: Okay, iff miners agree Literally no node software actually *opposes* BIP110.