A notable incident occurred in the Bitcoin blockchain, once again reminding us of the hidden risks of automating cryptocurrency operations. On August 12, in block 962,142, a transaction with a fee of 1.6 BTC was recorded—over $102,000 at the current exchange rate. However, the recipient did not receive a single satoshi: all funds went to the miners.

Data analysis shows one input of 160,343,885 satoshis. The entire amount was deducted as a fee, and the transaction output remained empty. This is a classic example of how an error in automation can lead to a complete loss of funds.

What went wrong?

The cause was a malfunction in an automatic script using the Replace-by-Fee (RBF) function. This mechanism allows replacing an unconfirmed transaction with a new one carrying a higher fee to speed up its processing in the mempool. In theory, RBF is a useful tool, especially when the network is congested and fees spike within minutes.

However, in this case, the bot behaved erratically. Instead of stopping at a reasonable level, it increased the fee every second, "eating" more and more funds from the balance with each new version. As a result, the fee consumed the entire input amount, and the recipient never received a single coin.

Who benefited?

The block was mined by the SpiderPool pool, which claimed all the satoshis. The total fee in this block was about 1.82 BTC, and 88% of that amount came from the erroneous payment. For miners, whose profits have been declining for several months, such a gift was a stroke of luck. Especially against the backdrop of some pools, including one of the market leaders, declaring bankruptcy in July.

How to protect yourself?

This case is a stark reminder of the need to control automation in wallets. I recommend following three simple rules:

  • Disable automatic fee increases via RBF. Manually confirming each change will force you to check the numbers before sending.
  • Set a hard fee limit. Most modern wallets allow you to specify a maximum number of satoshis per byte—this is enough to stop a faulty script.
  • Always conduct a test transfer. A few thousand satoshis will show whether the bot works correctly after each software update.

The situation also raises an important question: should a wallet even allow all funds to be deducted as a fee within a single transaction? While developers address this challenge, users should remember: automation in wallets requires no less scrutiny than a seed phrase. A thoughtless script can drain an account faster than any hacker.

My verdict: This is not just an unfortunate accident, but a systemic gap in the security of user interfaces. The incident with the $102,000 fee should serve as a signal for all cryptocurrency holders: trust, but verify every line of code that manages your money.