-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Warning! MEV appear on BSC! #1101
Comments
https://bscscan.com/address/0x00000000066f02e61a296e9f877ea4930c1622f2 This is too disgusting, these validators should be kicked out
|
This sandwich does not hide at all, stealing money directly from users, they are the biggest threat to BSC |
you are seeing it first time it seems its happening from years and trust me no one in bsc give the fuck about it and wont do it anything i m 1000% sure, btw one other validator is nodereal |
1 similar comment
What else does bsc have about the internal operations of validators? |
This definitely will destroy BSC, strongly support kicking out these validators and punishing them. |
what is this program which you get screenshoot ? which show deatiled informations about tx |
Blocknative
ср, 5 окт. 2022 г., 13:16 Halil İbrahim ceylan ***@***.***>:
… what is this program which you get screenshoot ? which show deatiled
informations about tx
—
Reply to this email directly, view it on GitHub
<#1101 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFPCK5MXE3KUREXC3C63JG3WBVIOHANCNFSM6AAAAAAQWVXYNM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This exist many years ago and there is many other method to earn money ! ... why post it in issue from BSC FULL NODE ? Please close this project we here to find solution when problem during install FULL NODE this is not a forum here dear friend |
For every vote down are you kidding me, what if right now every body open an issue Oh there is sniper Oh there is arbitrage Oh there thsi you kdding me ? its a BSC FULL NODE issue not a forum just reflect really reflect yourself your incredible you make people and developper loosing time to solve issue ! |
avenger make possible sandwich attack |
@whoami2323 in nodereal only one tx sender is allowed within one bundle) it is make impossible sandwich attack |
nodereal is OK, their service no longer helps sandwich. |
someone is running this type of transaction on my wallet to steal my stalk token, how can i stop him |
lol u might need to upgrade your programming capability its possible to send buy and sale transactions from 2 different address in same bundle and like buy from 1st send tokens to 2nd , sale tokens from 2nd and do sandwich i hope you get my point , so its 1000% possible |
It's absolutely disgusting that these validators are pulling such dirty tricks and getting away with it . MEV on a decentralized chain like ETH is understandable + everyone has a chance of doing it , but what's going on here is basically a few validators abusing their power for self benefict (for example some of these validators are doing arbitrage and destroying their competition in a very unfair way) and going against the basic principles of the chain. If Binance doesn't do anything about these occurrences there's no reason for BSC to be . Guess this goes a long way in showing the kind of corruption going on in the backstages of crypto ... |
sorry to rekindling this age old topic, just want to inquire @ctanbern @greyireland, may I know how can I check that this tx is never in public mempool? |
Validator: Avengers
Validator: Alps
Validator: BNB48 Club
This validators provide closed access to MEV. What is contrary to the principles of the network.
Same adress run several mev bots on ETH main network. https://etherscan.io/address/0x38563699560e4512c7574c8cc5cf89fd43923bca
https://bscscan.com/tx/0x0302b02863b497d8bc0d081b8e5572ceb5c181b942e1cbd49e4248fa4e7445e0
![chrome_UkkskaKnJM](https://user-images.githubusercontent.com/22947189/192512116-8e35ed53-88e5-4929-bf8f-b1c3976b6a66.png)
This tx is example. Its never was in public mempool. Anyone can check this.
This tx appear ONLY when confirmied. Since this adress use ONLY this validators list, we have understand whats goin on.
https://bscscan.com/tx/0xf28c8790840d9dbcf627b290548a20dc4f7448a655218e835d303372694f59d8
https://bscscan.com/tx/0x6d9843999f569b06b00d93ded39d102404cfa1592dd37892069ee87f48d047e6
The text was updated successfully, but these errors were encountered: