Background of BIP‑110 and the Fork
BIP‑110, short for Bitcoin Improvement Proposal‑110, proposes a rule that blocks must signal support for the change. The aim is to prevent non‑financial data—such as pictures and text—from being stored in Bitcoin transactions for an entire year, a practice critics say can congest the network and raise transaction costs for legitimate users. Opponents argue that paying a fee gives a user the right to use the block space however they wish, and that miners and node operators should not be deciding which transactions are valid.
When BIP‑110 supporters split from the main Bitcoin network on Saturday, they activated a minority chain that began rejecting any block that did not carry a support signal. This new chain started at block 961,632, while the main chain had already reached block 961,681.
Initial Block Production and Current Status
The fork produced two blocks in about eight hours, landing at block 961,633. At the same time, the main Bitcoin blockchain was at block 961,681, showing a gap of 48 blocks—roughly a day’s worth of activity on one side and almost none on the other.
The first block that the BIP‑110 chain rejected was mined by the AntPool mining firm and accepted by the rest of the network. An alternative block was produced by the Ocean mining pool, which the breakaway chain accepted.
Technical Challenges: Difficulty Adjustment and Mining Power
Bitcoin adjusts mining difficulty every 2,016 blocks to keep block production at about a ten‑minute cadence. The BIP‑110 chain inherited the current difficulty setting but controls only a tiny fraction of the total hash power. Consequently, its blocks appear at long intervals. The current difficulty adjustment schedule projects that the fork will need about 350 days to reach the next recalibration point, compared to just 14 days for the main chain.
Because the fork’s block production is so sparse, it cannot lower the difficulty until it completes 2,016 blocks at the present pace, a condition that is unlikely to be met in the near term.
Adoption and Support Levels
Over the past two weeks, only 2.53 % of blocks on the main chain have signaled support for BIP‑110. Activation of the proposal would have required 55 % support without a split, and the current level is far below that threshold.
The fork’s lack of momentum leaves it in a precarious position for anyone hoping to trade or hold its coins. Both chains accept the same transactions, meaning a signed transaction that moves fork coins will also be valid on the main Bitcoin network. A buyer could rebroadcast the same transaction on Bitcoin and receive real BTC from the seller, creating a potential attack vector that users must monitor.
Implications for Users and Potential Risks
A chain that produces a block every several hours is slow to confirm sales, making it unattractive for traders. Moreover, the identical transaction sets mean that a user could inadvertently lose funds if they rely on the fork’s block confirmations.
The two‑week window during which BIP‑110 nodes require every block to signal support ends at block 963,647. At the current production pace, the fork will not approach that milestone.
Future Outlook and Related Developments
While the BIP‑110 fork remains stalled, other cryptocurrency projects are advancing. Zcash’s upcoming Tachyon upgrade, for example, aims to scale shielded payments, improve quantum‑resistance, and test its funding, security, and governance structures.
The BIP‑110 situation highlights the challenges of introducing protocol changes through a hard fork and the importance of broad miner and community support to ensure a functional network.
