The activation clock is still ticking. The outcome is already decided.

At the time of writing, BIP110Monitor.com shows just 2.63 percent miner support for BIP-110. The activation threshold is 55 percent. There are 948 blocks remaining in the current signalling period. Even if every one of those blocks were to arrive with a yes vote, total support would cap out at roughly 48 percent. That is mathematically below the threshold. BIP-110 is not going to activate in this cycle.

So the question from BeInCrypto’s headline — “BIP-110 Activation Frozen After Coldcard Exploit: Is the Soft Fork Dead?” — has a precise answer. It is dead for this cycle. It may be dead for much longer. The more important question is why. Why did a soft fork with a 55 percent activation threshold, a written Bitcoin Improvement Proposal, and a functioning implementation in Bitcoin Knots fail so badly?

The answer is not technical. It is architectural. BIP-110 was not killed by bad code. It was killed by a broken consensus architecture. The Coldcard exploit was the trigger, but the wound was pre-existing. The network had already decided, in its own dispersed and chaotic way, that this particular proposal did not merit the risk of activation.

I have spent the past five years working across Bitcoin, Layer 2 scaling, and on-chain data analysis. In 2017, while most of my peers were chasing ICO presales, I allocated 50 ETH to audit whitepapers for twelve early-stage projects. I rejected all but one. The one I accepted did not have the most elegant code. It had the most robust social consensus. That lesson has never left me: the architecture of trust is built, not inherited. BIP-110 was built on code, but it never built the surrounding trust architecture needed to survive a crisis.

This article draws on BeInCrypto’s reporting, BIP110Monitor.com’s real-time dashboard, Coinkite’s official disclosure, and public statements from Udi Wertheimer, Michael Saylor, and Adam Back. The goal is to explain not only what happened, but what BIP-110’s failure reveals about Bitcoin governance in the ETF era.

Context: What BIP-110 Actually Is

BIP-110 is a Bitcoin soft fork proposal. The name suggests a Bitcoin Improvement Proposal. The reality is narrower. It does not increase block size. It does not change the UTXO model. It does not introduce a new cryptography primitive. It does not create a new token. BIP-110 is a temporary limit on the amount of data that can be carried in a transaction.

That is the whole proposal. A transaction is a container. It carries inputs, outputs, amounts, and sometimes arbitrary metadata. BIP-110 would restrict how much arbitrary data that container may hold. The stated logic is simple: Bitcoin’s block space is scarce. Transactions that carry large amounts of non-financial data squeeze out transactions that carry financial value. Limiting data payloads protects the payment use case.

The technical positioning is important. BIP-110 is not a scaling solution. It is a resource management intervention. It is a policy experiment wrapped in a consensus rule. It is also controversial because it sits on the border between protocol maintenance and content policing. Who decides what data is too much data? Who decides which data matters? The BIP itself does not answer those questions. It simply says: no transaction may carry more than a specified amount of data.

The code for BIP-110 was written by Dathon Ohm. It is packaged with Bitcoin Knots, not Bitcoin Core. This is the first red flag. Bitcoin Core is the reference implementation that the vast majority of the network treats as the canonical source of truth. Bitcoin Knots is a smaller, more opinionated node implementation maintained by a separate group. A proposal that lives only on the periphery is already a minority rule. It may be supported by a small developer community, but it has not entered the mainstream software stack.

There is no public third-party audit of the BIP-110 rules. In a protocol like Bitcoin, where a single bug in a consensus rule can lead to a chain split, the absence of an audit is a serious omission. I have audited smart contracts, lending protocols, and staking mechanisms. I would not deploy a rule change of this kind without at least two independent reviews. The fact that BIP-110 reached a voting window without a published audit tells you how unprepared the governance process was.

The proposal also has a curious temporal structure. It is described as temporary. But in Bitcoin, temporary rules have a way of becoming permanent. The 1 MB block size limit was originally justified as a temporary anti-spam measure. It lasted for years. BIP-110’s temporary data cap would create a precedent for future caps. Once you accept that miners can vote to restrict data payloads, you accept that miners can vote to restrict anything.

