The silence around BIP 110 is louder than any code change. In a rare display of unity, two of Bitcoin’s most recognizable figures—Michael Saylor, the corporate colossus who holds over 200,000 BTC, and Adam Back, the cryptographic architect behind Hashcash—have publicly condemned a proposal whose technical details remain shrouded. Saylor called it a “dangerous precedent.” Back, typically measured, offered no technical rebuttal, only a terse opposition. The market barely flinched. Yet for those who watch the macro currents, this is not a quiet storm—it is a structural tremor beneath the surface of the world’s most resilient asset.
The context is the Bitcoin Improvement Proposal system, a decentralized governance mechanism that has produced both profound upgrades (SegWit, Taproot) and bitter schisms (the 2017 block size war). BIPs are meant to be transparent, debated publicly on mailing lists and GitHub. But BIP 110 exists in a fog. Neither the full specification nor the author’s identity have been widely circulated in mainstream crypto media. What we know comes from a single article snippet: two prominent figures oppose it, and it is deemed “highly controversial.” That is the entire dataset.
From a structuralist perspective, the absence of detail is itself a critical data point. In my thirteen years of analyzing protocol changes—from the ICO mania of 2017, where 85% of whitepapers were Ponzi models, to the DeFi summer of 2020, where yield farming promised returns that mathematics could not sustain—I have learned that when powerful actors oppose without specifying the threat, the threat is often more philosophical than technical. The opposition is not to a specific bug or vulnerability, but to a shift in the protocol’s unwritten constitution.
What could BIP 110 be? Based on the profile of the opponents, we can triangulate. Saylor’s entire thesis is “digital gold”—a fixed-supply, proof-of-work asset with no room for monetary expansion. Any proposal that alters the 21 million supply cap, changes the halving schedule, or introduces a mechanism for inflation would violate that thesis. Back, on the other hand, champions sidechains and the Liquid Network—scaling solutions that preserve Bitcoin’s main chain as a settlement layer. He would oppose any proposal that expands Bitcoin’s base layer functionality, such as adding covenants or enabling complex smart contracts, because it would conflict with his vision of layered scalability.
Two plausible scenarios emerge:
Scenario A – Monetary Modification: BIP 110 proposes a dynamic supply adjustment, perhaps to fund development or address long-term security assumptions. This would directly attack Bitcoin’s immutability narrative. Saylor’s “precedent” comment fits: once supply becomes adjustable, the door opens to future changes, fracturing the asset’s credibility as a store of value. Back would oppose on similar grounds—Bitcoin’s strength is its predictable issuance, and any tampering threatens the entire Litecoin-to-Bitcoin hierarchy of trust.
Scenario B – Base-Layer Expansion: BIP 110 introduces new opcodes or covenant structures that enhance Bitcoin’s scripting capabilities. This could enable complex financial primitives directly on the main chain, bypassing sidechains. Back, who has invested heavily in Liquid, would see this as a competitive threat. Saylor might support it in theory but oppose the governance precedent—rushing such a change without overwhelming consensus could lead to a fork, endangering the institutional adoption he has championed.
Both scenarios are speculative. The deliberate opacity from the original article only amplifies the narrative’s fragility. But in a bear market, when liquidity evaporates and every risk vector is magnified, speculation becomes a liability.
Let’s examine the governance mechanics. Bitcoin does not have a formal voting system. BIP activation relies on miner signaling and node software adoption. The opposition of two whales—Saylor as a corporate holder, Back as a core developer emeritus—carries weight, but it is not decisive. In 2017, the New York Agreement (SegWit2x) was supported by major exchanges and mining pools, yet it failed due to grassroots rejection. The difference here is the lack of any visible grassroots support. The BIP 110 author has not stepped forward to defend the proposal. The absence of a champion makes it likely that the BIP will be abandoned or revised into irrelevance.
But the deeper risk is not the proposal itself, but the precedent of how it was handled. A controversial BIP emerged, was quickly condemned by elites, and the details were withheld from the public. This is not how decentralized governance is supposed to work. It smells like centralized gatekeeping, where a few voices can smother debate before it begins. If Bitcoin’s development process becomes a closed circle of trusted insiders, the very thing that makes it resilient—permissionless innovation—erodes.
Contrarian angle: Perhaps the opposition is an overreaction. The “dangerous precedent” might be procedural, not technical. Perhaps BIP 110 proposed a new activation mechanism that bypasses the traditional rough consensus process. In that case, Saylor and Back are defending the governance status quo, not Bitcoin’s monetary policy. This is actually a healthy signal: the guardians are protecting the process, not just the asset. But if that is the case, why not say so? Why let speculation fester? The lack of transparency suggests there may be more at stake than they want the market to debate.
From a market perspective, the impact is muted. Bitcoin’s price has not reacted—yet. Volatility remains low, and funding rates are neutral. This indicates that the broader market has not priced in any scenario of protocol change. The market is treating this as noise, but noise in a quiet bear market can become signal. If more details leak, or if another prominent developer (e.g., Luke Dashjr) voices opposition, the narrative could shift from “minor governance squabble” to “existential threat.” For now, the risk premium is near zero, which itself is a contrarian signal—no one is hedging against a possible fork.
Institutional capital, which entered post-ETF approval, is especially sensitive to governance uncertainty. A proposal that splits the community could trigger a wave of hedging or even selling by risk-averse allocators. Saylor himself, as MicroStrategy’s chairman, would be the first to suffer. His public opposition is both a defense of his thesis and a protection of his balance sheet.
Beyond the illusion, the current never truly stops. The BIP 110 controversy, however opaque, reveals the underlying current of Bitcoin governance: it is human, messy, and vulnerable to concentration of influence. The technology remains sound, but the process around it is fragile. DeFi’s glass house shattered under its own weight in 2022; Bitcoin’s fortress of code has so far withstood every attack. Yet this governance dispute is not an attack from outside—it is a crack from within, a quiet stress test of the social layer that or us".
In the quiet aftermath, only the resilient remain. Bitcoin’s resilience has been tested by forks, bans, and crashes. This episode will likely pass without a scar. But for the macro watcher, the lesson is clear: liquidity is a ghost, but the debt is real. The debt is the trust we place in a process that operates in the shadows of a few key individuals. As long as that debt is serviced—by transparency, by open debate, by the willingness to let bad proposals die in public—Bitcoin will endure. The moment that trust is broken, the illusion of decentralization collapses, and the current stops.
The takeaway for investors is not to trade this news, but to monitor the process. If the BIP 110 author surfaces with a clear, technically sound proposal, and the opposition fails to provide substantive counterarguments, then the narrative flips: the guardians become gatekeepers, and the market should price in a governance risk premium. If the BIP is withdrawn in silence, the system validated itself. Either way, the truth will emerge only when the details do. Until then, hold the glass—but watch the cracks.