Have you ever watched a carefully planned change to a major network get almost completely ignored by the people who actually keep it running? That is pretty much what happened with BIP-110. The proposal aimed to limit certain non-financial data on Bitcoin, yet the market delivered a clear verdict. Only a tiny fraction of miners signaled support, a short-lived minority chain appeared and then faded, and today the enforcement nodes can be counted on two hands. Blockstream CEO Adam Back recently weighed in again, reminding everyone that attempts to force new rules onto Bitcoin tend to meet the same fate.
Why Adam Back Renewed His Criticism of BIP-110
On November 3 Adam Back posted a pointed message that quickly circulated among Bitcoin watchers. He pointed to earlier commentary from a well-known advocate and described it as a masterclass in how Bitcoin actually works. His core line was straightforward: attempts to impose your views on Bitcoin get market rejected. He added that discussions about established rules help people grasp the idea of immutability. In my view that last point lands especially hard because it cuts through a lot of the noise that usually surrounds these debates.
Back did not stop at one post. In a follow-up he stressed that the real issue is not necessarily the data payload itself. The market, he argued, will resist efforts to override consensus even when supporters believe the change is helpful. He also claimed the proposal failed its first technical gate quite badly. That combination of market rejection and technical shortcomings forms the heart of his latest remarks.
This is not a brand-new stance for him. Earlier in the year he had already voiced concerns that the proposal risked splitting the network. Similar doubts came from other prominent voices who questioned whether limiting particular transaction types justified altering consensus rules. The renewed comments feel less like a sudden outburst and more like a quiet confirmation that the earlier warnings held up.
The Core Idea Behind BIP-110
BIP-110 carried the formal title Reduced Data Temporary Softfork. Its author set out to place temporary limits on arbitrary data stored inside Bitcoin transactions for roughly one year. The rules would have capped standard transaction output scripts at 34 bytes, with a limited exception for OP_RETURN outputs up to 83 bytes. Additional limits would have applied to certain data fields and to aspects of Taproot transactions.
Supporters saw a practical benefit. They argued that inscriptions and similar non-financial data create unnecessary storage pressure on nodes. Restricting that activity, they believed, could lower operating costs and help keep Bitcoin focused on payments. One developer closely tied to alternative node software and a mining pool stood among the more visible backers.
Critics took a different view. Changing consensus rules to reject specific transaction types, they said, risks undermining the network’s neutrality. Once you start filtering content by category, the argument goes, you open the door to future pressure over other kinds of data. That philosophical gap proved difficult to bridge.
How the Activation Attempt Unfolded
The proposal required 55 percent miner signaling for voluntary activation. During the relevant window only 2.53 percent of blocks carried the signal. That shortfall made voluntary activation impossible under the stated threshold. On August 8 nodes enforcing the new rules rejected a block that the main network accepted, producing a brief chain split.
The minority branch managed just two blocks before falling behind. Coverage at the time showed the new chain struggled to gather enough hash power to keep producing blocks at a regular pace. After the split some supporters floated the idea of switching the minority network’s proof-of-work algorithm to something other than SHA-256. That move would have severed any remaining dependence on the existing mining ecosystem.
I’ve found that these moments reveal a lot about how Bitcoin governance actually functions in practice. Softforks that lack broad miner support rarely gain lasting traction, and the market tends to treat minority chains with skepticism. The rapid disappearance of meaningful hash rate on the BIP-110 branch fits a familiar pattern.
Current Node and Signaling Numbers
Recent measurements paint a stark picture of remaining support. On November 3 one monitoring service recorded only eight enforcing nodes out of 18,870 observed nodes. That works out to roughly 0.04 percent. During the same difficulty period zero BIP-110 signaling blocks appeared among 649 mined blocks.
These figures do not capture every privately run node, of course. They do, however, offer a useful snapshot of publicly visible participation. Bitcoin Core made up nearly 90 percent of the monitored nodes while an alternative implementation accounted for about 10 percent. Running the alternative software does not automatically mean a node enforces BIP-110, because the software allows different configurations.
The current numbers stand in sharp contrast to earlier periods when several hundred nodes reportedly ran compatible software. The drop suggests that even among those who initially experimented with the rules, sustained commitment has been limited.
Attempts to impose your views on bitcoin get market rejected.
Market Rejection as a Recurring Theme
Back resurfaced an older observation of his during the latest discussion: time is a flat circle. The phrase captures the sense that contentious fork attempts keep returning in different packaging. Each time the market has tended to favor the rules already in place. Supporters of change often argue that their proposal addresses a genuine problem. Opponents counter that the cost of altering consensus outweighs the benefit.
Perhaps the most interesting aspect is how consistently the economic majority has aligned with the status quo. Hash rate, exchange support, and user preference have repeatedly concentrated on the chain that continues under existing rules. That pattern does not mean every future change is doomed. It does suggest that proposals need unusually broad buy-in before they can stick.
In my experience watching these episodes, the technical merits of a proposal matter less than the social and economic coordination required to activate it. BIP-110 offered a clear technical design. What it lacked was the critical mass of miner signaling and node adoption needed to overcome inertia.
Storage Concerns Versus Neutrality Arguments
Supporters of the data restrictions focused on practical node operation. Larger blocks filled with non-financial data raise the cost of running a full node. Over time that pressure could discourage ordinary users from verifying the chain themselves. Restricting certain data types for a limited period looked, to them, like a reasonable temporary measure.
Opponents replied that Bitcoin has always treated transaction data as neutral. Once the network begins filtering by content category, the principle of permissionless inclusion starts to erode. They worried that today’s storage concern could become tomorrow’s content concern. That philosophical disagreement never really closed.
- Supporters emphasized lower storage costs and a sharper focus on payments
- Critics stressed the risk of opening the door to broader filtering
- Both sides agreed the change would alter consensus rules
- Neither side persuaded the other to shift ground significantly
The temporary nature of the proposed softfork was meant to reduce the stakes. A one-year experiment could be evaluated and then allowed to expire. In practice the market never gave the experiment a serious run.
Lessons From the Short-Lived Chain Split
When the minority nodes rejected a main-chain block on August 8, the network briefly demonstrated what a contested softfork looks like in real time. Two blocks appeared on the new branch. Then the hash rate advantage of the original chain reasserted itself. The minority branch fell behind and never recovered meaningful momentum.
Discussions about changing the proof-of-work algorithm on the minority side highlighted how far some supporters were willing to go. Switching algorithms would have created an entirely separate mining market. That step would also have removed any remaining claim to continuity with the original Bitcoin chain. Most observers treated the idea as a last-resort option rather than a viable path forward.
I’ve noticed that chain splits of this kind often serve as stress tests. They reveal how quickly economic activity and hash power reconverge around the dominant set of rules. In this case the reconvergence happened within a very short window.
What Limited Node Counts Tell Us
Eight enforcing nodes out of nearly nineteen thousand is a striking ratio. Even allowing for undercounting of private nodes, the visible footprint remains tiny. Zero signaling blocks in a recent difficulty period reinforces the impression that miner interest has effectively vanished.
Node software choice adds another layer. The dominant client continues to run the vast majority of observed nodes. Alternative implementations exist and serve useful purposes for some operators, yet they do not automatically translate into support for any particular softfork. Configuration choices matter more than the binary of which client is installed.
Earlier reports of several hundred compatible nodes show that interest was higher at one point. The subsequent decline suggests that many operators who tried the software later disabled the enforcement rules or switched back. Sustained voluntary adoption never materialized.
Immutability as a Practical Reality
Back’s emphasis on immutability is not abstract philosophy. It reflects the observed behavior of the network over multiple contentious episodes. When a proposed rule change fails to attract sufficient economic support, the existing rules continue. That continuity is what many participants value most.
Some readers may feel frustrated by the difficulty of enacting change. Others see the high bar as a feature rather than a bug. A system that can be altered too easily risks losing the very properties that make it useful as a neutral settlement layer. The BIP-110 episode illustrates how that high bar operates in practice.
In my own reading of these events, the market’s rejection does not mean the underlying storage concern is imaginary. Node operators do face rising resource demands. The debate is really about the proper method for addressing those demands. Softforks that alter consensus remain one of the most costly tools available, and the network has shown it prefers other approaches when possible.
Broader Implications for Future Proposals
Any future attempt to restrict data types or adjust consensus rules will face the same coordination challenge. Proponents will need far higher levels of miner signaling and node adoption than BIP-110 ever achieved. Technical soundness alone is unlikely to be enough. Social consensus and economic alignment remain decisive.
The temporary character of the proposal was intended to lower the risk. Even that safeguard failed to generate the necessary support. Future designers may need to explore mechanisms that require even less disruption or that can be tested more thoroughly before activation attempts.
One practical takeaway is the value of early, broad signaling data. Waiting until a formal activation window to discover that support sits at a few percent wastes time and attention. Transparent tracking of interest throughout the discussion phase can help everyone calibrate expectations more realistically.
The Role of Public Commentary
Public statements from figures like Adam Back serve as coordination signals of their own. When a well-known voice describes a proposal as having failed its first technical gate, that assessment influences how others allocate their attention. The same is true for commentary that frames the episode as another demonstration of market rejection.
These statements do not decide outcomes by themselves. Hash rate and node software choices do. Still, they help shape the narrative within which operators make their decisions. Clear, repeated articulation of the immutability principle reinforces the high bar that any consensus change must clear.
I’ve found that the most useful commentary tends to stay close to observed data rather than pure advocacy. Pointing to the actual percentage of signaling blocks or the measured node counts keeps the conversation grounded. Emotional language can mobilize supporters, yet it rarely changes the underlying economics.
Looking at the Numbers in Context
A signaling rate of 2.53 percent against a 55 percent threshold is not a near miss. It is a decisive shortfall. Likewise, eight enforcing nodes against nearly nineteen thousand observed nodes is not a temporary dip. It is residual activity. Those ratios help explain why Back described the outcome as market rejection rather than a close contest.
| Metric | BIP-110 Result | Implication |
| Miner signaling | 2.53 percent | Far below 55 percent threshold |
| Enforcing nodes | 8 of 18,870 | Approximately 0.04 percent |
| Signaling blocks in recent period | Zero of 649 | No ongoing miner interest |
| Minority chain blocks | Two | Failed to sustain production |
The table summarizes the key quantitative outcomes. Each line points in the same direction. Support never approached the levels required for a successful softfork of this type.
Why Neutrality Arguments Resonated
Many participants who might have been sympathetic to the storage concern still hesitated over the method. Altering consensus to exclude certain data felt like a larger step than the problem justified. Once that principle is breached, the argument runs, future proposals could target other categories of data for different reasons.
That caution is not unique to this episode. Similar concerns have appeared whenever proposals touch the rules that determine which transactions are valid. The consistent preference for preserving neutrality has shaped the outcome of several earlier debates as well.
Supporters countered that temporary, narrowly defined limits are not the same as permanent content filtering. The market, however, appeared unconvinced. The gap between those two interpretations remained wide enough to prevent coordination.
Practical Realities for Node Operators
Running a full node already carries non-trivial costs in bandwidth, storage, and time. Additional data that does not serve the monetary function of the network increases those costs. Operators who feel the pressure most acutely are often the ones most open to restriction proposals.
Yet the same operators also value the ability to verify the chain without relying on third parties. If enforcement of new rules requires ongoing social coordination and carries the risk of temporary chain splits, many will choose the simpler path of staying with the dominant ruleset. That calculation helps explain the sharp drop in enforcing nodes over time.
Alternative approaches such as better pruning tools, more efficient data encoding, or fee-market adjustments may ultimately prove more durable. They avoid the high coordination cost of consensus changes while still addressing resource pressure.
The Persistence of Contested Ideas
Back’s remark that time is a flat circle captures an important dynamic. Ideas that fail in one form often reappear later in modified packaging. The underlying tension between data openness and resource costs is unlikely to disappear. Future proposals will almost certainly revisit related questions.
Each cycle, however, leaves a clearer record of what the market will and will not accept. The BIP-110 episode adds another data point. Softforks that lack broad miner and economic support tend to remain minority experiments. That pattern is now well established.
For those who continue to believe restrictions are necessary, the lesson may be that technical design must be paired with far more extensive outreach and demonstrated support before any activation attempt. For those who prioritize neutrality, the outcome reinforces the resilience of existing rules.
Closing Thoughts on Consensus and Market Signals
The story of BIP-110 is ultimately a story about how Bitcoin absorbs and rejects proposed changes. A well-intentioned effort to limit certain data types met a decisive lack of miner signaling, a brief and unsuccessful chain split, and a rapid decline in node enforcement. Adam Back’s recent comments simply underline what the numbers already show.
Market rejection is not always polite or gradual. Sometimes it is abrupt and quantitative. In this case the percentages spoke clearly. Whether future proposals learn from that clarity remains an open question, but the record of this episode is now part of the public history of the network.
I’ve come to see these moments as useful stress tests rather than pure setbacks. They force participants to articulate their priorities and reveal where genuine coordination is possible. The high bar for consensus change continues to protect the properties that many users value most. That protection is not free of trade-offs, yet it has proven remarkably durable so far.
As the network continues to grow and resource pressures evolve, similar debates will return. The next proposal may look different. The fundamental requirement of broad economic alignment is unlikely to change. Watching how that requirement is met, or not met, will remain one of the more revealing aspects of Bitcoin’s ongoing development.
