In the coming days, bitcoin may face an extremely dangerous scenario related to the activation of the BIP-110 proposal. This is not just a technical update, but a potential network split that could create fertile ground for stealing funds from careless users.

The essence of the problem is that when the blockchain splits, a double balance situation will arise: the same amount of assets will be reflected in both chains. This opens a direct attack vector for malicious actors who can buy coins of the new network with real bitcoins, exploiting a vulnerability in the transaction mechanism.

Attack mechanics: how funds are lost

In the early stage of the split, transactions are valid in both versions of the network. When an owner decides to sell fork tokens, they sign a transfer that automatically becomes a template for an identical operation in the main network. As a result, an equivalent amount is debited from their address in real bitcoins, and fees are deducted twice. The wallet does not zero out — exactly the amount declared for sale is lost.

The greatest risk is for large holders. The only reliable strategy under current conditions is to keep assets completely static. Without a signed operation, it is impossible to replay a transaction, so a static balance becomes the only protection.

Historical context and technical details

Bitcoin has already gone through a similar hard fork. After the Bitcoin Cash split in 2017, developers had to embed a special mechanism into the new network to prevent transaction replay between chains. The BIP-110 specification lacks such protection, making the situation especially dangerous.

The conflict dates back to fall 2025, when Bitcoin Core v30 raised the OP_RETURN field limit from 80 to 100,000 bytes. Critics viewed this as a simplification for embedding extraneous information in the blockchain, and in December, the Bitcoin Knots team proposed BIP-110, limiting the volume of non-payment data for a year.

For standard activation, the initiative must be confirmed by 1109 of 2016 blocks, but currently only about 2.6% of blocks carry the flag. However, the authors provided an alternative scenario: starting from block #961,632 (expected August 8), nodes with BIP-110 will begin rejecting blocks without the required flag. Since almost the entire hash rate does not set it, these nodes will stop following the main chain. This alone will not create a new blockchain — miners willing to mine under the new rules are needed for a split. Restrictions on non-payment data will take effect later, from block #965,664 in early September.

My analysis: The situation is extremely alarming. The lack of a protective mechanism in BIP-110 is not a technical oversight but a fundamental design flaw. To all bitcoin holders, especially large ones, I strongly recommend refraining from any operations from August 8 until the network fully stabilizes. It is better to miss potential profit from selling fork tokens than to lose real assets.