That is why the objections to BIP-110 are not only about inscriptions or ordinals. They are about the precedent. A soft fork that quietly imposes a data limit today can become a soft fork that loudly imposes a content filter tomorrow.

The Coldcard Exploit: The Trigger That Was Not the Cause

Coinkite disclosed a vulnerability in its Coldcard hardware wallet. The disclosure immediately became a macro event. Bitcoin users began asking uncomfortable questions. If a hardware wallet vendor can be compromised, what else can be compromised? If the hardware layer is fragile, how much trust should we place in a new consensus rule?

The developers behind BIP-110 paused the activation process. That is the report. That is the news. A hardware wallet vulnerability stopped a soft fork.

But the Coldcard exploit has no direct causal relationship with the BIP-110 code. BIP-110 does not run on hardware wallets. It runs on nodes. It is a consensus rule. Coldcard is a signing device. The two objects live on different layers of the Bitcoin stack. A vulnerability in one does not, in any logical way, invalidate the other.

Yet the industry reacted as if the two were connected. Why? Because Bitcoin’s governance is not a logical process. It is a social process. The hardware wallet exploit created an atmosphere of doubt. In an atmosphere of doubt, every upgrade proposal is suspicious. Every technical change appears dangerous. BIP-110 already had weak support. The exploit gave hesitant node operators a reason to say no.

The deeper problem is timing. BIP-110 was already struggling to reach consensus. The vote was mathematically doomed before the Coldcard disclosure. The exploit simply gave the proposal a convenient coffin. This is a recurring pattern. Projects fail not when the code breaks, but when the surrounding narrative breaks. I saw this in the NFT market. I predicted the collapse of generic PFP projects in 2021 by analyzing on-chain holder behavior and community sentiment months before prices corrected. The pattern is the same here. The code was never the issue. The social consensus around the code was the issue.

Udi Wertheimer, a prominent Bitcoin ecosystem figure, publicly urged users to switch back to regular nodes. That is an emergency instruction. It is not a policy recommendation. It is a warning that nodes running BIP-110 will enforce a different set of rules at block 961,632, and that this divergence could become dangerous.

Adam Back, one of the most respected names in Bitcoin, criticized the 55 percent activation threshold. He argued that the threshold was too low. Historically, Bitcoin upgrades have required overwhelming support to avoid chain splits. SegWit took years. Taproot achieved broad consensus before activation. A 55 percent threshold invites a scenario where a narrow miner majority forces a rule on a large minority. That is not a recipe for social stability.

Michael Saylor has framed Bitcoin as a property rights network. His support for BIP-110, or at least for the idea of limiting data bloat, is consistent with his broader thesis: Bitcoin’s value lies in its scarcity, its immutability, and its monetary purity. If anyone can paste JPEG data on the chain for a few satoshis, the ledger becomes a storage layer for arbitrary content. Saylor’s argument is principled. It is also insufficient. No executive can manufacture consensus in a decentralized network.

Core Analysis: The Math Was Already Unforgiving

Let me be precise. The current signalling period has a limited number of blocks. At the time of the report, BIP-110 support was approximately 2.63 percent. The activation threshold is 55 percent. That means support was more than twenty times below the required level. Even if every remaining block voted yes, the maximum possible support was about 48 percent.

This is not a close race. This is not a proposal that lost by a few votes. BIP-110 was facing an arithmetic impossibility. The remaining blocks could not produce enough yes votes to cross the threshold. The vote was over before the last 948 blocks were mined.

This should send a signal. Miner signalling is a social ledger. It reflects mining pool economics, node operator sentiment, developer influence, and exchange pressure. A support level of 2.63 percent means that the proposal had almost no institutional backing from the miners who would have to enforce it. It was a proposal without a constituency.

Why did support collapse? Several factors converge.

First, BIP-110 is bundled with Bitcoin Knots, not Bitcoin Core. Most miners and node operators do not run Bitcoin Knots. They run Bitcoin Core. This means the feature was invisible to the majority of the network. A soft fork cannot activate if the majority of the economic nodes never load the code.

