Block Size Wars, BIP-110, and Bitcoin Consensus with Samson Mow | Bitcoin Infinity Show #215

— BIP-110 and mandatory signalling: Samson Mow argues BIP-110 lacks broad consensus and represents a 1% attack — low-cost pressure on miners via node signalling without meaningful economic backing. He distinguishes it sharply from BIP-148, which had 80% miner hashrate and ecosystem support for SegWit.

— BIP-148 vs. BIP-91 activation history: BIP-148 did not activate SegWit; BIP-91 did. BIP-148 was a nudge that pushed a single holdout (Jihan/Bitmain) to step aside. Consensus existed for SegWit's malleability fix; BIP-110 lacks equivalent broad agreement.

— Technical viability concerns: NUTS (BIP-110 client) does not follow its own specification; recent bugs were found. No tested deployment path exists for miners; flipping the signalling bit does not guarantee block compliance without running unproven software.

— Divisive rhetoric and mob dynamics: Samson witnessed coordinated attacks on neutral voices (Jimmy Song, Lynn Alden, Plan B). BIP-110 supporters frame disagreement as corruption ("Big Bitcoin," Blockstream, suits) rather than engaging substantive technical objections.

— Minority fork risk: If only ~15% of hashrate signals and the broader network rejects non-compliant blocks, signalling miners mine a worthless fork. No preparation or dialogue with major pools suggests participants have not gamed out failure scenarios.

— Process and precedent: Samson advocates consensus-building, not unilateral change. He offered to work on anti-spam measures through standard development channels but rejects mandatory deadlines on a $1 trillion network.

— Do not assume miner signalling equals commitment: Miners face severe financial risk if they signal for BIP-110 but the broader network rejects it. They must run compatible software, maintain revenue, and cover operational costs during a potential fork. Retail nodes signalling does not force miner action.

— Watch for ecosystem coordination before mandatory signalling: Serious activation requires documented testnet deployment, developer review, and explicit public commitments from mining pools and exchanges. The absence of this suggests low probability of successful consensus.