BlockBeats News, on June 8, according to the analysis of X user @litangsongyx, the reason for the loss of users who "traded KOGE/USDT for a single transaction of $47,000" this morning was that nearly 50% slippage was set and MEV protection was not turned on. The user traded $210,000 in a single transaction and eventually received $161,000 worth of KOGE, losing $47,000. Due to the user's huge trading volume, Routing splits his transaction into 3 liquidity pools: $120,000 trading volume uses the Uniswap V4 liquidity pool; $43,000 trading volume using the Uniswap V3 liquidity pool with tail number E507; The $47,000 trading volume uses the PancakeSwap liquidity pool with tail number 7057; When trading through the PancakeSwap liquidity pool with tail number 7057, the MEV bot used a $320,000 transaction to push KOGE to an extremely high level, causing the user to complete the transaction at an extremely high price. There is no problem with the PancakeSwap liquidity pool, which is only responsible for the exchange, and the slippage is determined to be routed by the order. The fromTokenAmount parameter indicates that the user wants to exchange 214838 USD for KOGE, and the minReturnAmount parameter indicates that the minimum amount of KOGE that the user wants to receive is 1640 KOGE, and the actual amount of KOGE received is 2547 KOGE, and the order routing is correct. The problem was that the slippage was too high, 214838 USD could be exchanged for about 3,300 KOGEs at the time, and since the minimum number received was 1,640 pieces, it can be assumed that the user's slippage settings were as high as nearly 50%, and MEV protection was not turned on. The user has added KOGE tokens to the ZKJ-KOGE liquidity pool to earn fees after the MEV attack.
The content is for reference only, not a solicitation or offer. No investment, tax, or legal advice provided. See Disclaimer for more risks disclosure.
Reward
like
1
Share
Comment
0/400
GRAFUNI
· 06-08 06:46
Pancakeswap a very financially dangerous instrument
Analysis: A single transaction of KOGE was squeezed with 47,000 USD as the user set a slippage of nearly 50% and did not enable MEV protection.
BlockBeats News, on June 8, according to the analysis of X user @litangsongyx, the reason for the loss of users who "traded KOGE/USDT for a single transaction of $47,000" this morning was that nearly 50% slippage was set and MEV protection was not turned on. The user traded $210,000 in a single transaction and eventually received $161,000 worth of KOGE, losing $47,000. Due to the user's huge trading volume, Routing splits his transaction into 3 liquidity pools: $120,000 trading volume uses the Uniswap V4 liquidity pool; $43,000 trading volume using the Uniswap V3 liquidity pool with tail number E507; The $47,000 trading volume uses the PancakeSwap liquidity pool with tail number 7057; When trading through the PancakeSwap liquidity pool with tail number 7057, the MEV bot used a $320,000 transaction to push KOGE to an extremely high level, causing the user to complete the transaction at an extremely high price. There is no problem with the PancakeSwap liquidity pool, which is only responsible for the exchange, and the slippage is determined to be routed by the order. The fromTokenAmount parameter indicates that the user wants to exchange 214838 USD for KOGE, and the minReturnAmount parameter indicates that the minimum amount of KOGE that the user wants to receive is 1640 KOGE, and the actual amount of KOGE received is 2547 KOGE, and the order routing is correct. The problem was that the slippage was too high, 214838 USD could be exchanged for about 3,300 KOGEs at the time, and since the minimum number received was 1,640 pieces, it can be assumed that the user's slippage settings were as high as nearly 50%, and MEV protection was not turned on. The user has added KOGE tokens to the ZKJ-KOGE liquidity pool to earn fees after the MEV attack.