Analysis: A single KOGE transaction was caught at $47000, and a user set a sliding point of nearly 50% without activating MEV protection

According to BlockBeats news, on June 8th, according to X user @ litangsongyx's analysis, the reason for the user's loss of $47000 in a single KOGE/USDT transaction this morning was due to setting a sliding point of nearly 50% and not activating MEV protection. The user had a single transaction volume of $210000 and ultimately received a KOGE worth $161000, resulting in a loss of $47000. Due to the huge transaction volume of the user, the router has split their transactions into three liquidity pools: Using Uniswap V4 liquidity pool with a trading volume of $120000; $43000 trading volume using Uniswap V3 liquidity pool with tail number E507; $47000 trading volume using PancakeSwap liquidity pool with tail number 7057; When trading through the PancakeSwap liquidity pool with tail number 7057, the MEV robot used a $320000 transaction to push KOGE to a very high level, causing the user to complete the transaction at a very high transaction price. The PancakeSwap liquidity pool has not encountered any issues. The liquidity pool is only responsible for redemption, and the determination of slippage is left to order routing. The 'from Token Amount' parameter indicates that the user wants to exchange $214838 for KOGE, while the 'minReturnAmount' parameter indicates that the minimum quantity of KOGE the user wants to receive is 1640. However, 2547 KOGE were actually received, and the order routing was not incorrect. The problem lies in setting the sliding point too high. At that time, $214838 could be exchanged for approximately 3300 KOGE. As the minimum received quantity was set to 1640, it can be inferred that the user's sliding point setting was as high as nearly 50%, and MEV protection was not enabled. The user has added KOGE tokens to the ZKJ-KOGE liquidity pool to earn fees after the MEV attack.