In the coming days, the Bitcoin community may face a serious challenge: the activation of BIP-110 creates conditions for a dangerous attack on user funds. This is not about a theoretical vulnerability, but a real theft vector that has already been dubbed the "double balance."
Mechanics of the threat: how a fork becomes a trap
The essence of the problem is that when the blockchain splits, the same volume of assets will be reflected in both chains. Attackers can exploit this by offering to buy the new network's coins for real bitcoins. At an early stage, transactions are valid in both versions of the network. By signing a transfer of fork tokens, the seller inadvertently hands the buyer a ready-made template for an identical operation on the main network.
As a result, an equivalent amount is debited from the same address, but this time in real bitcoins, and fees are deducted twice. The wallet is not zeroed out—exactly the volume that was listed for sale is lost. Large holders who want to quickly cash in on the "free" coins are the first to be at risk.
Why the network ended up on the brink of a split
The conflict dates back to the fall of 2025, when Bitcoin Core v30 developers raised the OP_RETURN field limit from 80 to 100,000 bytes. Critics argued that this would simplify the placement of 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 out of 2016 blocks, but currently only about 2.6% of blocks carry the flag.
However, the authors provided a fallback scenario. Starting from block #961,632, expected on 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. By itself, this will not create a new blockchain—miners who continue to mine blocks under the proposal's rules are needed for a split. If none are found, the alternative chain will not emerge.
The BIP-110 restrictions on non-payment data will take effect later—starting from block #965,664, expected in early September. Until then, both networks will be able to accept the same operations. To safely separate assets, the owner will first need to obtain coins that exist only in one branch, and only then use them to separate one balance from the other.
My assessment: The situation resembles the chaos around Bitcoin Cash in 2017, but with one key difference—the BIP-110 specification lacks a protective mechanism to prevent the transfer of transactions between chains. The only reliable strategy for holders is to keep assets idle until the networks are fully separated. Any attempt to "make a quick profit" on the fork could result in the loss of real funds. I recommend refraining from any operations with fork tokens in the coming weeks.