Second, the proposal was framed as a response to spam. But the definition of spam is contested. Miners who process high-fee inscriptions make money from those transactions. From a pure fee perspective, inscriptions are not spam. They are revenue. Asking miners to vote for a rule that reduces potential fee revenue is a hard sell. The incentive structure works against the proposal.

Third, the Coldcard exploit shifted the conversation. Instead of debating block space allocation, the community began debating hardware trust. A hardware wallet vulnerability is a supply chain story. It is a physical security story. It is not a consensus rule story. The conflation of these narratives created enough noise to bury any remaining support.

Fourth, the activation mechanism itself was flawed. The 55 percent threshold is low by historical standards. But the second phase of BIP-110 would create a dangerous enforcement condition. After block 961,632, nodes running BIP-110 would reject blocks that did not signal approval for the proposal. This is not a soft fork in the classic sense. It is a mandatory signalling requirement. If a miner produces a block without the BIP-110 marker, nodes enforcing BIP-110 would treat that block as invalid.

The risk is obvious. Imagine a world where 10 percent of miners continue running BIP-110 after block 961,632. They will see the canonical chain as invalid. They will produce their own blocks. Their blocks will follow the BIP-110 rules. If exchanges and wallets do not coordinate, Bitcoin experiences a chain split. The market price of the minority chain will be volatile. The price of the majority chain will also suffer. This is the nuclear scenario that institutional investors fear most.

I have built yield strategies across Compound and Aave. I managed a portfolio of more than two hundred thousand dollars in total value locked. The one thing I learned above all else is that liquidity fears governance risk more than it fears price volatility. A chain split is the ultimate governance risk. It creates two tokens, two histories, and two communities. BIP-110 did not have to generate a split. The possibility alone was enough to kill it.

The architecture of Bitcoin’s upgrade process is designed to prevent this exact scenario. The requirement for broad consensus is not a bug. It is a firewall. BIP-110 tried to bypass that firewall with a 55 percent threshold. It tried to make activation easier. In doing so, it made activation harder. The lower the threshold, the more resistance the proposal encounters from the rest of the ecosystem.

The Hidden Target: Inscriptions and the Battle Over Block Space

BIP-110 never names ordinal inscriptions. The proposal does not mention BRC-20 tokens. It does not mention JPEGs or audio files or text-based metadata. But the mechanism is unambiguous. A limit on transaction data payloads is a direct response to the wave of arbitrary content being written to the chain.

This is the elephant in the room. The Bitcoin block space is a finite resource. Every block contains 1 megabyte of base data and, since SegWit, up to about 4 million weight units. Historically, most of that space was used for financial transactions. In the past few years, a growing portion has been used for metadata, images, and experimental token standards. This is not inherently bad. Miners earn fees. Users express themselves. The protocol remains neutral.

But the neutrality is exactly what BIP-110 questioned. The proposal says, in effect, that some data is not worth the block space. It says the market should not decide. It says a consensus rule should decide. That is a profound philosophical shift.

Supporters of BIP-110 argue that Bitcoin is money, not a database. They point to rising fees. They argue that cheap, arbitrary data storage on Bitcoin crowds out legitimate financial activity. The ledger should be reserved for settlement. If users want to store data, they should use a different network. This is a coherent position.

Opponents of BIP-110 argue that permissionlessness means anyone can write anything to the chain as long as they pay the fee. They point out that a data cap is a form of content discrimination. The protocol does not care whether a transaction is buying a coffee or inscribing a poem. The protocol only cares about the cryptographic signature. Introducing a data cap politicizes the protocol. It invites miners and developers to become arbiters of use case.

I have published controversial work on the death of the PFP NFT market. I argued that the OpenSea royalty surrender killed the creator economy. The same pattern is visible here. When the market cannot monetise a narrative, the market abandons it. Inscriptions generated a wave of economic activity. Then the activity created congestion. Congestion created demand for a rule change. The rule change failed. But the underlying demand for block space did not disappear.

BIP-110 was a blunt instrument. It could have been designed to target specific types of data. It could have been tied to fee thresholds. It could have been introduced as a soft policy at the miner level. Instead, it was proposed as a consensus change with a low activation threshold, no audit trail, and no reference implementation in Bitcoin Core. It was, in short, a governance trap. And the ecosystem stepped back.

