time is a flat circle ∞

Read this a couple years ago, lots of interesting nuances but TLDR was « it depends ¯\_(ツ)_/¯ »

Reminds me of my favourite book about building things in crypto from a few years ago 😄

After taking a few weeks off, I'm excited to kick off @ETHConf next week talking about what it will take to make Ethereum reasonably necessary for the world 😄 If you're around NYC next week and want to chat about this, my DMs are open 📭 See you there!

Edge City is truly special: the mix of horizon-expanding programming, thoughtful community building and A+ execution make its event some of the most unique & worthwhile I’ve attended over the years ✨ Strongly recommend checking the next California one out if you can 😄

I think you'd enjoy this talk from a few years ago 😄 piped.video/watch?v=FxBA_9dm…

Thanks for the nudge 🫡

Fusaka is going live tomorrow: more blobs, more room to scale L1 gas, and better devex 😄 The upgrade will happen at slot 13,164,544 (21:49:11 UTC). See the announcement for all the info 👇

Fusaka is ready for mainnet 🌃🎉! It will activate at slot 13,164,544, on December 3, 2025, 21:49:11 UTC. The fork introduces PeerDAS, a significant scaling milestone, as well as a slew of other EIPs. More info below 👇

Episode 2 with @0xstark and Nils Gilman starts going into the meat of things. Expect more out in the coming weeks ☀️ piped.video/watch?v=GUxwGds2…

Fusaka is coming to Ethereum's testnets 🌃 - Holesky: Oct 1st - Sepolia: Oct 14 - Hoodi: Oct 28 Read the full announcement for client release info and to learn about the update's features, including PeerDAS, L1 scaling & UX improvements 👇

Sometimes I'll google things like "yellow paper" and for a brief moment, I'm frustrated that the results page look like this 😅

PSA: the Holešky testnet will be shut down two weeks after Fusaka finalizes on it. See the full announcement below 👇

Here you go 😄 blog.ethereum.org/2025/06/19…

In June, we introduced Protocol: a new structure to align the EF around our three strategic goals — Scale L1, Scale Blobs, Improve UX — without compromising on hardness or security. Here's an update on the first track, Scale L1 👇

Ethereum's roadmap is to make the impossible inevitable. We believe in somETHing, sufficiently so to get us through the many, many impracticalities. And that's what we'll keep doing for the next 10 years. Happy Birthday, @ethereum🥳

At the protocol level, zkEVMs are a great example: they felt impossible just a few years ago, and now @eth_proofs tracks tons of teams who are getting closer and closer to real-time proving of Ethereum blocks! Onchain, we went from blockspace being used for scams, to speculation, then building an internal economy that's starting to see signs of adoptions outside of crypto. We can now seriously start designing for a world where Ethereum secures trillions! And beyond that, efforts like d/acc are aligning Ethereum's philosophy of progress with other technologies, Summer of Protocols is trying to derive a grand theory of protocols, both for crypto and beyond, and @Zuzalu_city & @JoinEdgeCity are embedding Ethereum's values (and technologies!) into literal cities 😄

So, one way to think of the roadmap going forward is this: some things that were impossible when Ethereum launched 10Y ago, that seem impractical today, will be inevitable when slot 38549829 arrives in 10 years!

And, again, DAOs are only one example of this pattern: - DeFi went from @EtherDelta to @Uniswap nearing 3T$ in total volume - Sharding shipped, as the rollup centric roadmap, now securing billions - Prediction markets went from fringe econ to mainstream - ... and The Merge 😄

But that wasn't the end of DAOs: a couple years after this incident, @MolochDAO appeard and proved that Ethereum was the place for DAOs to exist and scale. Now, they power all aspects of Ethereum and beyond, from L2s, to DeFi, public goods, and even things like @UkraineDAO

TheDAO was Ethereum's most popular app in 2016, became the largest online crowdfunding event in history, and, after it got hacked led to the most intense "messy middle" in Ethereum's history...! To put this in context: TheDAO had more ETH in it than *all L2s combined* 💀

However, this process doesn't only happen at the protocol-level: it's deeply engrained in the ecosystem. Onchain, the most notable example is DAOs. An idea that was hinted at in the 90's, formalized in the 2010's, but didn't have anywhere to exist before Ethereum.

None of this was straightforward: Ethereum took 2+ years to launch from that initial announcement, and the Beacon Chain was the result of a half-decade of R&D, including some dead ends. Between "impossible" and "inevitable", we have to go through the "impractical" 😅

From it's original announcement, Ethereum had the ambition to tackle impossible-seeming ideas: from a “modular, stateful, Turing-complete contract scripting system married to a blockchain” to building the most secure & scalable proof-of-stake system: Serenity.

