In the coming days, bitcoin could face a serious test that many holders underestimate. This concerns a potential soft fork initiated through the BIP-110 proposal, which, in my assessment, carries a hidden threat to asset security. Blockchain expert Kevin Loak is already raising the alarm, pointing to a mechanism that could lead to the loss of real BTC for those who try to "sell" coins obtained as a result of the network split.

The crux of the problem is that the blockchain split will create a "double balance" situation: the same amount of funds will be displayed in both chains. This is exactly where a window opens for attackers. At the initial stage, transactions in both versions of the network will be valid. By signing a transfer of fork tokens, the seller, without realizing it, hands the buyer a ready-made template for an identical operation on the main network. An equivalent amount is debited from the same address, but in real bitcoins, and fees are charged twice. At the same time, the wallet is not zeroed out—exactly the amount declared for sale is lost.

The most vulnerable here are large holders. The only reliable strategy in this situation is to keep assets completely immobile. Copying a transaction requires a signed operation, and if there is none, there is nothing to reproduce. This is a critically important point that I recommend everyone planning any moves in the coming days to take into account.

A similar scenario has already occurred in bitcoin's history. After the Bitcoin Cash split in 2017, developers had to build a special mechanism into the new network to prevent the transfer of transactions between chains. The BIP-110 specification lacks such protection, making the situation especially dangerous.

Why the network ended up on the brink of a split

The conflict had been brewing since autumn 2025, when Bitcoin Core v30 developers raised the OP_RETURN field limit from 80 to 100,000 bytes. Critics believed this would simplify the placement of extraneous information in the blockchain, which led to the emergence of BIP-110 in December. The initiative limits the volume of non-payment data for a year, and for standard activation it needs support from 1109 of 2016 blocks. Currently, about 2.6% of blocks contain the BIP-110 flag.

The authors also provided for a stricter 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 hashrate does not set it, these nodes will stop following the main chain. However, this alone will not create a new blockchain—miners willing to mine blocks under the new rules are needed for that. If none are found, the alternative chain will not emerge.

The BIP-110 restrictions on non-payment data will take effect later—from block #965,664, expected in early September. Until that moment, both networks will be able to accept the same operations. To safely split assets, the owner will first have to obtain coins that exist only in one branch, and only then use them to separate one balance from another. The block mining speed could shift both dates by roughly a day in either direction.

My analysis: The situation around BIP-110 is a classic example of how technical disputes over scalability can escalate into a threat to users. I recommend that all BTC holders refrain from any transactions between August 8 and early September, until the final network configuration becomes clear. Even if you do not plan to participate in the "distribution" of fork tokens, your activity could be used against you.