Thanks to our good friends at https://t.co/YwrGdN7aDG, I'm happy to announce that https://t.co/fUkjNNO5Hw is back up and running in *realtime*.
Website and API https://t.co/rPv1XNuxVT. The whole shebang! ๐ฅณ
So grateful to https://t.co/YwrGdN7aDG for their continued support.
Same in the US then.
No-one is talking about Trump, Russia, Ukraine, Musk, DOGE, Tariffs, Market Crash, or anything like that.
For sure.
Definitely real.
@CoWSwap have been a huge support to https://t.co/fUkjNNODx4 over the years.
Now they're taking that to the next level by offering grants to maintain and develop the platform:
https://t.co/6UCt6RGv2w
.NET
Python
HTML / JS
Linux sys admin
Get in touch with @middleway_eth
CoW Grants program is a proud contributor to ZeroMEV.
It is an important MEV data resource which @CoWSwap and the community has been using.
I'd consider this data resource a public good, and it is sad to see that most of the data collection infra is going to wound down.
After 3 years of publishing real-time MEV data, https://t.co/fUkjNNODx4 will continue, but serving historical data only.
The API is available here https://t.co/zqObXdtUst.
Full source code for every component of the system here https://t.co/6UCt6RGv2w.
I'm happy to announce that the full https://t.co/fUkjNNODx4 codebase is now open source.
Extractor, classifier, web server, web client and API included.
At a loose end over the hols? Follow the guide to get your very own zeromev on a single VM ๐ฒ๐.
https://t.co/6UCt6RGv2w
@orbmis@ChorusOne I warned about this pre MEV Boost. Great to see it formally presented.
PBS was never going to solve latency games. Or anything else.
Reducing MEV is the only way to reduce the problems of MEV.
A self-evident truth perpetually ignored by the MEV maximizers.
JaredFromSubway says @libevm's dashboard is the most accurate
he even said others are misleading.
so in 2023
-total MEV $270M
-tipped $180M
that's +0.3% APY to the 28M ETH staked ($61,000,000,000)
this is the "CentrAliZing FOrcE" we avoided by centralizing block builders๐คฏ๐คฆโโ๏ธ
@0xMikolaj But it isn't latency arbitrage. Yes they're reacting fast to CeX price changes, but on the DeX leg they are frontrunning .
DeX arbers set their bribes just above others on the same pair in the mempool. They have to. Therefore, it is targeted frontrunning on the DeX side.
I'm sorry this happened to you @zawarudoNFT. I'm afraid you're not alone.
Nice thread- other protections would be to transact on a fair ordered L2 like @arbitrum, or look at @CoWSwap.
These can protect you from CEX/DEX frontrunning arbs as well as sandwich attacks.
I publish Web3 guides once a week...ish.
Recently, I realized a $700+ loss trading shitcoins from a sandwich attack. REKT! ๐ฅช
Learn what Maximal Extractable Value (MEV) sandwich attacks are & how you can protect yourself against them in 2 mins.๐
1/๐งต
@0x9212ce55@TomMcLn There's no contradiction. Either sellers get rekt within their slippage (especially when slippage must be set wide in high vol) or they get reverted, which will definitely higher trading costs and possibly a worse price than their original slippage would have allowed.
"Stat arb" is not an appropriate term for frontrunning DEX users against low latency CEX feeds.
Whenever you hear "stat arb" with regards to MEV, it likely involves frontrunning.
I recommend @DeGatchi 's very informative podcast with the MEV searcher @0x9212ce55 (0xprincess). Here is some policy-relevant background info I found especially interesting:
โTo be competitive in the current block-building market you have to do sandwiching (โฆ) It basically doubles your block-building profit.โ
โI may be wrong but [I think that] the current leaders in the block-building market - except Flashbots, of course - are deeply tied with stat arb teams that are arbing CEX-es with DEX-es. So the major part of their block-builder revenues are coming from this. So not even sandwiches, but stat arb.โ
@0x9212ce55@TomMcLn You're describing a low volatility low liquidity situation, not say, ETH/USDC during a large price shock.
Slippage can actually act against the user (unlike with sandwiches) because the arber doesn't need to care if they make a user transaction revert.