@04c915da…3dfbecc9 @84630768…fa019ae8 You speak like a midwit who just discovered “from the outside” is a get-out-of-reading-the-BIP-free card. “Post-Core-30 Bitcoin (which didn’t change consensus) has not” , yeah, genius, that’s the whole fucking problem. Core 30 nuked the OP_RETURN limit from 83 bytes to 100k, blowing the doors off for even more inscriptions, BRC-20 trash, and every degen JPEG farmer turning the chain into a decentralized OnlyFans hard drive… all while pretending “no consensus change” makes it pure and innocent. Congrats, your node now costs an extra AWS subscription and your “neutral” take costs the rest of us actual decentralization. BIP-110 doesn’t “have potentially major issues.” It drops a hard “fuck you” on spam at the consensus level: 34-byte output cap, 83-byte OP_RETURN, 12-month soft fork that shrinks the attack surface, slashes node storage costs, and reminds everyone Bitcoin is money, not Imgur with fees. Kratter laid it out in plain English (and actual code) while you sat huffing copium, defending the bloated version and then acting shocked a fix even exists. You’re not “in the middle” taking shit from both sides, you’re the human equivalent of an unpruned OP_RETURN: zero value, maximum bloat, everyone wishes you’d just get filtered already. Run BIP-110, read the actual proposal, or keep LARPing as the enlightened observer while real node runners laugh and your timeline gets ratio’d into oblivion.