Contrarian Angle: The Real Loser Is Bitcoin’s Upgrade Muscle

Here is the contrarian read. The failure of BIP-110 is not a victory for decentralization. It is a symptom of governance paralysis.

Bitcoin has a long history of failed proposals. Some deserved to fail because they were technically flawed. Others failed because the ecosystem could not agree on a political framing. BIP-110 belongs to the second category. The code may have been imperfect, but no serious security researcher has claimed that the data limit mechanism itself was broken. The proposal died because the ecosystem became risk-averse at exactly the wrong moment.

Risk aversion is not wisdom. It is the absence of decision. A system that refuses to change is a system that has accepted its current form as permanent. That is a defensible position for Bitcoin. But it is a very different position from dynamic governance. If Bitcoin rejects every upgrade that provokes any controversy, then Bitcoin will never adapt to new market pressures.

The Coldcard exploit is a perfect example. The exploit is real. The disclosure was responsible. But the exploit has nothing to do with transaction data caps. The fact that it froze a soft fork indicates that the entire ecosystem is now a hostage to the news cycle. One headline can derail months of technical work. That is not resilience. That is fragility.

Read the ledger, not the pitch. The ledger says 2.63 percent support. The pitch says the soft fork was killed by a hardware wallet scandal. The truth is that BIP-110 was already underwater before the scandal broke. The ecosystem had no appetite for the upgrade. The exploit became the excuse, not the cause.

The deeper issue is the institutionalisation of Bitcoin. After the approval of spot Bitcoin ETFs, Bitcoin is no longer a niche asset for cypherpunks. It is a Wall Street asset. Institutional investors care about stability, regulatory clarity, and the absence of drama. A chain split is a nightmare for any asset manager. BIP-110’s low threshold and mandatory signalling design introduced the possibility of a split. That alone made it unacceptable to the institutional crowd.

The paradox is beautiful. Bitcoin was designed to be censorship-resistant and non-sovereign. But the institutional era has created a new form of governance veto. Institutions do not vote on Bitcoin Improvement Proposals. They vote with their order flow. If an upgrade threatens the narrative of Bitcoin as a stable store of value, institutions will push it aside. BIP-110 was pushed aside.

This is not inherently bad. Institutional capital creates stability. But it also creates conservatism. Bitcoin cannot be upgraded in a way that threatens the ETF narrative. It cannot be upgraded in a way that creates even a small chance of a split. It cannot be upgraded with anything less than a religious consensus.

Some would say that is the price of success. I say it is a structural transformation. The architecture of trust is built, not inherited. The trust in Bitcoin’s code used to be built through open debate. Now it is built through institutional risk committees. BIP-110 found itself in a world that no longer rewards protocol innovation. It rewards protocol stasis.

Is that a good thing? Time will tell. But the hypocrisy is visible. The same people who celebrate Bitcoin’s immutability are praising the fact that a proposal was frozen because a hardware wallet had a bug. Immutability and paralysis are not the same word.

Lessons from the ICO Era and the Bear Market

I began my career in 2017, during the ICO boom. I audited twelve whitepapers. I rejected all but one. The one I selected returned forty times my initial capital. The reason was not the technical whitepaper. It was the community. The successful project had developers who communicated honestly, a treasury that was not immediately siphoned, and a narrative that could survive bad news.

BIP-110 failed the bad news test. When the Coldcard exploit hit, there was no army of node operators ready to say, “Wait, this has nothing to do with the soft fork.” There was no coordinated communication campaign. There was only silence and fear. The proposal had no community shield.

The DeFi Summer taught me another lesson. In 2020, I built a yield farming strategy across Compound and Aave. I generated returns above three hundred percent APY for four months. I learned how quickly liquidity moves when a single parameter changes. The same physics applies to consensus. Support for a soft fork is liquidity. It can vanish in a block.

In the 2022 bear market, I liquidated non-core assets and deployed into Layer 2 infrastructure. I stress-tested protocols under high load. I learned to distinguish between temporary noise and permanent structural change. BIP-110 is temporary noise. The block space allocation debate is permanent structural change. The market will continue to mine inscriptions. Fees will continue to rise. The question of data limits will return, no matter how many soft forks fail.

