You might have heard about BIP-110; here’s why this fork is not just contentious, but it is built on a misunderstanding of Bitcoin node functionality and the network’s governance model. Practically speaking, BIP-110 is poised to face rejection due to its lack of support from critical stakeholders.
This article represents a counterpoint piece. Opinions expressed here are entirely the author’s and do not necessarily reflect those of either BTC Inc or Bitcoin Magazine.
BIP-110 suggests a consensus change to curtail the arbitrary data that can be included in Bitcoin transactions, aiming to impose limits on scripting capabilities. The proposal, led by the pseudonymous developer Dathon Ohm and endorsed by the Knots community—a separate Bitcoin implementation created by Luke Dashjr and his supporters—is set for a mandatory signaling phase in the near term, potentially resulting in a mandatory consensus rule change within the Bitcoin Core framework.
For BIP-110 to take effect, it will necessitate strong miner support; however, current miner signaling for this proposal remains well below the necessary threshold, with less than 1% of the current hashrate signaling support as of the latest reporting period.
The Functionality and Limitations of Bitcoin Nodes
Debates around BIP-110 often revolve around the perceived influence of Bitcoin full nodes. Some influencers, such as Knut Svanholm, have amplified the role of full nodes to an almost mythical degree, but these views are not technically sound. Recent public statements have romanticized the notion that every individual running a node somehow wields significant influence over the network’s direction, which fundamentally misrepresents the actual purpose and power of a node.
Knut’s statements, while eloquent, are ultimately misinformed. A Bitcoin node, by definition, is a full replication of the entire Bitcoin blockchain, including transaction data and block headers. Its primary purpose is to allow users to independently verify the integrity of Bitcoin’s ledger in accordance with the established consensus rules.
Nodes offer critical user benefits, including enhanced privacy. For instance, when using a local node, users can retrieve their Bitcoin balances directly from the blockchain without revealing their transaction history to third-party services. This approach contrasts with many mobile wallet services that rely on external servers to provide balance information, potentially compromising user privacy.
Additionally, nodes play a vital role in maintaining network consensus. Miners who operate nodes can gain insight into the network’s current state and help ensure consistency across all participants. While running a node doesn’t allow users to alter consensus rules directly, it does provide them with a means of assurance that the data they interact with is accurate and compliant with Bitcoin’s rules.
Despite some beliefs to the contrary, running a node does not grant users a direct stake in Bitcoin’s governance. Satoshi Nakamoto emphasized that Bitcoin’s security and transaction validation depend on a proof-of-work system, where computational power—not node count—determines consensus. Miners, as the primary enforcers of this system, are heavily influenced by economic and developer communities, creating a complex ecosystem that is difficult to manipulate.
Nodes primarily serve as a verification tool, confirming that a user’s interaction with the Bitcoin network aligns with its consensus rules. However, nodes alone cannot enforce or change these rules. Users attempting to modify the consensus through node operations effectively create a separate chain, diverging from the network’s established protocol.
Historical Precedents and Consensus in Action
In past instances of Bitcoin consensus disputes, such as the 2017 Bitcoin Cash fork, the power dynamics of nodes and heavy protocol stakeholders were evident. While Bitcoin nodes technically supported the Bitcoin Cash fork, this outcome was significantly influenced by strong backing from exchanges, major investors, media outlets, and influential developers. The nodes’ support in that instance was underpinned by broader economic activity and consensus within the community, a level of backing that BIP-110 lacks today.
The contrast between past and present consensus battles is stark. In the Bitcoin Cash fork, nodes were bolstered by economic nodes—such as exchanges—which processed significant transaction volumes. In the case of BIP-110, such economic and developer support is absent. Noteworthy Bitcoin advocates, including Michael Saylor, have publicly expressed opposition, leaving the proposal without key influencers’ endorsement.
While end users do have some indirect influence via their spending patterns, the majority participate through third-party services, such as mobile wallets and exchanges, which operate within the protocol parameters set by developers. This reliance on third-party services means most users have limited direct say in governance matters, relying instead on signals from trusted intermediaries to form opinions on consensus matters.
A recent example of this dynamic is evident in the actions of Foundry, a major mining pool, which recently began soliciting feedback from its miners on BIP-110. Miners possess the potential to signal their support or opposition through their hashrate, effectively casting a vote on the proposal’s fate. However, voter apathy among miners currently leans toward the status quo, signaling that the proposal will likely fail to gain traction.
As BIP-110’s signaling phase progresses, the current lack of consensus among major stakeholders—developers, investors, and miners—indicates a likely chain split in the near future. Such a split could negatively impact Bitcoin’s Lightning network, particularly for users relying on BIP-110-compliant nodes. Should the proposal fail, it would create a smaller, fragmented network, likely necessitating changes to its proof-of-work system to sustain viability.
