On August 12, an incident occurred in block 962,142 that exposed a serious vulnerability in the automation of cryptocurrency transactions. One user of the Bitcoin network, due to a script error, paid a fee of 1.6 BTC — over $102,000 — while the recipient did not receive a single satoshi.
Analysis of blockchain data shows that the transaction had one input of 160,343,885 satoshis, and all of these funds were directed to miners. The output remained empty, meaning the sender lost the funds entirely.
What went wrong?
The user ran an automated 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. This is a standard tool for dealing with mempool congestion, but in this case, the bot spiraled out of control.
Instead of stopping at a reasonable level, the script increased the fee every second. With each new version of the transaction, it "consumed" more and more funds from the balance. Ultimately, the fee absorbed the entire input amount, and the transfer was included in a block with a zero output. Miners accepted the transaction because the Bitcoin protocol does not limit the fee amount a sender is willing to pay.
The block was mined by the SpiderPool pool, which received all the satoshis. The total fee in this block was about 1.82 BTC, and 88% of that amount came from a single erroneous transaction. For mining pools, such luck is especially welcome — their profits have been declining for several months, and companies are leaving the network at record rates.
How to protect against such errors?
This case serves as a reminder of the basic security rules for self-custody of cryptocurrency. First, you should disable automatic fee increases via RBF and switch to manually confirming each change. Second, it is worth setting a hard fee cap — most modern wallets allow you to specify a maximum number of satoshis per byte, and this limit is enough to stop a malfunctioning script.
Third, always conduct a test transfer. A few thousand satoshis will show whether the bot is working correctly before you send a significant amount. Those who transfer Bitcoin in bulk should verify transactions after every software update.
Automation in wallets needs to be checked just as carefully as the seed phrase. An uncontrolled script will drain an account faster than any hacker.
My comment: This incident is a vivid example that even experienced users underestimate the risks of automation. Wallet developers should consider implementing mandatory fee limits, especially for RBF transactions. As long as the protocol allows spending all funds on fees, such errors will keep recurring.