The testnet forkwar to determine PoW algo for Bitcoin-jr is more exciting than the BIP110 fork war itself was tbh.

Apparently it was premature to call it for Blake2b-256. See:

(They used testnet because they don’t want to use “Bpedo” and BIP110 blocks are coming in too slow— if any more will come in at all.)

Bdashers decided to use a testnet block header to randomly determine the proof-of-work algorithm for their forkcoin, but now testnet has been forked and they don’t know what to pick. (lol)

Just in case the Bdashers’ wipeout argument does stick around: Bitcoin nodes can always reject the BIP110 chain even in the *extremely* unlikely scenario that it would overtake the Bitcoin chain at some point, by running bitcoin-cli invalidateblock 0000000000000000000169eb6f811ddbd0daf343af7b62180cdb13e7c78dbc16.

Dusted off that pen to explain what could happen when Bitcoin Knots starts rejecting blocks that don’t signal support for BIP110 this weekend. https://bitcoinmagazine.com/technical/bitcoins-bip110-moment-three-possible-scenarios

BIP110 proof-of-work hard fork incoming! https://x.com/cguida6/status/2084653380194955653

BIP110 can as of now no longer be activated through hash power signaling. The "mandatory signaling" window starts next week, which practically speaking means Bitcoin Knots nodes will stall and/or fork off-- unless basically all miners suddenly decide to adopt this nonsense after all. https://filters.watch/

Repost for Nostr.

https://bitcoinexplainedpodcast.com/@nado/episodes/emergency-broadcast-coldcard-vulnerability