In the world of cryptocurrencies, even experienced users sometimes make costly mistakes. This time, the victim was a bitcoin wallet owner who accidentally paid a fee of 1.6 BTC — over $102,000 — for a transfer that never reached its recipient. The transaction was confirmed on August 12 in block 962,142.
Blockchain analysis shows that the transaction input contained 160,343,885 satoshis. All these funds went to miners as a fee, and the output remained empty. In other words, the user did not transfer a single coin but simply gifted the SpiderPool pool, which mined this block, a substantial amount.
Why the fee spiraled out of control
The cause of the incident was an automated script with the Replace-by-Fee (RBF) function. This function allows replacing an unconfirmed transaction with a new one carrying a higher fee to speed up its processing in the mempool. Usually, this is a useful tool, especially when fees surge within minutes and a payment gets stuck for hours.
However, this time the script malfunctioned. Instead of stopping at a reasonable level, the bot increased the fee every second, "draining" more and more funds from the balance. In the end, the fee consumed the entire input amount, and the recipient received nothing. The block was mined with a zero output, which is a rare but possible occurrence.
Notably, the total fee in this block was about 1.82 BTC, and 88% of that amount came from a single erroneous transaction. Mining pools find such "luck" especially timely: their profits have been declining for months, and companies are leaving the network at record rates. An accidental fee of over $100,000 was a real gift for them.
How to protect yourself from such mistakes
To avoid such situations, several measures must be taken. First, disable automatic fee increases via RBF. Manual confirmation will force you to check every change before sending it to the network.
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 few thousand satoshis will show whether the bot is working correctly. Those who transfer bitcoins in bulk should run a test transaction after every software update.
This situation once again reminds us of the basic rules of self-custody of cryptocurrency. Automation in wallets needs to be checked as carefully as the seed phrase. An uncontrolled script can empty an account faster than any hacker.
Bitcoin was trading near $63,770 at the time of the incident, making the mistake even more painful. Losses exceeded $102,000, and not a single cent reached the intended address. The question remains open: should a wallet allow spending all funds on a fee within a single transaction? It seems developers should consider introducing protective mechanisms.
My comment: this case is a vivid example that even technically advanced users can fall victim to their own tools. RBF is a powerful function, but it requires caution. I strongly recommend that anyone using automated scripts implement limits and test modes. In the world of cryptocurrencies, the price of a mistake can be catastrophic.