In the coming days, the bitcoin community may face a serious challenge: the activation of the BIP-110 soft fork creates fertile ground for a new wave of attacks on coin holders. Blockchain expert Kevin Loak warns that those who try to sell tokens obtained as a result of the network split risk losing their real bitcoins. This is not just a technical detail, but a real threat for those hoping for a "free" airdrop.
The essence of the problem is that the blockchain split will lead to a double balance: the same volume of assets will simultaneously exist in both chains. It is precisely this, in my deep conviction, that attackers will exploit. They 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, the seller inadvertently provides the buyer with a ready-made template for an identical operation in the main network. As a result, an equivalent amount is debited from the same address, but in real bitcoins, and fees are deducted twice. At the same time, the wallet is not zeroed out—exactly the volume that was declared for sale is lost.
The first to be hit will likely be large holders—they are the ones who most often try to quickly monetize a fork. The only reliable strategy, as Loak rightly notes, is to keep assets stationary. To copy a transaction, a signed operation is required, and if there is none, there is nothing to reproduce.
Why the network is on the brink of a split
The dispute has been ongoing since 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 placing extraneous information in the blockchain. 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.
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—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 separate 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 speed of block mining could shift both dates by approximately a day in either direction.
My expert assessment: this situation is a vivid example of how technical disputes in the community create real risks for ordinary users. Bitcoin has already gone through a similar hard fork with Bitcoin Cash in 2017, and then developers had to build a special protection mechanism into the new network. The BIP-110 specification lacks such protection, making this initiative especially dangerous. I recommend that all bitcoin holders exercise maximum caution and refrain from any operations with fork tokens in the coming weeks.