On August 12, an incident occurred in block 962142 that exposed a critical vulnerability in cryptocurrency transaction automation. A bitcoin wallet owner transferred 1.6 BTC (about $102,778) as a transaction fee, but the recipient never received a single satoshi.
Analysis of blockchain data shows that the transaction had one input of 160,343,885 satoshis. All of these funds went to miners, and the output remained empty. This is a classic example of how automated systems can spiral out of control, turning from an optimization tool into a source of catastrophic losses.
The root of the problem: unchecked RBF
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 in the mempool. This mechanism is designed to solve a real problem: fees can spike within minutes, and a stuck payment often waits hours for confirmation.
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 "drew" more and more funds from the balance. As a result, the fee consumed the entire input amount. The recipient received nothing, and the transfer landed in a block with a zero output.
Why did the network accept this transaction?
Bitcoin miners accepted the transaction because the protocol does not limit the fee amount 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 payment.
How to protect yourself: three key settings
First, automatic fee increases via RBF should be disabled. Manual confirmation forces you to verify each increase before sending it to the network. Second, a hard fee cap should be set. 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, a test transfer is always necessary. A few thousand satoshis will show whether the bot is working correctly.
This situation serves as a reminder of the basic rules of self-custody for cryptocurrency. Victims of the Coldcard wallet hack also followed all recommendations but ultimately lost their digital funds. Binance founder Changpeng Zhao noted at the time 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.
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 falling for months, and companies are leaving the network at record rates. A random fee of over $100,000 was a real gift for them. Meanwhile, the question remains open for cryptocurrency wallet developers: should a wallet allow spending all funds on a fee within a single transaction?
My view: this case is not just a coincidence but a systemic signal. The industry has relied too long on "smart" algorithms without proper oversight. Tools like RBF require built-in safeguards, such as an absolute fee limit and multi-step verification. Otherwise, we will see more and more stories where automation turns $100,000 into dust.