On August 12, an incident occurred in block 962,142 that once again raised the question of the reliability of automated cryptocurrency transaction management tools. One bitcoin wallet user fell victim to their own script, paying a fee of 1.6 BTC (about $102,778) for a transfer that never reached its recipient. All 160,343,885 satoshis that entered the transaction input went to miners, while the output remained empty.

What went wrong?

At the heart of the problem lies the Replace-by-Fee (RBF) function, which allows an unconfirmed transaction to be replaced with a new one carrying a higher fee to speed up processing. This is a useful mechanism during periods of network congestion when standard fees spike sharply. However, in this case, an automated script launched by the user spiraled out of control. Instead of stopping at a reasonable level, the bot increased the fee every second, each time "drawing" more and more funds from the balance.

The end result was catastrophic: the fee consumed the entire input amount. The bitcoin protocol does not limit the fee size, so miners accepted the transaction without a single satoshi in the output. The block was mined by the SpiderPool pool, which received nearly all the funds — the total fee in the block was about 1.82 BTC, and 88% of it came from this erroneous operation.

Lessons for users

This case is a stark reminder that even trusted tools require oversight. First, it is worth completely disabling automatic fee increases via RBF or setting up manual confirmation for each step. Second, a hard fee limit must be set in the wallet settings — most modern solutions allow you to specify a maximum number of satoshis per byte. Third, before large transfers, always run a test transaction with a small amount, especially after software updates.

With the current bitcoin price around $63,770, the mistake cost more than $102,000 — and this despite the recipient not seeing a single cent. Miners, whose profits have been declining for several months, likely viewed this case as a gift from fate. However, for wallet developers, the question remains open: should spending all funds on a fee within a single transaction be allowed?

My view: The incident highlights a systemic problem — excessive automation without proper safeguards is more dangerous than manual management. Until wallets learn to block such scenarios, users can only rely on their own vigilance and common sense.