Woofun AI reports that the BIP110 proposal, authored by Brandon Black and compiled by AididiaoJP and Foresight News, has been decisively rejected by the mining community, ending a year-long debate within cryptocurrency Twitter circles regarding @dathon_ohm’s initiative to implement a 'temporary soft fork to reduce data.' The core contention centered on the assertion that certain Bitcoin transactions embed data within locking or unlocking scripts, which external software can interpret as additional information beyond the intrinsic meaning of the Bitcoin script itself.

Proponents of the measure characterized this embedded data as 'junk data' and argued that its reduction justified what they described as the most 'confiscatory' Bitcoin soft fork to date. This proposal was notable for deploying significantly faster than the previous two soft forks and operating with a lower activation threshold, aiming to curtail transaction types that supporters viewed as violating the network's foundational principles.

The fundamental architecture of Bitcoin is defined as an open-access, censorship-resistant distributed ledger, a design choice that establishes its primary value proposition against alternative ledger systems. Any participant willing to pay sufficient transaction fees to incentivize block template builders and miners can append content to the ledger. This openness is not a minor feature but the central utility of the system; without it, the Bitcoin ledger would be functionally indistinguishable from a bowling alley scoreboard, lacking the immutable, permissionless nature that distinguishes it from centralized databases.

The inevitability of usage by individuals or entities that others may dislike is an inherent consequence of this open access, similar to the principle of free speech, which holds no value if it only protects speech that is socially approved. If the ledger were restricted to only include transactions that specific groups approve of, the mechanism would lose its significance and utility as a neutral, global settlement layer. Therefore, the argument follows that there is no justification for censoring how other participants construct their ledger entries, just as one would not accept external censorship of one's own entries.

Proponents of BIP110 often attempted to distinguish between monetary and non-monetary entries, claiming that the restrictions should only apply to the latter.

However, this distinction is technically impossible to enforce within the current protocol. Every transaction on Bitcoin creates a ledger record by satisfying the conditions of a specific locking script, consuming input UTXOs and generating new output UTXOs. The size or complexity of a transaction’s script is irrelevant to node operators or ordinary users for several reasons. First, individual participants generally do not monitor or care about the specific details of other users' transactions, much like one does not concern themselves with what others order at a coffee shop.

Second, Bitcoin nodes themselves do not categorize transactions based on intent; they only validate whether a transaction is valid or invalid based on predefined rules. While verification costs vary—large multisig transactions incur higher costs, while certain Ordinals or OP_RETURN entries are relatively cheaper—the protocol does not differentiate between 'monetary' and 'non-monetary' purposes.

A common analogy used to argue for stricter controls suggests that Bitcoin, like gold, would be a purer monetary asset if it could not be 'used in other ways.' If gold were restricted solely to currency functions and could not be used for jewelry or industrial applications, it might be considered a more stable store of value.

However, it is precisely the physical properties that make gold an excellent currency—such as its malleability and luster—that also drive its popularity in jewelry and industrial sectors. The same logic applies to Bitcoin: because anyone can pay to write data, it is impossible to control how others interpret that data. No matter how script structures are restricted, users will always employ software other than the standard Bitcoin client to interpret these entries in alternative ways. Consequently, 'other uses' are inevitable, just as they are in the gold market. In the gold market, fluctuations in non-monetary demand lead to price distortions; in Bitcoin, surges in block space demand from 'non-monetary' data can result in rising transaction fees.

Despite these parallels, Bitcoin possesses two distinct advantages over gold in managing these alternative interpretations. First, creating Bitcoin transactions that can be interpreted in alternative ways does not directly impact Bitcoin’s market value as an asset to the same degree as non-monetary demand impacts gold. Unlike gold, the volume of Bitcoin used for these 'additional purposes' remains very small relative to the total supply. Second, the Bitcoin protocol was designed from inception with mechanisms to minimize the burden of such 'alternative interpretations' on the verification network.

