The EF mandate reminds us that protocol design choices shape decentralization:
“If Ethereum supports only a narrow set of account types… those use cases that require smart accounts can only be served through intermediaries.”
Protocol limitations create centralization pressure.
Expanding native account capabilities (eg. EIP-8141) helps ensure advanced UX inherits Ethereum’s CROPS guarantees instead of relying on trusted middleware.
EIP-8141 (link below)👇
Today, the Foundation’s Board released the EF Mandate.
This document, which was first intended for EF members, reaffirms the promise of Ethereum, and the role of EF within this ecosystem.
good to be working with you all on this from Account Interface.
same Access Layer cluster. App Enablement and Account Interface are both focused on the places where protocol guarantees can quietly disappear.
making the self-sovereign path the default one is our shared mission.
CSL @CharlieStLouis Nov 16 Article Ethereum’s Guarantees Shouldn’t Stop at the Protocol Ethereum’s guarantees don’t automatically carry through to the applications and infrastructure people use. And I think that deserves more attention as the ecosystem grows. Following some conversations
a list of all 69 participating orgs:
* 3mi labs
* aarhus university
* aria
* axiom
* aztec foundation
* bar-ilan university
* binius
* blockstream
* carnegie mellon university
* category labs
* cnrs
* complutense university of madrid
* consensys
* epfl
* elte / university of birmingham
* etherealize
* ethereum foundation
* ethlabs
* ideal
* imperial college london
* inria
* ku leuven
* lambdaclass
* ledger
* lfg labs
* lirmm / university of montpellier
* math, inc.
* mavan / bitmine
* microsoft research
* miden
* mit / nyu
* nethermind
* nvidia
* nyx foundation
* offchain labs (prysm)
* onetimelabs
* pauli group
* powdr labs
* project eleven
* ream
* riva labs
* seoul national university
* shielded labs
* silence laboratories
* stellar development foundation
* succinct
* symbolic software
* tachyon foundation
* technical university of munich
* technion
* tel aviv university
* trail of bits
* uc san diego
* universite de rouen normandie
* university of cambridge
* university of luxembourg / layerzero labs
* university of minnesota
* university of pennsylvania
* university of warwick
* veridise
* world foundation
* xi'an jiaotong-liverpool university
* zcash
* zero latency labs
* zisk
* zksecurity
* zodl
* a16z
* 20squares
* zero knowledge podcast
thank you all for taking time away from your lives to come and share your brilliance with us
hey TORN holders - 2ish more days to vote FOR on proposal #71 and get new 0.01, 0.03, 0.3, 3, 30 ETH tornado cash pools on ethereum mainnet (exact clones of existing ETH pools)
without a push of new FOR votes it is on track to being defeated
tornadocash.eth.limo/governa…
The September all-Protocol update is out. Glamsterdam heads to Sepolia on Oct 6, both Hegotá headliners are on devnets, and the PQ roadmap is taking concrete shape. Plus faster block propagation and autoresearch. Highlights in the thread below. 👇
today EF Protocol published two posts. we hope you check them out!
for me, they mark the end of a transition that started back in april. when @kevaundray, @0xfredrik, and i stepped into the cluster coordinator roles, the job within the job was cluster-wide alignment: shaping a strategy born from our imperative (concentrate Protocol on what only Protocol can and will do), grounded in CROPS, and aimed at what Ethereum needs right now to endure for 1,000 years.
1️⃣ the first post makes that strategy public: a quantum-resistant ethereum L1 by december 2029, the multi-fork plan to get there, and what each of our five research arcs needs from the upcoming forks.
2️⃣ the second post is our first unified hardfork opinion: grades from every team in the cluster, argued down to one tier list covering every EIP proposed for hegotá, with the reasoning behind every grade.
read the priorities first. the tier list is those priorities applied.
lastly, Protocol is hosting a Reddit AMA on r/ethereum, sept 16 at 2pm UTC. hope to see you there. question form in the next post. 👇
The Protocol Cluster has published two new posts:
Hegotá EIP Opinion Post and Tier List evaluates and grades all 62 EIPs proposed for Hegotá, providing the cluster’s first unified tier list for a network upgrade
Current and Emerging Priorities covers commitments and research arcs, anchored on a quantum-resistant Ethereum L1 by Dec. 2029
Offered as one input to Hegotá scoping, roughly 60 researchers, engineers, and individual domain experts across all 9 teams in the Protocol Cluster contributed to the Hegotá tier list, providing 397 tier grades before discussing contested items live.
The plan, commitments, and shared set of cluster-wide priorities covered in the companion post provide the context behind the final tier grades.
The Protocol cluster will host a Reddit AMA on r/ethereum on September 16 at 2pm UTC to talk through these priorities, the Hegotá tier list, and anything else on your mind.
→ Submit questions ahead of time here: pad.ethereum.org/form/#/2/fo…
Read the articles here:
→ EF Protocol - Current and Emerging Priorities: blog.ethereum.org/2026/09/07…
→ EF Protocol - The Hegotá EIP Opinion Post and Tier List: blog.ethereum.org/2026/09/07…
Will Corcoran @corcoranwill Aug 28 Article Glamsterdam Retro / Hegotá Prep How do you synthesize 60 points of view, across one of the most intellectually dense and diverse organizations in tech (let alone crypto), into a single EIP tier list + fork-planning post? We're about
AA update: The Frame Transactions EIP was moved today to Scheduled status for the Hegotá upgrade. It was proposed as a headliner and moved in March of this year to Considered status. There was strong consensus that it was important to ship Account Abstraction in Hegotá even if the specific implementation was still up for debate.
There's been a lot of progress in the past few weeks as another implementation, EIP-8130, became a contender. This EIP is scheduled to be shipped on @base in September. It spurred productive conversation async and in a breakout this past Tuesday about the best way to not fracture standards across the ecosystem by shipping two incompatible Account Abstraction implementations between the L1 and L2s.
The crux of the issue is arriving at a shared transaction type that both preserves flexibility and future-proofness for the L1 and allows L2s to statically analyze transactions for performance and DoS-resistance reasons. At a minimum, we should make sure that the AA scheme we adopt for the L1 is flexible enough that 8130, or any future account system, can be built on top of it so that from the user's perspective the same account can work across L1 and L2s.
Authors of both EIPs, core devs, researchers, and testing teams have been working toward a solution that respects the imperative to get Account Abstraction in the next fork without delay but avoids fracturing ecosystem standards.
That said - Account Abstraction _will_ ship in Hegotá, so core devs decided today to move EIP-8141 from Considered to Scheduled today. This was made with the caveat that the version of Account Abstraction that ships in Hegotá may significantly change from what's on the Hegotá Meta EIP right now: potentially the EIP number, the transaction type, etc.
The move to Scheduled doesn't materially change the conversation that's been happening over the past few weeks or enshrine the current spec. When an EIP is proposed as a headliner and moved to Scheduled, it just signals an intention to make the fork schedule dependent on that feature being shipped. It's more common than not for the implementation to change significantly between being Scheduled and shipping.
Big appreciation to @_chunter of @base, @Offchain, @EthLabs_org, and client teams for moving the conversation forward. Progress is ongoing and can be followed at the AA breakouts on Tuesdays at 14:00 UTC or asynchronously on Forkcast.