A 12-Year-Old Bitcoin Dispute Returns as BIP-110 Divides the Community
A decade-old dispute over Bitcoin address blacklisting has resurfaced as developer Luke Dashjr backs BIP-110, a controversial proposal to ban image and text data from the blockchain, prompting institutional investors to reassess governance risk and the legitimacy of technical leadership in Bitcoin’s decentralized protocol. The clash between security concerns and protocol neutrality now threatens to fracture consensus on the network, raising questions about which version of Bitcoin would be recognized by institutional derivatives markets if a fork occurred.
- David Bailey publicly attacked Luke Dashjr over a 2014 blacklisting incident, arguing it disqualifies him from maintaining Bitcoin software.
- BIP-110 needs 55% miner support to activate but has commanded less than 0.79% backing since December 2025, far below Bitcoin’s historical 95% threshold.
- If activated, BIP-110 would reject blocks that fail to signal support starting early August, echoing the contentious 2017 SegWit fork dispute.
- ~20% Network node share running Bitcoin Knots during 2025 spam debate.
- 0.79% Peak miner signaling for BIP-110 since December 2025 activation period began.
- 55% Miner threshold required for BIP-110 activation versus historical 95% consensus bar.
A 12-year-old controversy over censorship in Bitcoin’s code has become central to a current governance battle, raising fresh questions about developer authority and protocol legitimacy at a time when institutional capital is watching closely.
On July 10, Nakamoto CEO David Bailey resurfaced a 2014 incident in which Luke Dashjr, a respected Bitcoin Core developer, had secretly embedded address blacklists into a version of Bitcoin software distributed through Gentoo Linux.
The blacklist blocked transactions to gambling services including SatoshiDice and shipped as the default setting, silently censoring payments until node operators discovered the change and publicly objected.
Bailey’s timing was deliberate: Dashjr is now the primary advocate for BIP-110, a proposed protocol rule that would ban the storage of images, text, and other non-monetary data on the Bitcoin blockchain for one year. The revival of the blacklisting dispute signals deepening anxiety among influential figures about whether Dashjr should hold central influence over Bitcoin’s technical direction.
Dashjr’s 2014 Blacklist and the Governance Question It Poses
The 2014 incident centered on Dashjr’s view that gambling transactions posed a moral hazard to Bitcoin adoption. Acting unilaterally, he modified the Gentoo Linux package of Bitcoin Core to automatically reject addresses tied to SatoshiDice and other gambling platforms.
The patch shipped with blacklisting enabled by default, meaning users who compiled Bitcoin software from that repository had their nodes silently filtering transactions without their knowledge or explicit consent.
When the censorship was discovered, the reaction was swift. Bitcoin community members filled forums and social media with criticism, arguing that embedding moral judgments into the protocol’s default behavior violated Bitcoin’s foundational principle of neutrality.
A fellow Bitcoin Core developer pointed out that such contentious changes should ship in separately named software versions, not in the default build. Dashjr subsequently reversed the default, made the blacklist optional, and apologized publicly. Bitcoin Core itself never shipped the feature.
Supporters of Dashjr stress this context: the change was reversed before it caused lasting harm, it was made optional, and the apology was genuine.
Yet the incident remains a live reference point in debates over who should steer Bitcoin’s protocol.
BIP-110 Reignites Questions About Data Neutrality and Miner Consensus
BIP-110 proposes a one-year embargo on inscriptions, data embedded into Bitcoin transactions by users deploying protocols like Ordinals. Dashjr frames this category of data as spam that bloats the blockchain and undermines Bitcoin’s utility as money. He runs Bitcoin Knots, an alternative implementation of Bitcoin software that already enforces these restrictions.
During 2025’s heavy period of inscription activity, Bitcoin Knots powered approximately 20% of the network’s public nodes, giving Dashjr’s software meaningful reach across the network.
To activate BIP-110, Dashjr and his supporters need 55% of miners to signal support for the rule change, a notably lower bar than Bitcoin’s historical standard of 95% consensus, which was required for past upgrades like SegWit. Since the signaling period began in December 2025, miner backing has never exceeded 0.79%, leaving support far short of the 55% threshold.
Despite this minimal miner endorsement, nodes running BIP-110-compliant software plan to begin rejecting blocks that fail to signal support for the rule starting in early August. This enforcement mechanism echoes the 2017 SegWit upgrade, when users forced a protocol change by threatening to reject non-compliant blocks.
The parallel to SegWit carries significant weight in institutional circles. SegWit arrived with broad backing across miners, developers, and users, and faced genuine technical objections rather than mere preference disputes. BIP-110 has neither advantage.
Prominent figures openly oppose it: MicroStrategy’s Michael Saylor called the proposal a self-inflicted protocol risk, and Blockstream’s Adam Back warned that enforcing the rule could trigger a fork that splits Bitcoin into two incompatible chains, stranding supporters of the losing fork on worthless software.
The CME Futures Question That Could Define Which Bitcoin Survives a Fork
For institutional investors holding or trading Bitcoin through regulated derivatives markets, the most critical question may be how the CME Group’s cash-settled Bitcoin futures contract would treat a network fork. David Bailey raised this issue explicitly, noting that Wall Street participants may not fully grasp how Bitcoin governance actually functions when consensus breaks down.
If BIP-110 enforcement causes the network to split into two competing chains, one that rejects inscriptions and one that accepts them, which version would the CME settle its contracts against?
This question has profound implications for institutional participants. CME Bitcoin futures are cash-settled against the spot price reported by the CME CF Bitcoin Reference Rate, which aggregates prices from major trading venues.
In a fork scenario, those venues would need to decide which chain they treat as “Bitcoin.” The fork that retains the most mining power, user adoption, and exchange liquidity would likely be designated as the reference version.
BIP-110’s current 0.79% miner support suggests that if activated, the majority of mining power would continue on the non-BIP-110 chain, potentially making that chain the one recognized by institutions and derivatives venues.
Bailey has publicly stated that the Wall Street community “has no idea how Bitcoin governance works” when consensus fractures, amplifying concern among institutional investors about the operational and financial risks of a contested fork.
Why the 12-Year-Old Dispute Matters Now for Institutional Legitimacy
The timing of Bailey’s critique is strategically significant. By linking Dashjr’s current role as BIP-110’s champion to his 2014 censorship decision, Bailey is arguing that Dashjr’s judgment cannot be trusted to unilaterally reshape the protocol.
This framing targets not just the technical merits of BIP-110, but the authority and process by which protocol changes should occur in a decentralized network.
For institutional investors, the resurfaced blacklisting incident highlights a governance fault line in Bitcoin: the tension between technical expertise and democratic legitimacy. Dashjr is widely respected as a brilliant developer, but the 2014 incident demonstrates he is willing to embed his personal values into the protocol’s default behavior.
That willingness, combined with BIP-110’s current lack of miner consensus, suggests that activation would depend on enforcement by nodes rather than broad agreement. In institutional markets, such scenarios trigger warnings about protocol fork risk and custody complications.
The contrast with SegWit underscores the stakes. SegWit arrived with genuine technical benefits, broad stakeholder backing, and high miner signaling thresholds. BIP-110 has experienced minimal miner support, faces credible technical objections from prominent figures, and would require node-level enforcement to activate against miner indifference. Bailey’s excavation of the 2014 dispute serves to reinforce the narrative that BIP-110 represents
