The MEV supply chain on Ethereum is ripe for disruption because of a lack of robust financial incentives. There are a handful of solutions to the MEV problem being worked on for implementation in 2023.
Before I get too deep in the weeds about how MEV is extracted on-chain post-Merge, it's worth revisiting the basics of what MEV is and why it exists in the first place. For this, I recommend reading Part 1 of the @glxyresearch MEV series as a refresher:
@glxyresearch@ChainsightLabs Third-party builders and relays are new entities in the MEV landscape of Ethereum made possible because of the advent of MEV-Boost software, as well as the open-sourcing of both builder and relay code by the Flashbots team.
@glxyresearch@ChainsightLabs Diving deeper into the competitive dynamics of builders, several builders like Flashbots also operate their own MEV relays, and this despite there being little to no financial incentives for businesses to run their own relays.
@glxyresearch@ChainsightLabs As background, relays are the off-chain marketplaces where builders participate in a blind auction to sell their blocks to validators. Most operators do not earn a revenue from their relay operations.
The costs of operating a relay can differ drastically depending on how performant a relay is. For example, relays that are permissionless, opening themselves up to more builders, and therefore, potentially more profitable MEV blocks, need to protect against DoS and spam.
In addition, performant relays that try to minimize the amount of latency when sending blocks to validators on Ethereum must set up multiple servers that can handle variable load conditions and maintain a high bandwidth network.
Based on the costs of running a performant relay that competes with the Flashbots relay, which is operated at zero cost to users, there does not appear to be strong incentives for relay operators to build and maintain performant relays over the long-run.
Competition between relays, much like the competition between builders (which are themselves searchers to an extent), may decline over time and result in centralization.
Ethereum core developers and the Flashbots team view relay censorship as a short-term issue because, even if relay diversification does not improve, there is a plan to remove relays entirely from the MEV supply chain through enshrined PBS.
Only the roadmap to implementing enshrined PBS on Ethereum remains unclear. One of the core challenges of PBS is designing a way to facilitate block auctions in a decentralized way.
In contrast to enshrined PBS, Ethereum developers are considering another possible framework for enabling block auctions in-protocol called protocol-enforced proposer commitments (PEPC).
@bertcmiller In addition there are alternative network-level solutions like the shutterized beacon chain concept that is being spearheaded by the Gnosis team and may see an early implementation on the Gnosis Chain later this year.
@bertcmiller@koeppelmann Outside of relay censorship, there is a concern that block building will become centralized to a few specialized entities.
@bertcmiller@koeppelmann There is ongoing research on how to redesign the core responsibilities of a builder such that multiple builders collaborate to create a single block. Flashbots is actively working on a solution to decentralize the role of block builders through collaborative block building.
@bertcmiller@koeppelmann But today the technical details around how their solution, SUAVE, will work are scant and still actively being researched.
(Head to the Flashbots discussion forums if you want to get involved with that research!)
@bertcmiller@koeppelmann Closely intertwined with the research highlighted above on mitigating relay and builder centralization, developers are monitoring and discussing solutions for several other areas of MEV such as:
- programmable privacy
- user MEV kickbacks
- cross chain MEV
@bertcmiller@koeppelmann MEV-Boost has enabled the early beginnings of a more decentralized MEV supply chain, where several different entities can participate as a searcher, builder, validator, or relay.
@bertcmiller@koeppelmann However, due to the lack of robust incentives to encourage competition among searchers, builders, and relays, there is a concern that the MEV supply chain becomes dominated by a few knowledgeable stakeholders over the long-term.
@bertcmiller@koeppelmann While Flashbots is spearheading a large portion of the work towards solving the negative externalities of MEV on Ethereum, the open sourcing of MEV infrastructure since the Merge is envisioned to diversify the number of stakeholders involved in solving these issues.
@bertcmiller@koeppelmann Special thanks to the many wonderful people in the Ethereum ecosystem that helped me with my research for this report, some who are already tagged in this thread, and others like @EigenPhi@bloXrouteLabs@sreeramkannan! 🌟
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The first public Shanghai testnet dubbed Zhejiang was launched yesterday. Developers plan on activating the Shanghai upgrade on Zhejiang next Tuesday, February 7.
Assuming Shanghai goes smoothly on Zhejiang next week, developers will decide on an activation date to release the upgrade on the Sepolia testnet during the next ACDC call on Thursday, February 9.
Ethereum developers are targeting March 2023 for the activation of Shanghai and staked ETH withdrawals. In my latest report, I give a detailed overview of how staked ETH withdrawals will be enabled on Ethereum. Here's the tldr🧵
@kellyjgreer All validators wanting to withdraw their staking rewards will have to ensure their withdrawal credentials are updated to the new “0x01” format. This is also a requirement for validators who want to exit, stop validating, and withdraw the full balance of their staked ETH.
@kellyjgreer According to @benjaminion_xyz, an Ethereum core developer and product lead for CL client Teku, there is roughly 302,154 validators with 0x00 credentials, and 186,722 with 0x01 credentials on the Beacon Chain.
After a two-week hiatus, Ethereum devs reconvened for the first ACD call of 2023. They discussed planning around Shanghai and most notably, they agreed to punt EOF implementation from the upgrade.
The main rationale for removing EOF from Shanghai was two-fold. First, it was clear that testing for the code changes would likely delay the upgrade by roughly a month. In addition, developers expressed concern about the permanence of changes to the EVM as result of EOF.
“In the EVM it’s much harder to remove things than it is to remove other features,” said @VitalikButerin, adding, “You have applications that are written in EVM code and if the EVM changes, then those applications can’t change."
Ethereum devs agreed on the scope of Shanghai today. It’s going to be:
- staked ETH withdrawals
- big EOF implementation
- warm coinbase
- push0
- limit and meter initcode
- time based EL forking
- getpayloadV2 and getpayloadbodiesbyrange
Other than the first bullet, every other code change could be removed from Shanghai if devs think it would significantly delay a March 2023 activation date.
Devs will be back Jan 5 to discuss the readiness of client implementations for Shanghai. Stay tuned for my full write up of today’s call, which will be published tomorrow on Galaxy.com 💫
I have for you today not one, but TWO writeups of the latest Ethereum dev calls. As you know, I had skipped writing one for last week and that call ended up being very material to Shanghai planning.
Yesterday, on the 2nd anniversary of the Beacon Chain, devs had a call focused on discussing improvements to the consensus layer (CL) specifications of Ethereum.
On the call, @dannyryan reaffirmed the devs' decision to work on enabling staked ETH withdrawals for Shanghai separately from their work on proto-danksharding (EIP 4844). EIP 4844 will now likely be activated in a separate upgrade after Shanghai.