An incident occurred on the Bitcoin network that once again reminds us of the hidden risks of automating cryptocurrency operations. One user, in an attempt to speed up a transfer, accidentally initiated a transaction with a fee of 1.6 BTC — about $102,778 at the time of confirmation. The funds were debited from the balance, but the recipient never received a single satoshi.

According to blockchain data, on August 12, block 962,142 recorded a transaction with one input of 160,343,885 satoshis. The entire amount went to miners, while the output remained empty. In essence, the user sent their entire balance as a reward for processing a transfer that was never completed.

The root of the problem: unchecked RBF

The cause was an automated script using the Replace-by-Fee (RBF) function. This mechanism allows replacing an unconfirmed transaction with a new one carrying a higher fee, which is useful during periods of network congestion when standard payments can hang for hours. However, in this case, the algorithm malfunctioned: instead of stopping at a reasonable level, the bot increased the fee every second, literally "eating" funds from the balance.

The Bitcoin protocol does not limit the fee size that a sender can set, so miners from the SpiderPool, who mined this block, gladly accepted the transaction. The total fee in the block was about 1.82 BTC, and 88% of that amount came from the erroneous payment.

How to protect yourself from uncontrolled fees

This case is a serious signal for everyone using automated wallet management tools. First, you should disable automatic fee increases via RBF and switch this process to manual mode. Second, it is worth setting a hard fee limit in your wallet settings — most modern solutions allow you to specify a maximum number of satoshis per byte. Third, before launching new scripts or after updating software, always run a test transaction for a small amount.

The situation also raises an important question about whether a wallet should even allow spending all funds on fees within a single operation. Clearly, developers should consider built-in protective mechanisms to prevent such scenarios.

My comment: This incident is a vivid example that automation in cryptocurrencies requires no less caution than storing secret keys. The market is currently going through tough times for miners, and such "gifts" only highlight how fragile the balance between convenience and security can be. Always check the settings of your tools — the cost of a mistake can be measured in tens of thousands of dollars.