These mechanisms include limits on block size and the number of signatures (sigops) in transactions, which are the components that incur the highest verification costs for nodes. These early restrictions were implemented specifically to prevent high-frequency, high-volume abuse of the ledger. It is these constraints that have fostered layer-2 innovations such as the Lightning Network, Ark, Spark, and Cashu. When 'non-monetary' data causes a surge in block space demand, it drives users toward these more efficient scaling solutions, which ultimately allow fewer records to be stored on the main chain, thereby preserving the integrity and efficiency of the base layer.

Woofun AI data shows that the rationale behind BIP110 identified as unfounded, the technical specifics of the proposal reveal extensive restrictions on Bitcoin’s scripting capabilities. BIP110 intended to limit the size of locking scripts, restrict the number of alternative scripts available in Taproot, and render Taproot annexes ineffective.

Furthermore, it sought to remove all upgradable witness versions and Tapscript versions, eliminate all upgradable opcodes in Tapscript, and disable specific opcodes such as OP_IF and OP_NOTIF in Tapscript. These restrictions were not permanent for all existing assets; they would only apply to UTXOs created within approximately 52,414 blocks after activation, a period equivalent to about one year. This targeted approach aimed to phase out specific scripting patterns while maintaining compatibility with older, established transactions.

The activation and enforcement mechanisms proposed in BIP110 were particularly aggressive, lowering the miner readiness signal threshold to 55%, a significant drop from the over 90% typically required for previous soft forks. To ensure adoption, the proposal introduced a node enforcement mechanism: if insufficient signaling was detected by block 961,632, nodes adhering to this rule would treat unsigned blocks as invalid. This mechanism was designed to force the changes to be locked in at block 963,648 and fully activated at block 965,664. This timeline represented an unprecedented acceleration in consensus changes, with less than 9 months passing from BIP numbering to activation. The speed of this process meant minimal code review and a disregard for the broader community consensus, raising concerns about the stability and security of the network.

Historically, the most aggressive restrictions on Bitcoin scripts occurred when Satoshi disabled several opcodes in 2010 due to a serious vulnerability identified as CVE-2010-5137. That change was necessitated by a clear security threat, whereas BIP110 was driven by ideological objections to how certain participants used the ledger. The proposal aimed to push through these changes with an unusually low threshold and a compressed timeline, under the pretext that some people were interpreting ledger entries in ways that proponents did not approve of. This approach ignored the long-standing principle that Bitcoin’s consensus rules should only be altered in response to critical security flaws or widely accepted improvements, not to censor specific types of data usage.

Community reaction to BIP110 was overwhelmingly negative, with developers, investors, KOLs, and businesses voicing strong opposition. Ironically, those who utilized the 'opposed' data had already updated their software to prepare for the possibility of activation. Even if BIP110 had succeeded, these users could still embed similar data using external software to interpret entries in alternative ways. Many observers predicted this outcome, noting that on an open public ledger, it is impossible to restrict how others use external software to interpret entries. The inevitability of alternative interpretations means that any attempt to restrict data embedding is fundamentally flawed and unenforceable in the long term.

In conclusion, BIP110 attempted to restrict how users of an open-access ledger could utilize the network, a goal that is technically impossible and philosophically misaligned with Bitcoin’s core values. The problems it claimed to address, such as verification costs and block space usage, are already effectively managed by Bitcoin’s existing protocol constraints. By attempting to force these changes through with an irresponsible timeline, hasty code review, and disregard for community consensus, the proposal failed to gain traction.

Fortunately, Bitcoin is not such a fragile system, and such reckless attempts at modification were rejected by the network. Miners clearly signaled their opposition, and by August of this year, this 'attack' on Bitcoin’s consensus rules ended in failure. This outcome reinforces the resilience of the network, allowing it to continue producing blocks at a steady pace, with the next block serving as a testament to the enduring strength of decentralized consensus..