BIP-110, also known as the "Reduced Data Temporary Softfork" (RDTS), has emerged in public discourse as a controversial attempt to curb the proliferation of data deemed "non-financial" on the Bitcoin network. Spearheaded by the pseudonymous developer Dathon Ohm and backed by Luke Dashjr, this proposal sought to restrict Ordinals inscriptions, BRC-20 tokens, and the Runes protocol—seen by some in the community as spam—for a period of one year. Technically, the project imposed strict limitations on output sizes and data insertion via a User-Activated Soft Fork (UASF) designed to pressure miners through network nodes.
Despite its bold ambitions, the proposal appears destined for failure. Miner support remains marginal, hovering around 1%, with only a tiny fraction of total hashrate expressing interest in the upgrade. Furthermore, key figures within the ecosystem, including influential developers and thought leaders, have leveled sharp criticism, highlighting design flaws and a lack of rigor. More significantly, the dominant Bitcoin Core client has already signaled that it will not integrate the update. As things stand, if the project’s proponents attempt to force the protocol through, they would merely isolate themselves on a minority chain with no economic viability.
Beyond the failure of BIP-110, the issue of blockchain bloat remains a real and persistent technical challenge. The debate is less about historical data storage—where growth is capped by block size—and more about the explosion in the number of UTXO (Unspent Transaction Outputs). The accumulation of these "dusty" transaction outputs forces nodes to saturate their RAM, thereby increasing the hardware requirements needed to validate the network. This phenomenon poses a latent threat to decentralization, as it could, in the long term, limit Bitcoin maintenance to institutional infrastructure at the expense of independent users.
Faced with these challenges, the community is now prioritizing solutions rooted in technological innovation rather than arbitrary usage restrictions. Projects such as Utreexo, which proposes compressing the entire UTXO set, or improvements to synchronization tools like AssumeUTXO, illustrate a commitment to increasing protocol resilience without compromising its fundamental neutrality. By favoring software engineering to lighten the load on nodes, the ecosystem is proving that the challenge posed by spam can be addressed through more robust and consensual methods than attempts at soft-fork-driven chain splits.