BIP-110, the Reduced Data Temporary Softfork, proposes a one-year temporary consensus soft fork that introduces seven new validation rules to restrict arbitrary data in Bitcoin transactions. It limits new non-OP_RETURN scriptPubKeys to 34 bytes (OP_RETURN up to 83 bytes), caps most data pushes and witness elements at 256 bytes, restricts Taproot control blocks to 257 bytes, and invalidates Taproot annexes, undefined witness versions, and specific opcodes (including OP_SUCCESS* and OP_IF/OP_NOTIF) in Tapscripts. Pre-activation UTXOs remain spendable under the old rules, and all restrictions automatically expire after roughly 52,416 blocks. The BIP itself identifies two key technical tradeoffs: capping control blocks constrains large on-chain script trees, which could complicate advanced constructions like BitVM (though proponents note these can use testnets or sidechains temporarily). It also temporarily disables certain upgrade hooks used in future soft forks, though this is viewed as low-risk given normal activation timelines. Critics raise additional concerns. The proposal’s 55% hashrate signaling threshold and UASF-style activation carry a risk of chain splits or reorgs if miner support remains low, a point Adam Back has highlighted while describing the proposal as technically flawed. The Taproot restrictions may also slow future innovation in complex scripts and covenants. While supporters argue it reduces node resource burdens from data bloat and refocuses Bitcoin on monetary use, skeptics contend the practical benefits are limited compared to the risks of precedent-setting transaction filtering and reduced neutrality. In summary, BIP-110 trades short-term limits on data-heavy and experimental uses for stronger monetary prioritization, at the cost of potential innovation friction and activation risks. It remains highly controversial as of July 2026. -grok