The Bitcoin development community faces a potential consensus split as BIP-110, a proposal to limit arbitrary data in transactions, heads toward a signaling deadline with minimal miner support. The situation offers important lessons for blockchain professionals about how protocol governance actually functions versus popular misconceptions.
Understanding the Proposal and Current Support
BIP-110, led by pseudonymous developer Dathon Ohm and backed by the Knots community, proposes restricting Bitcoin's scripting capabilities to limit certain data types in consensus-valid transactions. The proposal has attracted support from some node operators, particularly those running alternative implementations like Knots on platforms such as Start9 and Umbrel.
Current miner signaling stands at less than one percent, making this one of the least-supported soft fork attempts in Bitcoin's history. The proposal lacks backing from most senior Bitcoin Core developers, who remain either opposed or apathetic to the changes. Major industry figures, including Michael Saylor, have publicly opposed the fork.
The Reality of Bitcoin Consensus
A central misconception driving BIP-110 support is the belief that running full nodes alone can change Bitcoin consensus rules. This fundamentally misunderstands how Bitcoin governance operates.
Bitcoin nodes serve specific functions for professionals in the ecosystem:
- Verifying transaction history and supply integrity against consensus rules
- Providing privacy by eliminating third-party balance queries
- Relaying transactions across a censorship-resistant network
- Enabling block template assembly for miners with sufficient hashrate
However, nodes cannot unilaterally change consensus without support from multiple stakeholder groups. Historical analysis identifies six key pillars: economic nodes, investors, media influencers, miners, protocol developers, and application developers.
The 2017 UASF succeeded not merely through node count, but because it had backing from protocol developers, investors, and exchanges with significant economic weight. BIP-110 lacks this coalition.
Implications for Blockchain Professionals
For developers and technical professionals, this situation underscores critical realities about Bitcoin protocol work. Foundry, one of the world's largest mining pools, recently allowed miners to vote on BIP-110 with their hashrate, with non-voters defaulting to opposing the change.
A chain split appears likely in coming weeks, which could impact Lightning Network wallets running on BIP-110-compliant nodes. Professionals working on Bitcoin infrastructure should prepare for this eventuality and understand that the resulting fork would likely represent a small minority chain.
For those pursuing careers in Bitcoin development, this episode demonstrates that successful protocol changes require building consensus across diverse stakeholder groups—not just technical merit or grassroots node support.