The bear market also taught me to respect survival metrics. A protocol survives because it has a clear function, a committed user base, and a realistic revenue model. BIP-110 had none of these. It had a function, but the function was contested. It had no user base beyond a small group of developers. It had no revenue model because it was not a product. It was a policy. Policies need political parties. BIP-110 had none.

The Institutional Translation: What TradFi Sees in BIP-110

Since 2024, I have worked as a Web3 research partner. My job is to translate raw blockchain data into institutional language. I have written reports that connect ETF inflows to altcoin liquidity. I have fielded questions from asset managers who have never opened a Bitcoin Core client but ask very precise questions about governance risk.

What do those institutional investors see when they look at BIP-110? They see a proposal with a 55 percent activation threshold. They see a potential chain split. They see a hard fork debate that could create two conflicting Bitcoin assets. None of that is acceptable.

Institutional capital does not reward risk-taking at the protocol layer. It rewards predictability. The ETF era has made Bitcoin a macro asset. Macro assets do not change their consensus rules every few months. Macro assets do not create chain splits. Macro assets do not ask miners to vote on data caps.

This is why BIP-110’s failure was inevitable. It was not just a technical failure. It was an institutional failure. The proposal did not account for the new governance environment. In 2017, a vocal minority of miners could push a contested soft fork. In 2026, any contested soft fork is a sell order.

I am not saying this is good. I am saying this is the reality. The architecture of trust built by Bitcoin’s original community has been augmented by the architecture of risk management built by the traditional financial world. BIP-110 was a relic of an older, more experimental era. The market moved on.

What Would a Better BIP-110 Look Like?

If the next version of BIP-110 is ever proposed, it will need a different design. It will need to be bundled into Bitcoin Core from day one. It will need at least two independent security audits. It will need a threshold closer to 90 percent than 55 percent. It will need a clear, non-censorious framing. It will need an opt-out path for nodes and miners.

The activation mechanism should also be redesigned. A mandatory signalling rule is dangerous. It invites chain split risk. A better approach would be a relay policy, not a consensus rule. Miners and node operators can choose to discard large data payloads without changing the consensus rules. This is already happening at the mempool level. Many miners have imposed their own transaction size limits or fee rules. The market is capable of solving the problem without a soft fork.

The next battle will not be a soft fork. It will be a war over mempool policy. Each miner will decide what to include in their blocks. Each node will decide which mempool rules to enforce. This is messy, but it is safe. It does not require a global threshold. It does not create a chain split. It simply creates a patchwork of policies.

The failure of BIP-110 may actually be good for Bitcoin in the long run. It teaches the ecosystem that consensus changes require more than code. They require a broad coalition. They require institutional alignment. They require the architecture of trust to be constructed before the activation clock starts ticking.

The Role of Code, Hype, and Liquidity

Code is law. Hype is temporary. The BIP-110 code still exists. The hype around it has died. The law was never activated. But the block space is still finite. The inscription debate is still unresolved. The mining fee structure is still evolving. Hype may be temporary, but the underlying liquidity of Bitcoin’s block space is permanent.

Narratives shift. Liquidity stays. In 2021, everyone believed PFP NFTs would create a new creator economy. The OpenSea royalty surrender and the collapse of speculative JPEG trading ended that narrative. In 2024, everyone believed every project needed an AI agent. That narrative also shifted. BIP-110 belongs to a specific moment in Bitcoin’s governance history. The moment passed.

But the liquidity of attention in the Bitcoin ecosystem is always seeking the next conflict. The next conflict will be about fees. It will be about whether large data transactions should be allowed. It will be about who controls the mempool. BIP-110 asked the question too early, with too little support, and in the middle of a hardware wallet scandal. The question was correct. The timing was wrong.

The Clock at Block 961,632

Block 961,632 is not the end of the world. It is a technical marker. If enough nodes run BIP-110, that block will trigger a new set of validity rules. If not, the proposal simply dies. Right now, the evidence says the proposal is dying. There are not enough nodes. There are not enough miners. There is not enough consensus.

