Adam Back, one of the most recognizable names in Bitcoin's technical history and chief executive of Blockstream, has turned his considerable rhetorical force against supporters of Bitcoin Improvement Proposal 110, publicly mocking the proposal's backers and delivering a blunt forecast: the associated Bitcoin fork will stall within three weeks of mandatory signaling. The intervention lands with weight — Back is not a peripheral commentator but a cryptographer whose Hashcash proof-of-work system was cited directly in Satoshi Nakamoto's original Bitcoin white paper. When he speaks on protocol matters, the development community listens, even when — especially when — he is being acerbic.
What BIP-110 Proposes and Why It Has Lit a Fuse
Bitcoin Improvement Proposals are the formal mechanism through which changes to the Bitcoin protocol are debated, refined, and either adopted or discarded. BIP-110, which has generated a sharp spike in controversy, involves a proposed fork that would require mandatory signaling from miners and nodes as a condition of activation. Mandatory signaling mechanisms have historically been among the most contentious features in Bitcoin upgrade debates — they force participants to declare a position, removing the ambiguity that softer activation paths permit and raising the political temperature considerably. The specifics of what BIP-110 would change at the protocol level remain the subject of heated technical discussion, but the mandatory signaling component alone has been enough to draw sharp opposition from influential corners of the ecosystem.
Back's Dismissal: Blunt, Personal, and Historical
Back did not confine himself to dry technical objections. His invocation of Satoshi Nakamoto — arguing implicitly that the original Bitcoin design already anticipated and resolved whatever problem BIP-110 purports to address — frames his opposition as a defense of foundational intent rather than mere conservatism. The phrase "Satoshi Was Not Retarded," crude as it is, carries a specific argumentative function: it suggests that the protocol's original architecture was deliberate and sophisticated, and that proposals which contradict its logic do not represent progress but regression dressed up as innovation.
This is a familiar move in Bitcoin discourse, and Back deploys it with the confidence of someone who was in direct email contact with Nakamoto during Bitcoin's earliest days. Whether one agrees with his conclusion or not, the rhetorical frame is effective — it shifts the burden of proof onto BIP-110's advocates to demonstrate not just that their change works technically, but that it improves on a design that its original author already thought through carefully.
The Three-Week Clock
The more operationally significant part of Back's statement is the timeline. By predicting that the fork stalls within three weeks of mandatory signaling beginning, he is making a falsifiable claim — not a vague expression of skepticism but a concrete forecast tied to a specific mechanism. This matters because it transforms the debate from a purely technical argument into something with a visible scoreboard. If the fork does stall within that window, Back's credibility on protocol matters is reinforced. If it proceeds past that point, proponents of BIP-110 have a data point to wield in return.
The prediction also implicitly tells us something about Back's read of current miner and node operator sentiment. A fork stalling under mandatory signaling typically means that a sufficient threshold of the network's hashrate or economic nodes have declined to signal support, effectively vetoing the change. For Back to make this call with apparent confidence suggests he believes — based on whatever visibility he has into mining pool coordination and node operator preferences — that BIP-110 lacks the broad coalition it needs to push through activation. Mining pools command enormous influence at this stage of any upgrade cycle, and if major pools are not aligned with BIP-110's proponents, the mandatory signaling mechanism becomes its own executioner.
The Deeper Pattern in Bitcoin Governance
BIP-110's controversy fits a longer pattern in Bitcoin governance disputes. Since the block size wars of 2017 — which produced the Bitcoin Cash fork — the community has developed a deep institutional allergy to proposals that can be characterized as coercive or that appear to short-circuit the rough-consensus model Bitcoin developers have historically relied upon. Mandatory signaling proposals tend to activate precisely this allergy, regardless of their technical merits. Critics of Back's position would argue that his hostility reflects an incumbent's preference for the status quo over necessary evolution. His supporters would respond that Bitcoin's resistance to change is a feature, not a bug — and that proposals which cannot survive the gauntlet of community skepticism probably should not be touching a two-trillion-dollar monetary network.
What is clear is that Back's intervention has raised the public stakes of the debate. Dismissing BIP-110's backers with pointed mockery rather than measured disagreement is a deliberate choice. It signals that he views the proposal not as a good-faith technical experiment that simply needs more work, but as something more fundamentally misguided — an attempt to alter Bitcoin's architecture in ways he considers incompatible with what the protocol was designed to be.
What This Means for BIP-110's Prospects
Proposals that attract this level of opposition from credentialed long-term contributors face a steep climb. Back's prediction of a stall within three weeks of mandatory signaling will now function as a public benchmark. Proponents of BIP-110 need to demonstrate sufficient miner and economic node support to prove him wrong — and they need to do it on an accelerated, visible timeline. If the fork does stall as Back predicts, it will likely set back the broader category of changes BIP-110 represents, regardless of their technical validity. The Bitcoin development community has a long memory for proposals that overreached, and a failed mandatory-signaling fork tends to poison the well for successor proposals traveling similar territory.
Written by the editorial team — independent journalism powered by Bitcoin News.