A glaring incident has been recorded in the Bitcoin blockchain, serving as a stark reminder of the risks of automation in the world of cryptocurrencies. On August 12, in block No. 962,142, a transaction was confirmed where the sender, instead of transferring funds, burned 1.6 BTC in fees at once — more than $102,000 at the current exchange rate. The recipient did not receive a single satoshi: all 160,343,885 satoshis from the input went to the miners, and the transaction output turned out to be empty.

Root of the problem: a mindless RBF script

The cause of the incident was an automated system with the Replace-by-Fee (RBF) function. This mechanism, designed to speed up "stuck" transfers by increasing the fee, spiraled out of control. Instead of stopping at a reasonable level, the bot literally "hiked" the fee every second, creating new versions of the transaction with ever-higher fees per byte.

In the end, the algorithm "consumed" the entire amount intended for the transfer. The Bitcoin protocol does not limit the fee size, so the network accepted the transaction, and the mining pool SpiderPool, which mined the block, received a record reward. The total fee in the block was about 1.82 BTC, and 88% of that amount came from a single erroneous operation.

Lessons for security: three key rules

To avoid repeating such mistakes, it is necessary to implement simple but critically important measures. First, categorically disable automatic fee increases via RBF. Manually confirming each change will force you to check the numbers before sending them to the network.

Second, set a hard limit on the fee. Most modern wallets allow you to set a maximum number of satoshis per byte. This limit is enough to instantly stop a faulty script. Third, always conduct a test transfer. A couple of thousand satoshis will show whether the bot is working correctly before you entrust it with your funds.

This case is yet another piece of evidence that absolutely secure storage does not exist. Even when following all recommendations, automation in wallets requires the same careful control as the seed phrase. A mindless script can empty an account faster than any hacker. Miners, whose profits have been falling for several months in a row, likely perceived this $100,000 gift as manna from heaven. However, for wallet developers, the question remains open: should the system even allow spending all funds on fees within a single transaction?

My comment: This incident highlights a fundamental UX problem in Bitcoin: the protocol's flexibility turns into a risk for inattentive users. I think the industry is long overdue for seriously considering the implementation of "safeguards" at the wallet level that would block abnormally high fees. Otherwise, such stories will repeat, undermining trust in the very mechanism of transfers.