yoav.eth

[yoav.eth @yoavw]

@PTvardovsk23119 @bkiepuszewski I'm not aware of AA specific projects but isn't it a part of what light clients enable?

[yoav.eth @yoavw]

@PTvardovsk23119 @thedaofund I'm not sure what layer you mean. All verification happens inside the account, while 4337 just ensures that execution only happens after successful validation of the same UserOp. See also my reply to your other tweet.

[yoav.eth @yoavw]

I'm deeply honored, and excited to see @thedaofund taking off!

[thedao.fund @thedaofund]

With no further ado, below are the first batch of applicants that were minted badges today:
@samczsun
@yoavw
@nicht_tintin
@GNSPS
@montyly
@gf_256
@hritzdorf
@Fredrik0x
@tinchoabbate
Gustavo Grieco
@AndrewMohawk
@iphelix
@dxo1312
@SoosMate
@rv_inc
@0x11b6
@MatthiasEgli
@a_permenev
@FrankResearcher
@DanielVF
@sbetamc
@RenaudDUBOIS10
@dr_zircuit
@notdeghost
@1nf0s3cpt
@poojaranjan19
@theRaz0r
@x86NOP
@mattaereal
@palinatolmach
@k3mmio
@donnoh_eth
@auryn_macmillan

TheDAO Curators also all received an ETHSecurity Badge:
@VitalikButerin
@GriffGreen
@jbaylina
@Pol_Lanski
@pcaversaccio
@avsa
@tayvano_

[yoav.eth @yoavw]

I'm not sure what you mean by offchain verification.

Bundlers are just like block builders, picking UserOps from the mempool or other sources, and putting them onchain. The user can't make assumptions on which bundler will do it.

Paymasters are contracts called by EntryPoint and apply conditions to decide whether to pay the gas. They're fully onchain.

In 4337 all validation happens onchain - in validateUserOp and validatePaymasterUserOp.

[bartek.eth @bkiepuszewski]

Have you ever had your bank account frozen ? If you haven't, you'll never truly understand the current debate between permissionless and permissions chains. Some TradFi people want to trick you into thinking that baking TradFi rules into the low-level blockchain infra is the only way for blockchain adoption. These are the same people that were building intranets assuming the internet is too dangerous, does not protect privacy and is full of illicit use.

Anything that can be done by private, permissioned blockchains can be done more efficiently by private distributed databases. It is a fact well known for years to all IT professionals.

Public blockchains are slow, inefficient and achieving privacy there is hard. And yet this is where we will all be transacting in years to come for a very simple reason - they give guarantess that permissioned networks will never be able to give to all transacting parties. You will never be debanked holding ETH. Your trade on Uniswap will never be blocked by anyone and will always settle. TradFi orgs adopting these properties are forward looking. TradFi reimplementing existing rules on permissioned chains will fail in exactly the same way they failed in 2015. Just ask IBM, Corda/R3 and the likes

[yoav.eth @yoavw]

If you're an institution considering onchain activity, make @l2beat a part of your risk assessment. That's where you learn about the hidden trust assumptions.

[bartek.eth @bkiepuszewski]

I think people are seriously misunderstanding the role of audits. To quote the article below:

"Resolv’s smart contracts had received multiple audits from well-regarded security firms, none of which identified the privileged key vulnerability prior to the exploit"

I have no idea why anyone would think that audits should surface trust assumptions of smart contracts. Their role is to check if the implementation of whatever they are auditing is bug-free, ie the code does exactly what it is supposed to do. If the code allows a single EOA to mint tokens by design - it's fine from the perspective of auditors. This is simply not a bug, it's a feature.

What we're doing at @l2beat is exactly what auditors are not doing. We expose "features" to end users. Make them visible and transparent with constant online monitoring (because "features" can change, most contracts are not immutable). You can call them "trust assumptions", "counterparty risks", however you want. But minting by EOA is a feature. If you held USR, you simply had to trust that EOA.

If analysing trust assumptions of chains, interop, defi protocols, tokens is not (yet) part of your risk assessment, talk to us. That's exactly what we've been doing for years now

[bartek.eth @bkiepuszewski]

It's increasingly clear that L2BEAT's future is ANYBEAT. Looking for a good new name for the only trusted source of truth regarding public blockchains, not just ETH L2s. Even more needed in the AI era where virtually all news you consume are AI generated

[L2BEAT 💗 @l2beat]

The Ethereum Foundation’s new Mandate is the right document at the right time.

The core argument is very simple: self-sovereignty only counts if it's real. The commitment to CROPS (the principles that made Ethereum credible in the first place and the same principles we prioritize in our assessments) does not define a specific roadmap, it defines the values of the foundation, a cultural North Star. Whatever direction Ethereum's development takes, these principles don't get traded away.

