F2Pool, one of the world’s largest Bitcoin mining pools, has acknowledged that it was filtering transactions associated with addresses flagged by the U.S. Office of Foreign Assets Control (OFAC). The admission came after Bitcoin developer 0xB10C published an analysis suggesting that several sanctioned transactions were being systematically excluded by the pool. After initially defending the practice, F2Pool co-founder Chun Wang later said the pool would disable the transaction-filtering patch for now, citing the need for broader community consensus.
Research Sparked the Controversy
The issue surfaced after 0xB10C examined a set of transactions linked to OFAC-flagged Bitcoin addresses and compared how different miners and pools handled them. According to the findings, six transactions were reviewed in total. Of those, four transactions that did not appear in blocks mined by F2Pool were considered likely to have been deliberately filtered, while the remaining two may have been excluded for other reasons. Based on that pattern, the developer concluded that F2Pool was actively applying a filter to sanctioned transactions.
The findings quickly circulated across the Bitcoin community, where transaction neutrality and censorship resistance remain foundational values. Because mining pools play a major role in transaction selection, even isolated examples of filtering can trigger broader concerns about whether compliance pressures might influence block construction on the network.
F2Pool Confirmed It Was Applying a Compliance Filter
Following the publication of the analysis, Chun Wang publicly confirmed that F2Pool had implemented a compliance filter for OFAC-linked transactions. In a post on X that was later deleted, Wang defended the decision in forceful terms, arguing that he had the right to refuse to confirm transactions tied, in his view, to criminals, dictators, and terrorists.
His remarks went beyond a simple compliance explanation. Wang also argued that if a system is meant to be censorship-resistant, that property should come from protocol design rather than from expecting each participant in the system to voluntarily avoid censorship. In that framing, responsibility lies with Bitcoin’s architecture itself, not with individual operators acting against their own legal, ethical, or business judgments.
That argument, however, did little to calm critics. Instead, it sharpened a long-running debate inside Bitcoin over where responsibility for neutrality should sit: at the protocol layer, at the miner level, or across the broader ecosystem of pools, node operators, and users.
Community Pushback Was Immediate
The response from the Bitcoin community was swift and negative. Critics argued that a mining pool operator does not own all of the hashrate connected to the pool and therefore should not unilaterally impose personal or political preferences on miners contributing computing power. For many observers, the central issue was not only OFAC compliance itself, but whether a large pool should decide which valid Bitcoin transactions deserve confirmation.
The backlash reflected a broader concern about mining pool concentration. When a major pool filters even a small category of transactions, the immediate effect may be limited, but the precedent can be significant. Community members worried that selective filtering by large pools could normalize a model in which external sanctions lists or political judgments begin to shape transaction inclusion more directly.
Bitcoin’s value proposition has long been tied to the idea that valid transactions, once broadcast and properly fee-bumped, should compete on market terms rather than ideological ones. Any sign that miners or pools are applying non-economic filters tends to reignite fears that neutral blockspace could erode over time.
F2Pool Later Walked Back the Policy
After criticism intensified, Wang reversed course. In another post that was also later deleted, he said F2Pool would “disable the tx filtering patch for now” until the community reached a more comprehensive consensus on the topic. That statement marked a clear retreat from the pool’s earlier position and suggested that the scale of the backlash had become impossible to ignore.
Although the pool’s announcement appeared to settle the immediate controversy, it left several larger questions unanswered. The first is whether similar filtering practices may exist elsewhere in the mining ecosystem, either formally or informally. The second is how Bitcoin participants should respond when regulatory expectations collide with the network’s longstanding anti-censorship ethos.
A Familiar Tension in Bitcoin: Compliance Versus Neutrality
The F2Pool episode highlights a recurring tension in Bitcoin infrastructure: the conflict between regulatory compliance and the principle of permissionless transaction processing. Pools, exchanges, custodians, and other major service providers often operate in jurisdictions where sanctions compliance can carry legal and reputational consequences. At the same time, Bitcoin users expect the network’s transaction pipeline to remain credibly neutral.
That tension becomes especially visible in mining because miners and pools directly influence which transactions enter blocks. While Bitcoin’s protocol itself does not distinguish between politically acceptable and unacceptable transactions, the actors building blocks can still exercise discretion. In practice, that makes mining pools an important pressure point whenever sanctions and censorship concerns converge.
Wang’s comments also touched on an important philosophical divide. One side argues that robust systems should be designed to withstand censorship without relying on the goodwill of operators. The other argues that while protocol design matters, large infrastructure participants still have a responsibility not to undermine neutrality through discretionary filtering. The controversy around F2Pool showed how far apart those views can be in real-world operational settings.
Why the Story Matters
Even though F2Pool has said it will stop filtering these transactions for now, the incident carries significance well beyond a single mining pool. It demonstrates how independent technical analysis by developers can surface behavior that would otherwise remain opaque. It also shows that community pressure can still influence major industry players when Bitcoin’s core norms are perceived to be at risk.
More broadly, the episode serves as a reminder that censorship resistance is not a static attribute guaranteed in all circumstances. It is shaped by protocol rules, economic incentives, infrastructure concentration, and the behavior of influential intermediaries. As Bitcoin continues to mature and interact with traditional regulatory systems, conflicts like this are likely to reappear.
For now, F2Pool’s decision to suspend the filter may ease immediate concerns. But the underlying debate remains unresolved: if Bitcoin is to remain neutral and permissionless, how much discretion should major mining pools have over transaction selection, and what happens when that discretion is exercised in the name of compliance?