A glaring incident has been recorded on the Bitcoin blockchain: a wallet owner overpaid 1.6 BTC (about $102,778) in transaction fees for a transaction that was never delivered to the recipient. The incident occurred on August 12 in block 962,142.
Data analysis shows that the transaction input was 160,343,885 satoshis, and the entire amount went to miners. The output remained empty—not a single satoshi reached the destination. This is not just a technical glitch but a systemic error in the operation of automated fee management tools.
Why the fee spiraled out of control
The user ran a script with the Replace-by-Fee (RBF) function, which allows replacing an unconfirmed transaction with a new one carrying a higher fee to speed up processing in the mempool. The mechanism is useful when the network is congested and fees surge sharply. However, this time the script malfunctioned: instead of stopping at a reasonable level, it increased the fee every second, literally devouring the balance.
As a result, the fee consumed the entire input amount. The Bitcoin protocol does not limit the fee size a sender can set, so miners accepted the transaction without hesitation. The block was mined by the SpiderPool pool, which took all the satoshis. The total fee in the block was about 1.82 BTC, and 88% of that amount came from a single erroneous transaction. For miners, whose profits have been declining for months, such a gift is a real stroke of luck.
Three rules to protect against uncontrolled fees
This case is a stark reminder of the basic security principles when working with cryptocurrency. First, disable automatic fee increases via RBF. Manually confirming each change before sending it to the network is the only reliable barrier.
Second, set a hard fee cap. Modern wallets allow you to set a limit in satoshis per byte, and that is enough to stop an erroneous script. Third, always conduct a test transfer. A few thousand satoshis will show whether the bot is working correctly, especially after software updates.
Automation in wallets requires the same careful oversight as storing seed phrases. An uncontrolled script will drain an account faster than any hacker. Bitcoin was trading near $63,770, and the mistake cost over $100,000—a huge loss, especially since not a single cent reached the intended address.
My comment: this incident raises an important question about whether wallets should allow spending all funds on fees within a single transaction. Until developers implement mandatory limits, users should rely only on their own vigilance and testing. The cryptocurrency market teaches us: even the best tools can become a trap without proper configuration.