We also value EF’s commitment to the "walkaway test" - striving to make itself less necessary over time so the protocol remains decentralized. We believe Ethereum’s strength lies in this shared commitment to an open, neutral, and resilient commons.
And we’re proud to be fellow travelers in building this machinery of freedom!

[yoav.eth @yoavw]

@khamenei_ir Promise kept

[yoav.eth @yoavw]

@khamenei_ir How's life in the bunker treating you? One day you'll hear a buzzing sound from above, then... Nothing

[sudo rm -rf --no-preserve-root / @pcaversaccio]

guys, writing _simple_ software is becoming a true lost art. We are all so fucking addicted to dependency bloated, hyper composable Frankenstein systems where every tiny diff triggers a transitive verification nightmare. Oh and we keep pretending abstraction is free. Well guess what it is fucking NOT. Every layer introduces more state, more edge cases, more undefined behaviour, and more emergent interactions that nobody really fully models. Remember: observability decreases as indirection increases. I mean, formal reasoning effectively collapses when the effective system boundary is the entire ecosystem. Oh and then you guys vibe code even more dependency stuffed software and implicitly feed it back into the same LLM, great. Can we stop this insanity for a second?

Fewer dependencies (or even better _no_ dependencies). Smaller trusted computing base. Deterministic builds. Reproducibility. Code you can actually read, reason about, and audit e2e. Simplicity is not nostalgia. It is the only thing standing between us and a fucking systemic collapse.

[yoav.eth @yoavw]

I’ve worked with Bastian for years. He’s a thoughtful, principled strategist who seeks to understand and truly cares about Ethereum’s long-term success. After years quietly solving hard problems behind the scenes, it’s great to see him step forward. Excited for what’s ahead.

[Aerugo @aerugoettinea]

I am stepping into the role of interim co-ED @ethereumfndn to continue the progress that Tomasz has made over the last year.

Tomasz brought an energy and urgency that the EF needed at a critical time, and I join the community in thanking him for his work on behalf of the Foundation and the network.

This task isn't something that I take on lightly, knowing the weight of responsibility of the role through seeing it up close for some time, but it is one that I am prepared to handle.

I've served in a management position at the EF over many years, working closely with Hsiao-Wei, Tomasz, Josh Stark, Danny Ryan, Aya, and Vitalik at different points in time. My focus has been deliberately on illegible but essential work, helping management try to make well-informed decisions, working with EF's team leads, considering budgets, articulating strategy, setting priorities, and more.

The decisions I make will be guided by a principled insistence on the properties of what we're building (censorship resistance, open source, privacy, security). These properties are what make Ethereum relevant and competitive, and they are the foundation of Ethereum's value proposition to the world and everything the world builds on it; just as Ether is the foundational store-of-value that underpins every transaction across it; and just as both are indispensable to the EF's own treasury.

The mandate of the EF is to make sure that real permissionless infrastructure, cypherpunk at its core, is what gets built. Ethereum should outlast us, and it has been our job from the beginning to make sure it is robust enough to do so. I, and the rest of the EF, will work alongside other members of the community - core protocol contributors, researchers and client implementers, auditors and whitehats, incident responders, spec authors, solo stakers and validator operators, node runners, MEV gremlins, rollup and L2 teams, bridge and interoperability integrators, UX and product builders, infra providers and tooling maintainers, educators, community organizers, forum crews, lurkers, and free software advocates, grant-givers and culture-makers, artists, memers, cypherpunks, cyberanarchists, Landian accelerationists, financepunks, femboys, soundcloud rappers, transgenders, disinformationalists, cyborgs, anons, revolutionaries, shitposters, trolls, federal lists, hypebeasts, pirates, preppers, the bros, incels - to make it last 1000 years or more.

[yoav.eth @yoavw]

Safe module integrates EIL for cross-chain operations. Kudos @heymarcopolox @candidelabs

[marc @heymarcopolox]

We lost a valued customer last year.

They needed chain abstraction. Managing Safe accounts across multiple chains, and the signing overhead was killing their UX. Every key rotation meant six separate ceremonies. Every guardian update, same thing. Their users were drowning in signatures.

They asked if we had a solution. We said no.

Not because we couldn't build it. Chain abstraction was the 2025 narrative. Everyone was shipping it. We could have done it in weeks. Feature velocity, customer win, done.

But every solution we looked at had the same problem: trusted intermediaries. Relayers you had to trust. Wrapped assets. New points of failure. For infrastructure that secures savings, checking accounts and treasuries? No.

So we told them we didn't have it. They went with someone else.

That one stung.

You second guess it. Maybe we're being too pure. Maybe we're just slow.

But the teams we work with are building neobanks. Real money, real users. If a relayer goes down, if a bridge gets hacked, it's not our problem to solve. It's their users' funds. We can't sell infrastructure we don't control.

Then EIL was announced at Devconnect.

