Blockchain expert Kevin Loak has identified a critical vulnerability related to the upcoming Bitcoin network split due to the activation of BIP-110. In the coming days, a new fork token is expected to appear, and attempting to sell these coins could result in the loss of real bitcoins. This is not just a technical nuance, but a serious threat to holders hoping to obtain "free" assets.

Attack Mechanics: Double Balance and Transaction Interception

The blockchain split will create a situation where the same amount of funds will be displayed on both chains. At the initial stage, transactions are valid on both versions of the network. By signing a transfer of fork tokens, the seller unknowingly provides the buyer with a ready-made template for an identical operation on the main network. This allows attackers to copy the signature and debit an equivalent amount in real bitcoins from the same address, charging fees twice. The wallet does not zero out — exactly the amount declared for sale is lost.

Large holders, who most often conduct transactions with significant volumes, are at the highest risk of being hit first. The only reliable strategy at this point is to keep assets completely stationary. Copying a transaction requires a signed operation, and if there is none, there is nothing to reproduce.

Historical Context and Lack of Protection

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

Why the Network Is on the Brink of a Split

The dispute dates back to the fall of 2025, when developers released Bitcoin Core v30 and raised the OP_RETURN field limit from 80 to 100,000 bytes. Critics decided that the change would simplify placing extraneous information on the blockchain, so in December the Bitcoin Knots team proposed BIP-110, which limits the volume of non-payment data for a year.

For standard activation, the initiative must be confirmed by 1109 out of 2016 blocks. Currently, about 2.6% of blocks contain the BIP-110 flag. However, the authors also provided another 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 that point, 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 on one branch, and then use them to separate one balance from the other. The speed of block mining could shift both dates by roughly a day in either direction.

My analysis: the BIP-110 situation is a classic 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 during the network split period until there is a clear understanding of which chain will become dominant. Otherwise, an attempt to profit from the fork could lead to irreversible loss of funds.