A glaring case has been recorded in the Bitcoin blockchain: a user paid a fee of 1.6 BTC (about $102,778) but never transferred a single satoshi to the recipient. The transaction was confirmed on August 12 in block 962,142.
Analysis of the blockchain data shows one input of 160,343,885 satoshis. All these funds went to miners, and the only output remained empty. This is not a protocol error, but the result of a failure in an automated script used by the wallet owner.
Cause of the incident: an out-of-control RBF script
The user ran an automated script with the Replace-by-Fee (RBF) function. This mechanism allows replacing an unconfirmed transaction with another one carrying a higher fee to speed up its processing in the mempool. RBF is a useful tool, especially when network fees spike sharply and transfers get stuck for hours.
However, this time the script malfunctioned. Instead of stopping at a reasonable level, the bot increased the fee every second. With each new version, it "consumed" more and more funds from the balance. As a result, the fee absorbed the entire input amount, and the recipient did not see a single satoshi.
Miners accepted the transaction because the Bitcoin protocol does not limit the fee a sender is willing to pay. The block was mined by the SpiderPool pool, which took 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, this is a real gift, especially amid declining profitability.
How to protect yourself from such errors?
This case is a stark reminder of the basic security rules when working with cryptocurrency. First, disable automatic fee increases via RBF. Manually confirming each change will force you to verify every figure before sending it to the network.
Second, set a hard cap on the fee. Most modern wallets allow you to specify a maximum number of satoshis per byte. This limit is enough to quickly stop an erroneous script.
Third, always conduct a test transfer. A couple of thousand satoshis will show whether the bot is working correctly. Those who transfer Bitcoin in bulk should run a test transaction after every software update.
The situation 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 then noted that absolutely secure storage does not exist. Automation in wallets should be checked as carefully as the seed phrase—the secret set of words for accessing digital assets. An uncontrolled script will drain an account faster than any hacker.
My comment: This incident highlights a critical vulnerability not in the Bitcoin protocol, but in user tools. Wallet developers have long needed to implement mandatory "safeguards" that block transactions where the fee exceeds, say, 10% of the transfer amount. Until then, users remain hostages to their own mistakes and imperfect automation.