F2Pool co-founder opposed Bitcoin’s BIP-110 and BIP-54 drafts

On April 4, 2026, F2Pool co-founder Chun Wang publicly opposed two draft Bitcoin soft-fork proposals, BIP-110 and BIP-54, arguing that protocol changes should not be advanced like an omnibus bill that carries provisions participants would not support separately. Contemporaneous reports attributed the comments to Wang’s X account. The surviving reports do not establish that F2Pool adopted a formal pool policy or changed the blocks it mined.

The objection mattered because it put a prominent mining figure on record against two different forms of consensus intervention at the same time: temporary restrictions on how transaction data could be used, and a package of repairs for long-standing consensus weaknesses. Bitcoin had no company or foundation able to order either change into force. Any soft fork would depend on software, node, miner and market coordination, so visible disagreement was itself material even though it was not a vote or veto.

Two proposals, not one package

BIP-110, titled “Reduced Data Temporary Softfork,” proposed temporary consensus limits on several data-bearing transaction structures. Its stated goal was to constrain arbitrary-data use and refocus Bitcoin on payments. The April 4 record treated BIP-110 as a draft proposal, not active network rules. That distinction is essential: describing a BIP does not show adoption, and publishing code does not establish economic consensus.

BIP-54, “Consensus Cleanup,” was a separate draft. It grouped four categories of maintenance work: limiting a timewarp attack, reducing pathological block-validation cost, addressing a Merkle-tree ambiguity involving 64-byte transactions, and preventing future duplicate transactions without relying on the older BIP-30 check. The proposal’s own rationale said bundling could spread the fixed coordination cost of a soft fork across several fixes.

Wang’s reported response challenged that logic. According to the April 4 accounts, he argued that the timewarp weakness offered Bitcoin miners little practical benefit, that software and hardware improvements had reduced block-validation concerns, and that only the duplicate-transaction issue appeared worth repairing. Those were Wang’s contemporaneous assessments, not independently demonstrated findings in the reports.

Why a miner’s objection carried weight

Mining pools construct candidate blocks and coordinate hash power, making their implementation choices visible during many activation processes. A co-founder’s opposition can therefore signal coordination risk and encourage other participants to scrutinize a proposal’s scope. It cannot, by itself, settle Bitcoin’s rules. Miners do not own validating nodes, exchanges, custodians or users, and a personal post is not equivalent to a signed commitment by a pool.

The sharper governance issue was also easy to blur. BIP-54 bundled four repairs inside one proposal; BIP-110 was not one of those four repairs. Wang opposed both proposals, but the surviving account does not show that developers had formally combined BIP-110 and BIP-54 into a single activation package. Calling them one omnibus upgrade would overstate the record.

For institutions holding or servicing bitcoin, the practical concern was operational rather than directional price speculation. Competing rule sets can require engineering review, compatibility testing, custody planning and monitoring of activation signals. On April 4, however, there was no verified activation, chain split or market-price move attributable to Wang’s comments. This reconstruction therefore makes no causal market claim.

What remained unresolved on April 4

The event-day record established a public disagreement, not an outcome. Open questions included whether Wang was speaking only for himself, whether F2Pool would publish an implementation or signaling policy, whether each draft would change after review, and whether either could attract broad support across miners and non-mining nodes.

The appropriate historical reading is narrow: April 4, 2026 marked a clear objection from an influential mining figure to expanding Bitcoin’s consensus rules through BIP-110 and the multi-fix BIP-54 draft. It did not prove rejection by the network, demonstrate that the cited weaknesses were harmless, or authorize either proposal.