Odaily Planet Daily News According to X user @litangsongyx analysis, this morning "KOGE/USDT transaction was squeezed by $47,000". The user's loss was due to setting a nearly 50% slippage and not enabling MEV protection. The user's single transaction amount was $210,000, ultimately receiving $161,000 worth of KOGE, resulting in a loss of $47,000. Due to the user's large transaction volume, the routing split the transaction into three liquidity pools: a $120,000 transaction used the Uniswap V4 liquidity pool; a $43,000 transaction used the Uniswap V3 liquidity pool with the last digits E507; a $47,000 transaction used the PancakeSwap liquidity pool with the last digits 7057. When the transaction went through the PancakeSwap liquidity pool with last digits 7057, an MEV bot used a $320,000 transaction to push KOGE to an extremely high level, causing the user to complete the transaction at a very high price. The PancakeSwap liquidity pool did not have any issues; the liquidity pool was only responsible for the exchange, while the slippage judgment was left to order routing. The fromTokenAmount parameter indicates that the user wanted to exchange $214,838 for KOGE, while the minReturnAmount parameter indicates that the user wanted to receive a minimum of 1,640 KOGE. The user actually received 2,547 KOGE, and the order routing was also not incorrect. The problem lies in the excessively high slippage; $214,838 could have been exchanged for about 3,300 KOGE at that time, and due to the minimum received amount being set at 1,640, it can be inferred that the user set the slippage as high as nearly 50% and did not enable MEV protection. After the MEV attack, the user has added KOGE tokens to the ZKJ-KOGE liquidity pool to earn fees. Additionally, according to on-chain data analyst @ai_9684xtpa, this transaction being squeezed is not an issue from either Binance or OKX DEX.

#USDT