On August 12, a transaction was recorded in block 962,142 that became a real nightmare for the sender. A bitcoin wallet user transferred 1.6 BTC (~$102,778) as a fee, but did not send a single satoshi to the recipient's address.
Blockchain data analysis shows that 160,343,885 satoshis were received as input to the transaction, and all of these funds went to miners. The only output remained empty — the recipient received nothing.
What went wrong: uncontrolled RBF
The cause of the incident was a failure in an automatic script using the Replace-by-Fee (RBF) function. This mechanism allows an unconfirmed transaction to be replaced with a new one with a higher fee to speed up its inclusion in a block. RBF is a useful tool in a congested network, when transfer fees can spike within minutes and a stuck payment waits for confirmation for hours.
However, this time the script failed. Instead of stopping at a reasonable level, the bot increased the fee every second, "taking" more and more funds from the balance. As a result, the fee consumed the entire input amount, and the recipient never received the transfer.
Miners, of course, did not refuse such a gift. The block was mined by the SpiderPool pool, which received 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. For mining pools, whose profits have been declining for several months, such "accidents" are a real find.
How to protect yourself from such errors
This case is a vivid reminder that automation in cryptocurrencies requires special attention. First, you should disable automatic fee increases via RBF. Manually confirming each change before sending it to the network is a reliable barrier.
Second, you need to 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 stop an out-of-control script.
Third, always conduct a test transfer. A couple of thousand satoshis will show whether the bot is working correctly. Those who mass-transfer bitcoins should perform a verification transaction after every software update.
This situation also raises an important question about the security of self-custody of crypto assets. Even following all recommendations, users may face unforeseen problems. As Binance founder Changpeng Zhao noted, absolutely secure storage does not exist. Therefore, automation in wallets needs to be checked as carefully as the seed phrase — because an uncontrolled script can empty an account faster than any hacker.
At the time of the incident, bitcoin was trading near $63,770, making the mistake even more painful — the loss exceeded $102,000, and not a cent reached the intended address. This case is a warning signal for wallet developers: should they even allow spending all funds on a fee within a single transaction? The answer, in my opinion, is obvious — no. Introducing hard limits and warnings could prevent such losses in the future.