The Soul of Bitcoin: BIP-110 and the Unspoken War for the Protocol's Conscience

We chart the code, but the soul chooses the path. This is not a line from a blockchain manifesto; it is the quiet truth that surfaces every time a protocol faces a fork—be it in the chain or in the minds of its stewards. Last week, the Bitcoin community woke to a proposal that tested the very axiom of its existence: BIP-110. On paper, it is a soft fork. In practice, it is a referendum on whether Bitcoin can still claim to be a neutral ledger or if it has become a battleground for conflicting visions of digital sovereignty. I have been watching Bitcoin governance debates since the Ethereum Classic schism in 2017, when I volunteered to translate technical whitepapers for Spanish-speaking newcomers. That experience taught me that the most dangerous conflicts are not between codebases but between the unspoken assumptions behind them. BIP-110, as articulated by its anonymous authors, aims to limit arbitrary data in Bitcoin transactions to 34 bytes, revive the OP_RETURN opcode for metadata, and place temporary restrictions on Taproot outputs. The intended target is clear: the Ordinals and inscription ecosystems that have turned Bitcoin blocks into a gallery of memes and digital artifacts. But the proposal’s most radical feature is not the data cap—it is the reduction of the activation threshold from 95% to 55%. To understand why this matters, we must first grasp the context. Bitcoin’s governance has always been conservative by design. The 95% miner signaling requirement ensures that no soft fork activates without overwhelming consensus from the economic majority. This rule has protected the network from factional takeovers and preserved the simplicity that makes Bitcoin a reliable store of value. But with the rise of inscriptions—enabled by Taproot in 2021—block space has become congested with low-value transactions that inflate UTXO sets and bloat node requirements. Mining pools like Foundry and Antpool have publicly grumbled about the operational costs. The noise is real. Yet the community’s response has been fragmented. Some call for a clean-up, others for tolerance. BIP-110 emerges as the most aggressive clean-up attempt. Let me be clear: I have seen this pattern before. During the 2020 DeFi Summer, I published a detailed critique of DAI’s over-collateralization risks, warning that trustless promises often hide systemic fragility. The same caution applies here. BIP-110’s technical implementation is dangerously flawed. Within days of its release, developer Dathon Pwn discovered the BlockSlop consensus vulnerability: nodes running BIP-110’s modified Bitcoin Core would generate a historical fork when syncing old blocks because of inconsistent rule enforcement. This is not a edge-case bug; it is a fundamental break in the invariant that time is linear and consensus is unified. If exploited, an attacker could force a chain split without a single 51% attack. Based on my audit experience during the 2022 bear market, where I spent six months analyzing failed L1 protocols, I can say that the vulnerability alone should have disqualified the proposal from serious consideration. But the story does not end with a bug. The lowering of the activation threshold to 55% is what elevates this from a technical proposal to a governance coup. Historically, every successful soft fork—SegWit, Taproot—required years of deliberation and near-unanimous miner support. The 95% rule is not an arbitrary number; it is the mechanism that ensures no minority can force a change on the majority. By proposing 55%, the authors are effectively saying: ‘We consider a slim majority of miners sufficient to override the will of the node operators and users.’ This is the antithesis of the decentralization philosophy I have advocated for since my first essay on Ethereum Classic’s ‘Code is Law’ doctrine. The contrarian angle, however, is that BIP-110 is not entirely without merit. The UTXO bloat from inscriptions is a real problem. If left unchecked, the average node hardware requirements will increase, slowly eroding the barrier to entry for participation. I have seen this dynamic before: in my 2021 NFT soul-bound token project for preserving indigenous Mexican cultural heritage, we deliberately avoided storing metadata on-chain because we understood the cost of data permanence. But the solution is not to freeze innovation through a clumsy data cap. The better path is to encourage off-chain storage solutions like RGB or Taproot Assets, which I researched extensively while writing my manifesto on sovereign data rights. BIP-110’s heavy-handed approach would lock out all future experimentation, including promising second-layer scalability solutions that rely on Taproot’s scripting capabilities. Furthermore, lowering the threshold to 55% opens a Pandora’s box of regulatory scrutiny. If Bitcoin can be altered by a simple majority of miners, regulators in jurisdictions like the EU and the US—where I have engaged with policymakers on AI ethics—will argue that the network is no longer sufficiently decentralized to qualify as a commodity. The SEC could use this as ammunition to categorize inscriptions as unregistered securities, since their value would depend on the whims of a small group of miners. Michael Saylor, a vocal opponent of the proposal, understands this risk well. His opposition is not just philosophical; it is grounded in the pragmatic need for institutional clarity. Let us look at the numbers. Miner signaling data from major pools shows support for BIP-110 hovering below 3% as of July 20, 2025. This is not a typo. The proposal has almost no industrial backing. But the debate itself is significant because it exposes a deeper fracture: the Bitcoin community is no longer a single tribe. There are the ‘gold bugs’ who see Bitcoin purely as a store of value, the ‘degen builders’ who want it to be a platform for assets and applications, and the ‘protocol purists’ who believe that any change—even a soft fork—is an attack on immutability. BIP-110 is the first time these three groups have collided so directly. I recall a similar tension during the 2021 NFT explosion when I collaborated with a small group of artists. We chose to issue identity tokens on a second-layer solution to avoid bloating the main chain. That experience taught me that community-led initiatives can flourish without centralized protocol changes. The threat of BIP-110, even if it fails, could accelerate migration to alternative storage methods. That is a subtle but positive outcome: the market will self-correct, not through a vote but through adoption of more efficient technologies. Yet the most dangerous aspect of BIP-110 is not the proposal itself but the precedent it sets. If the community allows a poorly coded, vulnerable, and insufficiently debated proposal to remain in the public discourse without formal rejection, it signals that the governance process is weak. We need a clear rejection signal—not just from miners but from node operators and users. The User-Activated Soft Fork (UASF) mechanism exists as a last resort, but using it over such a flawed proposal would be a catastrophic misallocation of energy. History does not just repeat; it forks. The Bitcoin chain has already forked once over block size disagreements. A second fork over data limits would fracture the community permanently, creating two Bitcoins whose shared history becomes a weapon for mutual delegitimization. I wrote a 10-part series on ‘The Illusion of Decentralization’ in 2022, analyzing how failed L1s centralized after crises. The lesson was that the perception of security often rests on invisible consensus rituals. BIP-110 is testing whether those rituals still hold. So far, they do. The overwhelming rejection by developers, miners, and key holders suggests that the conservative default is intact. But the fact that the proposal was even published reveals a willingness to circumvent the traditional governance channels. That willingness will not disappear if BIP-110 is rejected. It will lie dormant until the next stress point. What then is the takeaway? The soul of Bitcoin is not in its code—it is in the collective decision-making process that resists shortcuts. We chart the code, but the soul chooses the path. BIP-110 is a reminder that the path must be chosen deliberately, not by a slim majority or a technical workaround. The community’s next steps should be to accelerate research into sustainable data storage layers, to strengthen the social contract that prohibits lowering approval thresholds, and to reaffirm that the 95% rule is not a bug to be patched but a feature to be cherished. In the coming months, I will be tracking three signals: the patch for BlockSlop in Bitcoin Core’s GitHub, any coordinated statement from the Bitcoin Core maintainers group, and the hash power distribution among pools in August when the miner signaling window opens. For now, the wise move is to ignore the noise and reinforce the basics—run a full node, verify your own transactions, and remember that the most powerful consensus is the one that never needs to be invoked. Code is law, until it isn’t. But for Bitcoin to remain the sovereign money we believe in, the law must be written slowly and changed even slower. BIP-110 is a hurried script. Let it remain unwritten.