TL;DR: Ethereum's roadmap is making the impossible inevitable 🗺️

We're confident that our new structure will position the @ethereumfndn to rise to the occasion. Protocol is now a more united and leaner organization with more focused teams. Here's our updated structure: protocol.ethereum.foundation…

.@etherscan ships 🚢 Asked them for a blob count column on the /blocks page: less than 12h later, it was live 🔥 etherscan.io/blocks

And, last but not least, we should use our judgement when implementing this and be open to revisit. The goal is to help provide clarity and structure, not slow down ACD with extra bureaucracy 😅

TL;DR: - Set a fork focus and orient ACD around picking headliner - Solicit community's input at key points in the process (focus/headliner selection & public devnets) - Formalize breakouts into Working Groups, ACD to provide input each fork

This doesn't mean people can't work on things that aren't "approved" by ACD. Anyone is free to do so, but this can hopefully help people spend their time on things that are aligned with the consensus direction.

Again, I propose two high-leverage tweaks: the breakouts (now Working Groups) should outline their goals in a similar way to fork headliners, and ACD should provide feedback at least each fork cycle.

For this, I propose a "barbell" approach: we should seek broad participation in setting the fork's focus & headliner, then have core devs work on implementations, and solicit input again through public community testnets with working implementations.

Practically, this means introducing a step upstream of EIP selection for the upgrades' most important features, that articulate why this is valuable, who benefits, what the risks are, etc. Shout out to @potuz_eth for already trying it out 😄

My first improvement proposal is to explicitly orient fork planning around a specific focus and headliner, welcoming input from the entire community, not just core devs.

This framing, as well as the recognition of the high opportunity cost we face, is what informed the decision to remove EOF from Fusaka. It was a process failure that it had to get there, which we need to make sure doesn't repeat itself.

Inspired by the IETF, AllCoreDevs uses "rough consensus" to make decisions. Historically, this has meant "amongst client teams", but this is an insufficient bar for such high-stakes decision. We should have consensus across the Ethereum community around major protocol changes.

In short, the most important decision ACD makes is which feature to make the "headliner" of the next hard fork: both the resource and opportunity costs are huge. If we get it wrong, it can affect the entire crypto ecosystem's trajectory.

Thank you to everyone who contributed to getting Pectra shipped securely 🦒 It’s been one of the most complex forks to scope, test and ship. Grateful for the opportunity to help shape it. Onto the next one ✨

Emmett Shear (@eshear) is live now with @tmbr_ss and @vgr on the Summer of Protocols Town Hall talking about Alignment Protocols ☀️

EOF was removed from the Fusaka network upgrade today. I've articulated my rationale for the decision in the PR to the Meta EIP: github.com/ethereum/EIPs/pul… I recommend watching the full call for context: piped.video/watch?v=M3DWaWbI…

In addition to this, Pectra introduces many other EIPs, including the long-awaited EIP-2537, which exposes BLS12-381 precompiles.

This upgrade also doubles (!) the average blob count on the network. This will help both existing and new L2s scale their Ethereum usage ASAP .oO 😄 Raising this limit was in part possible due to another EIP (7623), which bounds the worst-case block sizes on the network!

For stakers, Pectra introduces the ability to raise validators' effective balances. This means that small operators can compound their stake directly, while large ones can consolidate validators to reduce bandwidth use on the p2p network 🤖 It also removes the pre-merge PoW follow distance, shortening the delay to process validator deposits, and introduces execution-layer triggerable withdrawals, which enable more trustless staking constructions.

EIP-7702 allows standard Ethereum accounts (EOAs) to be extended with smart contract functionality, enabling use cases like transaction batching, gas sponsorship, or social recovery, all without migrating your assets 🔑

Ethereum's next network upgrade, Pectra, is coming to mainnet on May 7th, at epoch 364032 🎉 Pectra introduces EIP-7702, several improvements to validator UX, a doubling of the blob count (.oO!) and many other features! More on this below 👇

.@nayafia and @tmbr_ss are live on the Summer of Protocols YT chatting about antimemetics 🌞 piped.video/watch?v=Ze9pqaIr…

🤝

And, last but not least, once we've agreed to a path forward here, we should make sure it's well documented and clearly legible to the entire community 😄

To gather input beyond ACD, we should keep leaning into what already works (breakout rooms, recurring protocol calls), but also experiment with new formats, both synchronous and asynchronous, at different stages of the process.

Using our timeline again, ACD{E|C} would own the white boxes, and ACDT the coloured ones: