Murchandamus

Murchandamus Joins Pleb Underground For a BIP-110 Chat

- BIP-110 mandatory signaling activation in 16 days lacks sufficient support; only ~1% of hash rate and 11.8% of listening nodes currently signal compliance. - OP_RETURN limit increase (from 80 to 420 bytes, permitting multiple outputs) represents harm reduction philosophy: directing data into prunable outputs rather than the UTXO set. - Mempool policy vs. consensus rules trade-off: Policy-level filtering fails once miners gain financial incentive; consensus-level enforcement is slow and difficult to specify precisely. - Arbitrary data encoding is technically unavoidable due to Bitcoin's flexible scripting; attackers can encode via opcodes, public key hashes, or multisig constructions regardless of restrictions. - UTXO set bloat concerns are manageable because block space is limited to 4 MB per block (~54 GB/year if fully consumed for data), and disk/storage costs decline exponentially over time. - Bitcoin Core's recent optimizations include 35% IBD speed improvement via parallel thread lookup of UTXOs and more efficient LevelDB parameters in recent maintenance releases (31.1, 30.3, 29.4).