In an automated transaction, a bitcoin wallet user overpaid miners by 1.6 BTC — approximately $102,778. The funds were deducted, but the recipient never received a single satoshi. The incident was recorded in block 962,142, confirmed on August 12.
Analysis of blockchain data shows that 160,343,885 satoshis were received at the transaction input. The entire amount went to miners, while the output was empty. This outcome is the result of an uncontrolled fee increase caused by a script malfunction.
Cause of the incident: RBF spiraling out of control
The user ran an automated script with the Replace-by-Fee (RBF) function. This mechanism allows replacing an unconfirmed transaction with a new one carrying a higher fee, speeding up payment processing in the mempool. The technology solves a real problem: fees can surge within minutes, and a stuck transfer often waits hours for confirmation.
However, in this case, the script malfunctioned. Instead of stopping at a reasonable level, the bot increased the fee every second, "draining" more funds from the balance with each new version. In the end, the fee consumed the entire input amount. The recipient received nothing, and the transfer entered a block with a zero output. Bitcoin nodes accepted the transaction because the protocol does not limit the fee a sender is willing to pay miners.
The block was mined by the SpiderPool pool, which claimed all the satoshis. The total fee in this block was about 1.82 BTC, with 88% of that amount coming from a single erroneous payment. For mining pools, such luck is a real gift, especially amid declining profitability. Recall that one of the market leaders, Poolin, declared bankruptcy back in July.
Three rules to protect against uncontrolled fees
First, disable automatic fee increases via RBF. Manual confirmation will force you to check every change before sending it to the network. Second, set a hard fee cap. Most modern wallets allow you to specify a maximum number of satoshis per byte, and this limit is enough to quickly stop an erroneous script. Third, always run a test transfer. A couple of thousand satoshis will show whether the bot is working correctly. Those who transfer bitcoins in bulk should perform a trial transaction after every software update.
This situation once again reminded us of the basic rules of self-custody of cryptocurrency. Victims of the Coldcard wallet hack also followed all recommendations but ultimately lost their digital funds. Binance founder Changpeng Zhao noted then that absolutely secure storage does not exist.
Automation in wallets needs to be checked as carefully as the seed phrase — the secret set of words for accessing assets. An uncontrolled script will drain an account faster than any hacker.
Bitcoin was trading near $63,770. At that price, the mistake cost more than $102,000 — a huge loss, especially since not a single cent reached the intended recipient.
Bitcoin miners are unlikely to be upset. Their profits have been declining for months, and companies are leaving the network at record rates. An accidental fee of over $100,000 was a real gift for them. Meanwhile, an open question remains for crypto wallet developers: should a wallet allow spending all funds on a fee within a single transaction?
My comment: this case is a vivid example that even "smart" tools require oversight. RBF is a powerful feature, but automating it without limits is a ticking time bomb. The market needs stricter security standards for wallets, otherwise such incidents will keep happening.