A glaring incident occurred on the Bitcoin blockchain: a cryptocurrency holder paid a fee of 1.6 BTC (about $102,778) for a transaction that was never delivered to the recipient. The incident was recorded on August 12 in block 962,142.
Data analysis shows that 160,343,885 satoshis entered the transaction input. All these funds were directed to miners, while the output remained empty. In other words, the transfer was made in vain, and the entire amount went as a reward for processing the block.
The Root of the Problem: An Automated Script with RBF
The cause was a malfunction in an automated script using the Replace-by-Fee (RBF) function. This option allows replacing an unconfirmed transaction with a new one carrying a higher fee to speed up processing in the mempool. It is a standard tool for dealing with network congestion when fees surge within minutes.
However, this time the bot behaved erratically. Instead of stopping at a reasonable level, it began increasing the fee every second. With each new transaction variant, the script "consumed" more and more funds from the balance, until the fee swallowed the entire input amount.
The Bitcoin protocol does not limit the maximum fee size, so miners accepted the transaction without any issues. The block was mined by the SpiderPool pool, which received all the satoshis. The total fee in this block was about 1.82 BTC, with 88% of that amount coming from a single erroneous transaction.
How to Protect Yourself from Such Errors
This case is a stark reminder of the need to control automation. First, you should disable automatic fee increases via RBF. Manually confirming each change will force you to check every operation before sending.
Second, set a hard limit on fees. Most modern wallets allow you to set a maximum number of satoshis per byte, and this restriction is enough to stop a faulty script.
Third, always conduct a test transfer. A couple of thousand satoshis will show whether the bot is working correctly. This is especially important after every software update.
The situation also raises a fundamental question: should a wallet even allow spending all funds on fees within a single transaction? While miners, whose profits have been declining for several months, received a real gift, this case should serve as a signal for cryptocurrency wallet developers to implement stricter protective mechanisms.
My expert opinion: This incident is not just an unfortunate accident but a systemic gap in the UX design of cryptocurrency wallets. As long as the protocol imposes no restrictions on fees, the responsibility for fund security lies with developers, who must implement "safeguards" against such scenarios. Otherwise, we will continue to witness automation, designed to simplify life, becoming the cause of losses amounting to thousands.