I can’t remember the last time so many high-profile Bitcoiners lined up to discuss something and even @saylor chime in. So, let's talk a bit about it. BIP-110, in plain English: A one-year “temporary” soft fork intended to throttle arbitrary data storage on Bitcoin. Why this is even on the table: Bitcoin transactions already offer multiple nooks where extra bytes can be tucked away like scripts, OP_RETURN, witness data, Taproot paths, and more. Critics argue that this turns Bitcoin into a data landfill: it crowds out low-fee payments, raises the cost of running a full node, and slowly erodes decentralization as resource requirements creep upward. BIP-110 is framed as a response to that trajectory. The case for BIP-110: Supporters, including several prominent voices, see it as an ugly but necessary circuit breaker. Their view: non-monetary bloat doesn’t scale, and protecting node affordability, decentralization, and Bitcoin’s monetary role is worth closing the door on “everything on-chain” experimentation. The case against it (why the pushback is so intense): Critics, Michael Saylor among them, say it conflicts with Bitcoin’s core logic: ❶  Neutrality Bitcoin can’t reliably infer intent or “purpose,” so consensus rules should stay content-agnostic. Once you change consensus to penalize a controversial use case, you establish a precedent for doing it again when the next controversy shows up. ❷  Optionality and Innovation It narrows the upgrade surface area: future Taproot techniques, BitVM-style constructions, Miniscript patterns, niche pre-signed setups (essentially anything that depends on flexible expressivity) could be constrained or broken. Even the possibility can chill builders. ❸ Risk and Coordination “Temporary” consensus rules are a footgun → Activation and expiry edge cases, time-bound validity quirks, and higher chain-split risk. A lower signaling bar combined with aggressive enforcement raises the coordination temperature. If the real goal is cost control, critics argue the safer path is policy and relay choices, fee pressure, pruning, and L2 scaling, not consensus surgery. If you want one takeaway: BIP-110 isn’t just a fight about data. It’s a fight about what Bitcoin is allowed to be. Monetary purity and node sustainability vs. neutrality, openness, and permissionless evolution. Outcomes depend on $BTC node/miner/user adoption. As with any consensus change, it carries real risks regardless of intent. What do you think about BIP-110?