Two On-Chain Incidents Cost Crypto Investors $63 Million in One Month

Recent incidents in the cryptocurrency space have seen a total of $63 million lost due to on-chain operational errors, serving as a stark reminder of the risks involved in DeFi News trading. A whale's trading blunder resulted in a nearly $50 million loss, and previously, a $14 million address error occurred. DeFi News developers are working to build a more secure trading environment to prevent similar incidents from happening again.

Recent incidents in the cryptocurrency space have seen a total of $63 million lost due to on-chain operational errors, serving as a stark reminder of the risks involved in DeFi News trading. **Whale's Trading Blunder Results in Nearly $50 Million Loss** This week, a crypto whale attempting to swap $54 million USDT for AAVE tokens on a decentralized exchange (DEX) lost $49.5 million in a matter of seconds due to a poorly designed transaction structure. This was not a hack, scam, or market crash, but rather a case where the order size far exceeded available liquidity, and the DeFi News infrastructure executed the transaction according to its established rules. Reportedly, the user attempted to purchase AAVE tokens with $50 million USDT through the Aave interface. Due to the unusually large order size, the Aave interface (like most trading interfaces) warned the user of extremely high slippage risk and required confirmation via a checkbox.

Two On-Chain Incidents Cost Crypto Investors $63 Million in One Month插图
Slippage, the difference between the expected price and the actual execution price, consumed 91.6% of the transaction funds. An MEV (Miner Extractable Value) bot detected this inefficient transaction and seized the $49.5 million arbitrage opportunity before anyone could intervene. The bot's actions were entirely legitimate; it simply extracted value from a poorly executed transaction according to the established functions of the MEV infrastructure. **Previous $14 Million Address Error** Prior to this, an address error resulted in a $14 million loss. A user sent ETH to a contract address of a defunct protocol. Technically, the transaction was successfully executed, and the ETH accurately reached the contract address. However, the protocol's smart contract did not include an ETH withdrawal function, meaning the funds entered a mathematically closed environment from which they could not be withdrawn. Despite contacting the original developers, they confirmed that the code indicated the funds were permanently unrecoverable. The immutability of the blockchain, the industry's most frequently cited security feature, also became the reason why this loss could not be recovered. **Why Are Such Errors So Frequent?**
Two On-Chain Incidents Cost Crypto Investors $63 Million in One Month插图1
Both incidents point to a common problem: the design philosophy of DeFi News infrastructure is to precisely execute submitted instructions, without the friction layers common in traditional finance. Bank wire transfers include compliance checks, confirmation delays, and manual review for large transactions. DEX trades or direct wallet transfers lack these steps. While this architecture allows transactions to be completed in seconds, it also allows structurally flawed transactions to be completed in seconds, without any intermediary to intervene. There is no risk department to appeal to, no settlement window to cancel, and no counterparty to negotiate with after the fact. For small transactions, these characteristics are manageable. However, for institutional-level large transactions, where a single transaction may involve tens of millions of dollars, the lack of safeguards poses a significant operational risk. Clearly, these two incidents have not yet garnered enough attention from the industry as a whole. **Strengthening Unavoidable Safeguards** These two loss events undoubtedly add momentum to calls for stronger safeguards in the DeFi News space. DeFi News developers are working to build a more secure trading environment to prevent similar incidents from happening again.

0 comment A文章作者 M管理员
    No Comments Yet. Be the first to share what you think
Profile
Search
🇨🇳Chinese🇺🇸English