Fred.⚡🤖

Our paper on timing games in backrunning transaction sending, arxiv.org/pdf/2602.22032, co-authored with @0xBrMazoRoig and Christoph Schlegel (Flashbots), has been accepted at ACM EC'26! In this paper, we look into equilibrium strategies of capturing backrunning opportunities. A🧵

As of today, BuilderNet supports prioritised updates This means propAMMs and other designs that want to prioritise some calls over others are now feasible This + Titan's announcement earlier this week mark the beginning of a new chapter in transaction execution on Ethereum with a whole new set of challenges, opportunities and unknown unknowns (definitely tighter spreads) Making this new market efficient and reducing the need to rely on trusted intermediaries will require a lot of coordination across the ecosystem As a first step, we want landing updates to be permissionless. So we're launching v0 of a registry format we hope will become an industry standard - one where builders don't need to trust the prioritised updater. We've been collaborating with other builders and DeFi teams on this behind the scenes - post coming soon. Landing updates is just the beginning, we're cooking on several related features. Some of them are predictable, some of them are not - stay tuned. Docs in next tweet

We just shared a post explaining some TEE security research we’ve been contributing Every security system has its assumptions, with TEEs that assumption includes “the guy with the glock” to protect a TEE from physical attacks. That assumption hugely varies depending on who the physical custodian is. Trusting randoms on the internet is a recipe for disaster. That’s why we are working on designs & implementation of attestation systems that go beyond attesting the enclave, and attest other properties like *where* the TEE is running or what *other software* is running on the same chip but outside the enclave

1/ “Just put it in a TEE” sounds convincing, until you ask: where is this actually running? TEE attestations can prove what code is running and on which CPU. They don’t prove where that machine is running. That missing piece is the physical-access gap. 🧵

@omw_to_the_moon @ethereum @aztecnetwork @jaosef @lisacuesta Amazing! Congrats

I am pumped to announce that, as of April, I have been working at @ethereum foundation as the EVM Dev Tooling Lead. Bittersweetly, this does mark the end of my 3 (!!) years at @aztecnetwork. Thank you to @jaosef @lisacuesta and many others for the amazing memories, offsites and the massive learning opportunity, as I pivoted from engineering to product management. I am excited for what Labs will do post Alpha launch and serving as an example for privacy products in crypto. There is a lot in store there. In my new role at the EF, I hold myself accountable for making it easier to build EVM apps. I plan to tackle: 👉 Fixing top developer pain points and working with @HardhatHQ @solidity_lang, foundry, @etherscan, other SDKs, tooling and even all core devs. And yes, I have a list of the pain points. 👉 Ensuring tooling stays up to date with latest forks (glamsterdam, hegota etc) 👉 Working with the one and only @austingriffith and his team to ensure Claude code and other LLMs can build good, secure dapps (checkout ethskills.com btw!) 👉 Outlining broader language and tooling vision, funding strategies with appropriate teams, 👉 Sunsetting not needed tools or finding other maintainers. I have serving in this role for just about a month now and there is so much cooking. You will be hearing many fun announcements and big frustrations being solved over the next few weeks. Solidity devs - if you ever encounter any problem/frustration with any tooling - do reach out. My DMs remain open! To the X algorithm - help me be the point of contact for solidity devs! I want to know your biggest issues when building on Ethereum or L2s. PS: Is it cringe to say evm/acc?

Meet 0x841: a fresh sandwich bot lurking in the dark forest--currently attacking about 1500 users per day, while going almost unnoticed. What's particularly scary: most of the victims are using private mempools and should be protected.

thank you all for your contributions <3

@not_qz This is 🔥!

Check it out here ethlocal.world

first off, Ethereum is ALIVE just shipped an @ethereum events globe 🔹160 mapped over 52 countries 🔹browsable event calendar 🔹find your city & event! Made possible with @ethereumfndn 's curation with the ethereum community page Link 🔽 thank you @gabrielchua, I feel the AGI

Ethereum and Flashbots are the most genius ideas ever The fees are baked into the mechanism And the network is more valuable as it grows So the builders can just build, never need to sell anything, it literally sells itself and auto-profits

much humbled 🙏🙏🙏 time to democratize agentic mev ⚡🤖

❤️❤️❤️ so much hard work goes on behind the scene, including saying no to a million things, in order to be proud of our security guarantees. Still an even longer road ahead

very important paper about JIT resale of certain auction designs (!!)

1/n Ahead-of-time (AOT) auctions may lead to secondary resale markets. Arbitrum's Timeboost is a live case. We study what happens when such a market actually emerges.

Excellent overview of our paper on probabilistic backrunning (arxiv.org/pdf/2602.22032) and further discussion about what can be done to avoid spam by @0xBrMazoRoig: collective.flashbots.net/t/timing-games…

Glad our MEV community is waking up to this finally, from MEV searchers running LLM contests arbing prediction markets, to our MEV data queen @sui414 ;) fyi draft flashbots r&d blogpost coming up on agentic supply chain x block building, here is a sneak peek of an old draft.

TBH this shitshow reminds me so much of those good ole' days of onchain investigations and my hobbyist mining pool shenanigan research days pre-2020. Block building has a critical role to play in improving application UX and security with ecosystem accountability and assurances in execution quality that impact the economic reality of who gets what and why. "In practice, execution outcomes on Ethereum are shaped by an ecosystem of actors operating under market forces: routers, solvers, searchers, sequencers, builders, relays, and validators—each specialized, each operating under different trust assumptions, each influencing who gets routed, who gets seen, who gets censored, who gets sandwiched, and who gets reliable execution under congestion." - Decentralized Building: Wat Do writings.flashbots.net/decentralized-… In 2026, we can and should do better, let's use our tech to go from "don't be evil" to "can't be evil", from ngmi to wagmi.

@jloganolson @mikeishiring 🤝

Very impressed with gemini pro one-shotting an enclosure for this speaker based on a few photos with calipers (even got the mounting holes aligned!)

YES! This is what I mean: - mempools going dark - networking going dark - infra providers going dark These levels of the stack need privacy solutions too!

Announcing three new tracks for our work at @ethereumfndn Protocol this year! tl;dr: - Scale (@adietrichs, @vdWijden, @raulvk) - Improve UX (@barnabemonnot, @lightclients) - Harden the L1 (@fredrik0x, @parithosh_j, @soispoke) 1/...