EF Treasury Defipunk submission form for the projects that would like to participate:

Privacy is normal, and writing code is not a crime.

The EF is donating $500K to the legal defense of Roman Storm, and we will match up to a further $750K in donations from the community. Privacy is normal, and writing code is not a crime.

We're excited to be cohosting d/acc Berlin this year with @VitalikButerin We've got an action-packed day tomorrow starting with a keynote by @julianzawist followed by @tkstanczak and @koeppelmannn Join us tomorrow 👇

You can't spell DeFi without EF 🚀🚀🚀

EF treasury policy, key highlights:

Announcing the Ethereum Foundation Treasury Policy

Today, we released the Ethereum Foundation Treasury Policy. It outlines our approach to macroeconomics, the management of crypto and fiat-denominated assets, and reflects our commitment to transparency and cypherpunk values. [wow it's a thread 🧶]

d/acc Discovery Day is coming to Berlin! Join us on June 11, 2025, at silent green for talks, panels, and discussions on decentralization, defense, and democracy in tech. Led by @VitalikButerin , co-hosted by @OctantApp

censorship resistance, security, privacy are fundamental properties of Ethereum, they apply to short term goals, long term goals, architecture, everything goals and directions are always built on top of these fundamentals

Tectonic Shifts are happening in Ethereum Public Goods Funding. 2025-2027 will look way different than 2022-2024! things that are changing: - roadmap updates in the Ethereum ecosystem - changes at the EF - new funding sources, old funding sources drying up - new AI tech - new

The Ethereum Foundation's R&D team structure update: We're hopeful that this new structure will empower our internal teams to focus more clearly and drive key initiatives forward. Today, we also had to make some incredibly difficult decisions. Saying goodbye to talented and

@0xprivacypools You should join my crusade to make the official pronunciation of the letter W "dub" Every letter deserves a one-syllable name, W is today the sore exception. "dub" not sounding like w is fine, after all "aych" doesn't contain a h sound. (if we wanna fix that we could do "he"

@ameensol @AnettRolikova @TheRealKartik @ETHGlobal @ethereum @0xprivacypools my comment on UX was specifically about zk-snark UX I actually think @0xprivacypools UX is quite good! Of course it's far from what is needed for mass adoption, but it's at least as easy as @safe. Whereas on the devex side, @safe is still waaay easier than anything ZK (eg.

big name for a smol pool thank you for your trust @VitalikButerin priv/acc needs to start putting their money where their mouth is come on over and help fill this baby up

We’ve made a huge effort to change the existing paradigm against strong headwinds, but we’re getting there! @AragonProject roadmap based on @VitalikButerin 3 suggestions below: “Multi-level structures” ✅ Privacy with @zkMACI ⏳ AI ⏳ For multi-level structures you can

The @ethereumfndn has staked 50,000 $RAIL. The EF can now take part in RAILGUN governance and claim active governor rewards from protocol fees. RAILGUN is and always will be a technology aligned with Ethereum values.

Nordics are walking back the cashless society initiative because their centralized implementation of the concept is too fragile. Cash turns out necessary as a backup. Ethereum needs to be resilient enough, and private enough, to be able to credibly play this kind of role. https://t.co/WDZxk7Cnxf

A fun math aside, on the idea of splitting a large zk proving workload between multiple provers. Suppose you have N provers, and you have a proving workload that you split into N parts (so, one part per prover). You require provers to pre-register, but registration is open-access. Suppose you have a constant fault rate (eg. 1/5 of registered provers fail). Provers expect to complete in one round (eg. 3s). If one prover fails, other provers have to come in and re-prove that load. How many rounds does it take for the entire workload to get proven? Answer: log*(N) (yes, that's the iterated-log function) Why: In the first round, you go from N unproven workloads to N/5 unproven workloads In the second round, each remaining workload gets assigned 5 provers, so per-workload failure rate becomes 1 in 5^5. So you go to N / 5 / 5^5 unproven workloads In the third round, each remaining workload gets assigned ~5^5 provers, so failure rate is 1 in 5^(5^5). So you go to N / 5 / 5^5 / 5^(5^5) unproven workloads

The work of teams like MACI, also and others, is important. Along with privacy in finance and privacy in comms, we need privacy in governance. (In fact, we need the former two in part because finance and comms *are* governance)

IMO UN resolution votes should be secret ballot. Each country can choose (and replace) their own representative, but once the choice is made, what the representative does is up to their own conscience. Less "pressuring" by great powers, more seeing how people really think.

@zengjiajun_eth 1. This is average case, not worst case. We need real-time worst case for safe L1 use 2. Not formally verified 3. ~100 kW to prove. Proving is a 1-of-n trust model, but even still, perhaps we want proving doable at home (~10 kW) 4. We wanna 10-100x the L1 gaslimit So, truly

Real-Time Ethereum Proving is here. INTRODUCING: SP1 Hypercube

The novel thing we are doing is in the peer to peer network, the novel thing is in the principles, the thing that build a trillion dollar asset class is the soul, the attempt to do new things better

Ethereum will not abandon self sovereignty to take scaling shortcuts, this is what sets it apart.

以太坊跑不跑得起，已不是技術問題，而是階級問題？ 當以太坊持續尋找擴展主網效能的路時，有一個經常被忽略、但至關重要的問題浮上檯面：一般散戶還能自己跑節點嗎？ Vitalik 在 Ethereum Research 發表的新文，就聚焦在這點，「怎麼讓普通人，依然能跑得起節點？」

How to make Ethereum L1 scaling more friendly to users running local nodes for personal use:

Welcome to the stage 1 gang @Starknet!

we've hosted 4 distilled human judgment challenges on @PondGNN ever since vitalik wrote "AI as the engine, humans as the steering wheel" back in Feb David has been a star participant in these contests so i read his writeup with curiosity as the first empirical results on the

How can Ethereum fund the infrastructure it relies on? → Surfacing what matters • What principles, outcomes, or metrics should guide how funds are allocated? • What principles, outcomes, or metrics should guide how funds are allocated? • What does the ecosystem value? → A

just wrote up a monster post with @sejal_rekhan around how ethereums ecosystem can become self-sufficient & circular Some of these ideas have sat in my head for ages & grateful to Sejal for making the push to comprehensively write up an entire roadmap here's a 5 point TL;DR 1.

EVM DevEx is one of @Ethereum's strongest moats. {solx} is a chance to bring it to the next level via: 1) Faster language evolution 2) Eliminating the need for inline assembly 3) Solidity-to-RISC-V compilation 4) World-class LLVM tooling (e.g. VS Code debuggers)

upgrade in progress . . . activating Pectra @ epoch 364032 // 10:05:11 UTC

Hi @VitalikButerin @ethereumJoseph :)

A good reminder that stage 2 is not the only thing that matters for security: the quality of the underlying proof system matters too.

Privacy was always the true alpha.

Complexity is the bridge to simplicity. It always has been. Ethereum _overall_ is bloated, in its current form, with complexity (this goes beyond the L1 itself; just look at smart contract codebases these days...). So it's time to bridge over to simplicity. Agreed. Look, IMHO,

Simplifying the L1

The Future of Bitcoin & Ethereum with @VitalikButerin (Bitcoin Takeover Podcast S16 E24)