I was skeptical at first. But I read @yoavw's post on how EIL work under the hood. L1 as source of truth. Voucher system with economic guarantees. No trusted relayers. No new intermediaries.

It clicked.

Suddenly we had a way to build chain abstraction without compromising on what matters.

So we built Safe Unified Account.

Here's what it does:
• Sign once for operations across multiple L2s (Merkle proof verification)
• Atomic cross-chain via EIL integration (L1-anchored, not trust-based)
• No bridges, no relayers, pure cryptographic verification

The flow:
1. Construct UserOps for each chain
2. Arrange in Merkle tree
3. Sign root once
4. Submit with proofs to bundlers
5. Each chain verifies independently

For atomic operations, EIL's voucher system provides economic guarantees through XLP staking/slashing. Same signed voucher that claims funds on source releases funds on destination. Guaranteed by L1, not by trust.

The module is feature complete. Audit pending. We're sharing now to get feedback before we lock it down.

I don't know if we'll get that customer back. Maybe they're happy with what they chose. Maybe the trusted relayer approach works fine for them.

But I know we can finally offer chain abstraction to the teams building on Safe without asking their users to trust what they shouldn't have to trust.

Sometimes saying no is just buying time until you can say yes the right way.

[LI.FI @lifiprotocol]

The Ethereum Interop Layer (EIL) Explained 🎙

Ethereum is pushing toward a UX that feels single-chain. Is the Ethereum Interop Layer (EIL) the missing piece?

In our latest episode, @ThewizardofPOS and @yoavw from the Ethereum Foundation break down how lessons from Account Abstraction are being extended to enable trustless multi-chain execution with the EIL.

Key timestamps:
00:00 Meet the team working on EIL at the EF
8:20 What is the Ethereum Interop Layer?
16:50 Solvers vs XLPs — the censorship risk in intents
29:05 What EIL means for bridges
32:20 EIL vs OIF: how they fit together
43:00 Mainnet timeline & how builders can get involved

[yoav.eth @yoavw]

Ethereum is Trustless. Cross-L2 interop should be as well.

And that's what EIL does: empower the wallet to transact directly on any chain without intermediaries.

[LI.FI @lifiprotocol]

What is the EIL?

The EIL focuses on trustlessness. Wallet-centric, cross-chain orchestration where the user is always in control - without the intermediaries.

But what does this mean for markets today, and how could markets look with wider adoption of the EIL?

Read more: https://t.co/6IdKpWc3iK

[bartek.eth @bkiepuszewski]

> Our job should be to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can

The market is changing but the original mission of @l2beat is the same. We will keep the projects accountable with ever-expanding scope. Today L2s, tomorrow interop and in the future, hopefully, all DeFi and token issuers

[David Hoffman @TrustlessState]

The day after Vitalik declares rollups are no longer 'centric'

@payy_link migrates to being a private L2 on Ethereum

Ethereum's network effects remain undefeated.

[Steven Goldfeder @sgoldfed]

My thoughts on Vitalik's post:
🧵

[thedao.fund @thedaofund]

TheDAO is back. BULLISH

A decade later, we’re opening a new chapter.

TheDAO Security Fund: activating 75,000+ ETH to strengthen Ethereum security.

https://t.co/VV3cH313TE

[gaudenzio @gaudenzio_eth]

While some shake hands at Davos, others bring uncomfortable truths @VitalikButerin. The World Economic Forum convenes to discuss "rebuilding trust" in institutions. Meanwhile, @yoavw, Vitalik, @ThewizardofPOS answered with The Trustless Manifesto: we shouldn't need to trust at all.

https://t.co/4nbUWSgGVe

The inconvenient reality: Every centralized system begins with good intentions. Gateways become platforms. Platforms become landlords. Landlords decide who enters and what they do.

@ethereum wasn't built to make the old system more efficient. It was built to make it obsolete.

The manifesto's message is clear:

-Self-sovereignty over delegation

-Verification over blind trust

-Code over policy

-Math over middlemen

Trustlessness costs complexity, latency, and mental effort. It buys resilience, longevity, neutrality, and freedom.

The drift is already here: Hosted RPCs as defaults. Centralized sequencing. Upgrade keys that never disappear. Cross-chain relayers acting as gatekeepers.

Decentralization doesn't die through capture, it erodes through convenience.

So yes, I'm at Davos. Not to participate in the theater of "rebuilding trust," but to remind the architects of centralized systems why we're building the alternative.
Someone has to be here as well @VitalikButerin

Some conversations need to happen in uncomfortable rooms.

The world doesn't need more efficient middlemen. It needs fewer reasons to trust them.

[bartek.eth @bkiepuszewski]

In the next few threads, I will do a deep dive into EIL - Ehtereum Interoperabiliy Layer. The protocol allows for trust-minimized cross-chain execution with many interesting use cases and it's worth building intuition around it. This is Part 1 of the explainer 🧵👇