The danger is not that BIP-110 fails to activate. The danger is that a small group keeps running the code anyway. That group would produce a chain that rejects blocks without the signalling mark. The rest of the network would ignore this chain. But exchanges might be forced to list both chains. That is the worst possible outcome.

This is why Udi Wertheimer’s call to switch back to regular nodes was so important. It was a firewall. It was an attempt to ensure that no minority chain exists. It was a reminder that running an unactivated soft fork is not a neutral act. It is a political act.

I have seen this movie before. In the NFT market, I warned that generic PFP projects would collapse months before the market corrected. The mechanism was identical. A narrative had peaked. The on-chain data showed declining holder growth. The community was still loud, but the liquidity was already leaving. BIP-110 has the same shape. The community may be loud, but the miner support is 2.63 percent.

Summary of the Technical Assessment

Let me be clear about the technical takeaway. BIP-110 is not a scaling innovation. It is a rule experiment. It changes the maximum data payload per transaction. It does not increase throughput. It does not reduce fees. It does not change Bitcoin’s monetary policy. It is a content filter with a consensus wrapper.

The security assumptions are concerning. The proposal depends on miners and nodes reaching a fragile social consensus. The 55 percent threshold is too low. The enforcement mechanism creates a chain split risk. The implementation is not audited publicly. The integration is not part of Bitcoin Core. The developer ecosystem has not rallied around it.

This is not a recipe for success. It is a recipe for exactly what happened. The proposal failed to gain traction. The Coldcard exploit provided a final push. The community moved on.

But do not confuse a specific failure with a dead principle. The principle that block space is scarce is not dead. The principle that arbitrary data should not degrade financial use is not dead. The principle that the market should decide what belongs on the chain is not dead. BIP-110 was one answer to a question that will not disappear.

The next attempt will need to be smarter. It will need to start with a public audit. It will need to be included in Bitcoin Core. It will need to be discussed at Bitcoin Core developer meetings, not on Twitter. It will need to be supported by mining pools with a written commitment. It will need to survive a hardware wallet scandal, a policy panic, and a media backlash. If it cannot survive those things before activation, it will certainly not survive them after activation.

The Institutional Bridge and the Role of Research

As a research partner, I believe the role of analysts is to separate signal from noise. BIP-110 produced a lot of noise. The Coldcard exploit was noise. The speculation about chain splits was noise. The signal is simpler: Bitcoin’s governance is now constrained by institutional risk appetite.

This is neither good nor bad. It is a structural fact. Anyone who writes about Bitcoin must understand it. Anyone who proposes a soft fork must understand it. The old days of contentious upgrades are not necessarily over, but they are much harder.

I have produced detailed reports for traditional finance clients. They do not ask about the elegance of a BIP. They ask about the probability of a split. They ask about the behavior of exchanges. They ask about the response of custodians. They ask about the tax implications. BIP-110 fails every one of those institutional tests.

This is why I say the architecture of trust is built, not inherited. Bitcoin’s early trust was built by cryptographic proofs and open-source transparency. The new trust is built by custodians, ETFs, and regulatory clarity. BIP-110 did not fit into the new trust architecture. It belonged to an older, more chaotic world.

The Reality of the Vote

Numbers matter. The vote is the only objective measure of consensus. The vote says 2.63 percent support. The vote says 55 percent required. The vote says maximum possible support is 48 percent. The conclusion is inescapable.

Do not listen to the loudest voices. Listen to the ledger. Read the ledger, not the pitch. The ledger is a history of transactions. It is also a history of decisions. Every missing signalling bit is a no vote. Every empty block is a no vote. Every block produced by a pool that has not deployed the BIP-110 rules is a no vote. The ledger is clear.

Some will argue that miner signalling is not the same as node operator support. That is true. But node operator support is not measurable in the same way. The BIP-110 monitor does not track node count. If it did, the story would not be much better. Bitcoin Knots is a niche implementation. The number of nodes running it is small. The number of nodes with BIP-110 enabled is smaller.

