A glaring incident occurred on the Bitcoin network: a user lost over $102,000 in fees on a single transaction, while the recipient did not see a single satoshi. The incident was recorded on August 12 in block 962,142, where the fee amount reached 1.6 BTC.
Blockchain analysis shows one input of 160,343,885 satoshis. All these funds went to miners, while the single output remained empty. This is a classic example of how automation without proper oversight can lead to catastrophic financial losses.
The Root of the Problem: Unrestrained RBF
At the heart of the incident lies the Replace-by-Fee (RBF) feature, which allows an unconfirmed transaction to be replaced with a new one carrying a higher fee to speed up processing. The user ran an automated script with this feature, but something went wrong. Instead of stopping at a reasonable level, the bot began increasing the fee every second, "eating" more and more funds from the balance with each new version.
In the end, the fee consumed the entire input amount. The recipient received nothing, and the transfer landed in a block with a zero output. Bitcoin nodes accepted the transaction because the protocol does not limit the fee a sender is willing to pay miners. The block was mined by the SpiderPool pool, which took all the satoshis. The total fee in this block was about 1.82 BTC, and 88% of that amount came from a single erroneous transaction.
How to Protect Yourself from Uncontrolled Fees
This case is a stark reminder of the need for manual oversight. First, automatic fee increases via RBF should be disabled. Manually confirming each change before sending it to the network is a mandatory condition.
Second, set a hard fee cap. Most modern wallets allow you to specify a maximum number of satoshis per byte, and this limit is enough to quickly stop an erroneous script.
Third, always conduct a test transfer. A couple of thousand satoshis will show whether the bot is working correctly. Those who transfer Bitcoin in bulk should run a test transaction after every software update.
The situation recalled the basic rules of self-custody for cryptocurrency. Victims of the Coldcard wallet hack also followed all recommendations but ultimately lost their digital funds. Binance founder Changpeng Zhao noted at the time that absolutely secure storage does not exist.
Automation in wallets should be checked as carefully as the seed phrase—the secret set of words for accessing digital assets. An uncontrolled script will drain an account faster than any hacker.
Bitcoin was trading near $63,770. At that price, the mistake cost more than $102,000—a huge loss, especially since not a single cent reached the intended recipient.
Bitcoin miners are unlikely to be upset. Their profits have been falling for several months, and companies are leaving the network at record rates. The accidental fee of over $100,000 was a real gift for them. Meanwhile, the question remains open for cryptocurrency wallet developers: should a wallet allow spending all funds on fees within a single transaction?
My comment: this incident is a vivid example that "smart" features in wallets require no less trust than third-party services. The industry has long needed to implement mandatory safeguards, such as fee multipliers or balance-based limits, to protect users from themselves.