Attention to the upcoming BIP-110 soft fork is drawn not only by ideological debates about spam, but also by a real technical vulnerability. Blockchain expert Kevin Loak warns: attempting to sell coins obtained as a result of a network split could result in the loss of your real bitcoins. This is not just a theoretical risk, but a very specific attack vector that malicious actors could exploit within the first hours after activation.

Double balance and a trap for sellers

The essence of the problem is that the blockchain split will create a situation of double balance. The same amount of assets will be attributed to your address in both chains simultaneously. This is where the main danger lies. Attackers will start buying coins of the new network, offering real bitcoins for them. At an early stage, transactions are valid in both versions of the network. By signing a transfer of fork tokens, you inadvertently hand the buyer a ready-made template for an identical operation on the main network. Using your signature, they debit an equivalent amount, but in real bitcoins, and fees are deducted twice. At the same time, your wallet is not emptied — exactly the amount that was offered for sale is lost.

The first to be hit will likely be large holders who decide to quickly monetize "free" coins. The only reliable strategy in such a situation is to keep assets stationary. Copying a transaction requires a signed operation, and if there is none, there is nothing to reproduce.

Historical context and technical details

Bitcoin has already gone through a similar hard fork. After the Bitcoin Cash split in 2017, developers had to integrate 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.

The dispute has been ongoing since 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 the placement of extraneous information in 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.

At the same time, this alone will not create a new blockchain. A split requires miners who will continue mining blocks according to the proposal's rules. 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 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 then use them to separate one balance from another. The speed of block mining could shift both dates by about a day in either direction.

My analysis: The situation with BIP-110 is a classic example of how good intentions can create serious risks for holders. The lack of protection against transaction replay is not just an oversight, but a potential time bomb. I strongly recommend that anyone planning to participate in the asset split wait for network stabilization and not succumb to the temptation of quickly selling fork tokens. In cryptocurrencies, as in life, free cheese only comes in a mousetrap.