In a decentralized network, consensus is not a single event. It is a distributed reality. BIP-110 lacked distributed reality. It existed in code. It existed in a few repositories. It existed in a handful of conversations. That is not enough.

What Should Holders Do Now?

The practical answer is simple. Holders should do nothing. BIP-110 will not activate. The chain will continue producing blocks. The price of Bitcoin will continue to be set by macro factors, ETF flows, and liquidity conditions. The soft fork is irrelevant to the market.

Node operators should check their software. If you are running Bitcoin Knots with BIP-110 rules enabled, switch back to Bitcoin Core or disable the BIP-110 rules. This is not an admission of defeat. It is a risk management decision. You do not want to be on a minority chain.

Miners should ignore the proposal. There is no reason to signal support. The threshold is unreachable. Any signalling now would only create confusion. Let the proposal die quietly.

Developers should study the failure. The BIP-110 process offers a treasure trove of lessons. It teaches you how not to build consensus. It teaches you the importance of audits. It teaches you the danger of low thresholds. It teaches you that external events can kill a technically sound proposal.

The Future of BIP-110 and Similar Proposals

Will BIP-110 be resurrected? Perhaps. But a resurrected BIP-110 would need to be a different animal. It would need to be a Bitcoin Core proposal. It would need to be discussed for a year before activation. It would need to have a security audit. It would need to have the support of major mining pools. It would need to survive a period of bad news. If it cannot survive bad news, it does not deserve activation.

The more likely path is not a soft fork. It is a market-based solution. Miners can set their own transaction policies. Nodes can enforce their own mempool limits. Wallets can stop processing large inscription transactions. This is already happening. The market is slowly adapting to the reality of data-heavy transactions.

The problem with BIP-110 was not the goal. The problem was the method. A soft fork is the heaviest tool in Bitcoin’s governance toolbox. You do not use a sledgehammer to kill a fly. BIP-110 used a sledgehammer. The fly escaped.

The Hidden Centralization Risk

There is another issue that is rarely discussed. The 55 percent threshold may be too low, but the concrete manifestation of miner voting is deeply centralized. A small number of mining pools control the majority of hashrate. If a few pool operators decided to support BIP-110, the threshold could be crossed quickly.

This is not a theoretical risk. In the current mining landscape, the top five pools control a significant share of Bitcoin’s hashrate. A coordinated decision by those pools could create a sudden wave of signalling. The BIP-110 monitor would show a spike. The narrative would change overnight.

But the vote did not spike. It remained at 2.63 percent. This tells you that the mining pools do not want the proposal. They do not want the political risk. They do not want to be seen as censors. They do not want to create a chain split. They would rather stay neutral.

This is a sign of maturity. It also means that Bitcoin’s governance has moved from miner dominance to multi-stakeholder negotiation. Miners are not kings. They are participants. They cannot force an upgrade. They can only signal. The failure of BIP-110 is proof that miner signalling alone is not enough.

The Emotional Tone of the Market

The market is in a sideways consolidation. There is no euphoria. There is no panic. There is only waiting. In this environment, any controversial proposal faces an uphill battle. BIP-110 encountered the quiet, skeptical mood of a market that has been burned by many narratives.

Sideways markets are not bullish or bearish. They are neutral. Neutrality is the enemy of protocol change. People do not take risks when they are waiting for direction. They avoid risk. They stick with the status quo. BIP-110 was a risk. The status quo won.

I have seen this behavior in DeFi. When yields are flat, farmers move their capital to safer pools. When Bitcoin is sideways, governance voters move to safer positions. They vote no by default. BIP-110 needed a strong reason to overcome the default. It did not have one.

The Coldcard exploit was the final confirmation. If a hardware wallet maker can be compromised, why should a node operator trust a random BIP? The question is unfair, but it is human. Trust is not mathematical. Trust is social. The Coldcard exploit depleted a small but essential reserve of social trust.

The BeInCrypto Question: Is the Soft Fork Dead?

Let me answer the question directly. The soft fork is dead for this activation window. The clock is still running, but the math makes the outcome certain. Even if every remaining block votes yes, support will not reach 55 percent. That is the definition of dead.

