-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MEV bots. How this is possible? #6142
Comments
Did you mean someone can always trade before you? This is impossible. |
Not impossible my friend. If you need evidence then please check his transactions. Maybe it's because of Sunpump smart contract, I am not totally sure but this guys is making more than 1000$ per day with this technique. |
Did you mean that your account transactions have been monitored? |
it's not just my account. before asking me a question please check the transactions of the wallet that I provided. You will understand better. I guess sunpump smart contract prioritisation mechanism causes this. |
If you suspect that the problem is caused by the trading mechanism of the Sunpump contract, you can try to find their development team to understand. |
If you believe that Sunpump contract transactions have priority over other on chain transactions, this is impossible. |
Okay then, how this guy is able to do this kind of transactions? Maybe he is making request to the upcoming SR every time and get prioritised? You don't think that he is reading our mind and click the button just before us, right? :) |
Hello. I noticed that a wallet is creating a transaction just before me, both for when buying and selling. I'm sharing the screenshot and the wallet address below. I wonder how this is possible? Because of this kind of bots we are losing when buying and selling. I hope you can find a solution for this kind of issues.
You can check this account and it's transcations. If you need more info please let me know.
https://tronscan.org/#/address/TRhhAC4E163mZNpfueiizH7GAYM4H8vmyB
Clearly someone has found a way to prioritize their transactions in the mempool or something like that.
The text was updated successfully, but these errors were encountered: