In the coming days, the Bitcoin network may face a unique phenomenon—a soft fork initiated by proposal BIP-110. However, as I discovered through my own analysis, this situation carries a hidden threat to asset holders that could lead to direct financial losses.
The core of the problem lies in the creation of a so-called "double balance." When the blockchain splits, the same amount of funds will be reflected in both chains. This is precisely what, according to my data, attackers plan to exploit. The attack scheme looks like this: at an early stage, transactions are valid in both versions of the network. When the owner signs a transfer of fork tokens, they inadvertently create a template for an identical operation on the main chain. An attacker, having obtained this template, can replicate the transaction on the original network, debiting an equivalent amount from the address in real bitcoins. In this case, the fee is deducted twice, and the wallet is not zeroed out—exactly the amount declared for sale is lost.
Who is at risk and how to protect yourself
Large holders who decide to quickly monetize "free" coins will likely be the first to be hit. 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 simply nothing to replicate. This is a critically important point that many overlook in the pursuit of quick profits.
A historical precedent already exists: after the Bitcoin Cash split in 2017, developers had to embed a special protective mechanism into the new network to prevent the transfer of transactions between chains. Such protection is absent in the BIP-110 specification, making the situation especially dangerous.
Why the network is 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 believed this would simplify the placement of extraneous information on the blockchain. In response, the Bitcoin Knots team proposed BIP-110 in December, limiting the volume of non-payment data for a year. For standard activation, the initiative must be supported 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. True, this alone will not create a new blockchain—miners willing to mine blocks under the proposal's rules are needed for a split. If none are found, the alternative chain simply will not emerge.
The BIP-110 restrictions on non-payment data will take effect later—from block #965,664, expected in early September. Until then, both networks will be able to accept the same operations, which creates a window of vulnerability. The speed of block mining could shift both dates by roughly a day in either direction.
My verdict: This situation is a vivid example of how technical disputes within the community can create real financial risks for ordinary users. I recommend that all Bitcoin holders refrain from any operations with "fork coins" in the coming weeks and wait for the network to stabilize. In cryptocurrencies, sometimes the best strategy is complete inaction.