In the past two days, $KOGE created a 0.0003% LP pool, which has sparked controversy.
From my personal testing, it may require around 8000 USDT for the Binance router to utilize that LP pool. The average loss per transaction is around 0.4, and some individuals may experience even lower losses.
Some people believe that the entry point for this pool is too high and that it is a pool that only allows large participants.
It is reported that the pool party did not use HOOK. So it is not the pool party that is restricting.
Moreover, at 7:58 this morning, there was a case of being 'squeezed,' where a Binance WEB3 wallet user was squeezed.
The transaction hash is:
0x5eca419a63d65b6eb438ab4a9d649188de7f321378516ddee2c2475caa57fa11
Using OKLINK, you can check that the contract interacted with at this address is the OKX WEB3 contract address.
You can search for the transaction hash using the BSC browser to find more detailed information.
fromTokenAmount represents the amount of payment tokens 214838 USDT (with USDT precision of 18, hence it is 214838).
minReturnAmount represents the minimum amount to receive, and your percentage slippage is also set based on this value. This results in a little over 1640 KOGE.
According to the transaction hash, this order received more than 2500 KOGE, which is also greater than 1640. From the order perspective, this routing is perfectly fine.
Based on the USDT/KOGE price at that time, it was possible to obtain approximately over 3300 KOGE. Thus, the issue was identified; the slippage at that time was 50%, and they did not use an EVM node. This means that this large order was essentially exposed. It would be surprising if it wasn't squeezed; as long as the tokens obtained are greater than the minReturnAmount value within the slippage tolerance range, there should be no problem. If it does not meet the slippage requirements, the transaction will fail, and USDT will not incur any losses, at most some GAS fees.