But dead is not permanent. Bitcoin Improvement Proposals can be revised. Code can be refactored. New activation cycles can start. The underlying issue of data limits will return. The BIP-110 name may return, or it may be replaced by a better proposal.

The question is not whether BIP-110 is dead. The question is whether Bitcoin can still upgrade. If the only way to change Bitcoin is through Bitcoin Core, and Bitcoin Core is reluctant to include controversial proposals, then Bitcoin’s future upgrades will be rare. That is not necessarily bad. Bitcoin’s value proposition is stability. But stability can become stagnation.

The Coldcard exploit was a wake-up call. It showed how fragile the Bitcoin governance process has become. It showed that a single hardware wallet vulnerability can derail a protocol change. It showed that the architecture of trust is built, not inherited. We are all assembling this architecture one block at a time.

A Personal Note from the Field

I wrote my first institutional report on Bitcoin in 2020. I created dashboards that tracked yield, TVL, and miner flows. I learned that the market is a story machine. Every price change is a story. Every upgrade is a story. Every exploit is a story. The analyst’s job is to find the story that survives contact with data.

BIP-110’s story did not survive contact with data. The data said 2.63 percent. The data said no audit. The data said no Bitcoin Core integration. The data said no institutional support. The story was built on hope. Hope is not a consensus mechanism.

In 2017, I allocated capital based on audits, not hype. That discipline gave me a forty fold return. The same discipline keeps me from believing that BIP-110 could have succeeded. The signals were all negative from the beginning.

This is not a triumph of skepticism. It is simply a recognition of reality. The ledger knows. The ledger always knows.

The Bigger Picture

Bitcoin is at a strange moment. It is both a subculture and a global asset. It is both decentralized and institutional. It is both immutable and always changing. BIP-110 was caught between these poles. It could not satisfy the subculture because it felt censorship-adjacent. It could not satisfy the institutions because it carried chain split risk.

The proposal was a compromise that pleased no one. Supporters saw a weak attempt to fix a real problem. Opponents saw an intrusive attempt to control content. Institutions saw an unpredictable governance event. Miners saw a threat to fee revenue. No coalition formed.

This is the true lesson of BIP-110. A soft fork is not a technical product. It is a political coalition. BIP-110 failed to build that coalition. It was built in code, but not in minds. It was built in a repository, but not in market structure. It was built in a draft, but not in trust.

The architecture of trust is built, not inherited. BIP-110 tried to inherit Bitcoin’s existing trust. It offered no new trust. It offered only rules. Rules without trust are not consensus. They are commands. Bitcoin does not respond to commands. It responds to incentives.

The Mempool Will Outlive the BIP

The most important place to watch is the mempool. Not the BIP. Not the monitor. Not the Twitter threads. The mempool is the real battlefield. It shows what miners are willing to include. It shows fee pressure. It shows the actual demand for block space.

If large data transactions continue to pay high fees, miners will include them. The block space market will solve the data problem. If the market decides that inscriptions are wasteful, fees will fall and the problem will solve itself. The mempool is a more democratic governance mechanism than any soft fork vote.

BIP-110 was an attempt to bypass the mempool. It wanted to impose a rule before the market had reached a conclusion. That is why it failed. The market does not accept preemption. The market accepts trial and error. BIP-110 skipped the trial and went straight to the verdict.

The future of data limits lies in miner policies, node policies, and wallet defaults. Each actor will choose their own tolerance for data-heavy transactions. The result will be a patchwork. It will be messy. But it will not require a 55 percent threshold. It will not risk a chain split. It will not be frozen by a Coldcard exploit.

Final Thought

The last blocks of this signalling cycle will be mined. The BIP-110 vote will expire. The monitor will update. The proposal will be archived. The Coldcard exploit will fade from memory. The question of what belongs on Bitcoin’s block space will remain.

Do not look for the next BIP. Look at the mempool. Look at mining pool fee policies. Look at exchange listing decisions. Look at the behavior of large holders. The next battle over Bitcoin’s data will not be fought inside a soft fork. It will be fought in the everyday decisions of miners and users.

BIP-110 is dead. Long live the question. The architecture of trust is built, not inherited. We have just watched a brick fall. The wall still stands.