Ethereum in 2027 is going to be almost unrecognizable. High throughput, native AA, near native privacy. Meanwhile, foundations for of a faster Ethereum and for the PQ transition are being laid. If we keep apps and users in mind as the protocol transforms, the future is bright.

Love the Quicks Slots + FOCIL pairing! Faster slots are not just a tx speed boost for UX, they also mean transactions have more chances to be included by different builders. Combine that with FOCIL and we significantly improve inclusion guarantees. 🚌

Every Ethereum user knows the pain of signing (twice 😅) a swap, waiting, price moved and it failed, trying again, more waiting, done!! ...now do it all again because the swap was just step 1 of what you wanted to do. No more waiting: time to get the ball rolling on fixing this.

The first validator consolidation on Lido Core has successfully landed 🎉 This marks the beginning of migrating ~8.4M staked ETH from the legacy Curated Module to the new CMv2.

These are BENCHMARKS - which means we are not testing something random. Worst cases for each compute scenario - so pushing clients limits. Average block post-Glamsterdam with the 200MGas will be likely still processed in ~20ms = 10 GGas/s. A lot of room left for next bumps.

I'm sad to report that the AA collab between 8130 and 8141 (Frames) broke down last week, and Base and Ethereum are now going separate ways to implement different AA standards. I want to share some reflections on this collab and on the future of the EVM. For a long time, the EVM has been a unifying force between L1 and L2s. Thanks to a standard account model (EOA) and a standard transaction type (EIP-1559), users have been able to enjoy their wallets working seamlessly across EVM chains. Similarly, a AA standard shared across L1 and L2s would ensure a consistent multi-chain UX for smart accounts, including post-quantum (PQ) accounts which we will eventually all use. As the crypto industry matures, however, L1 and L2s are starting to diverge in the values they provide and the use cases they target: - For the L1, it's all about CROPS -- censorship-and-capture resistance, open source, privacy, and security. In short, Ethereum L1 wants to be the most decentralized programmable settlement layer of the world, which is what makes it a good base layer for L2s in the first place. - For L2s, it's all about scaling, customization, and compliance -- things that commercial and enterprise use cases demand, and that the L1 does not provide. These diverging needs have pushed the shared layer -- the EVM -- to its limit, and AA proved to be the breaking point. While L1 and L2s both value core AA use cases such as gasless transactions and passkey wallets, they differ sharply in what these features must comply with: - For the L1, AA transactions must be uncensorable, private, and quantum-resistant, which call for a transaction type optimized for PQ signature aggregation and privacy protocols, and an account model that can be freely programmed and extended by developers without permissions from the chain. These needs lead to AA standards such as ERC-4337, EIP-7701, and now EIP-8141 aka Frame Transactions. - For L2s, AA transactions must work at high scale, and they must be legible such that the protocol can enforce clear rules about what kinds of accounts/transactions are permitted vs not. These needs lead to AA standards such as Tempo Transactions and now EIP-8130 by Base. With the AA collab, the authors of 8130 and 8141 tried to define a shared standard that can work for both L1 and L2s. While we identified a number of technical solutions, they all required one side or the other to compromise at least a little bit on their core goals. But ultimately, Ethereum wanted to be the best version of Ethereum, and Base wanted to be the best version of Base, and while both sides acknowledged the benefits of ecosystem interoperability, it was ultimately secondary to the need for each chain to achieve their core goals. So separate ways we went, putting the burden on wallets to deal with the fragmentation that ensues. Now, just because we ended up with fragmentation doesn't necessarily mean it was a bad outcome. If reducing fragmentation comes at the cost of homogenizing chains to the point that they fail to solve problems for the users they care about, that would not be a price worth paying. While I was initially sad that the collab did not come to a successful conclusion, I took solace in the fact that both Ethereum and Base are now free to innovate on AA to the maximal extent in accordance with their own visions, unshackled from the need to accommodate the other side. If they execute well, and if the wallet community can bridge over the fragmentation, we may well end up with the best possible UX for the end users. So where does that leave us -- the broader Ethereum community including Ethlabs -- if we want to continue pushing for a consistent UX across EVM chains? I see two paths forward: - We can establish a coordination mechanism that encompasses more stakeholders than ACD itself (where only L1 client devs have voting powers), to govern shared L1<>L2 resources such as the EVM. That way, L2s can participate in shaping the EVM, as opposed to having to accept whatever the ACD decides, or being forced to fork if they don't like the decision (such as in this case with Base). - We can accept that fragmentation of the EVM and wallet UX across L1 and L2s is inevitable due to their conflicting needs, and dedicate our resources to building wallets and applications that can abstract over the differences. Indeed, the collab was an exercise in the first path -- we invited Base, Arbitrum, and other stakeholders to directly influence how native AA shapes up for the L1. While it ultimately failed in this case, I feel a better outcome could've been achieved if we had established a dialog between both sides way earlier, as opposed to well after L1 core devs had rallied around Frames. On the other hand, I also learned from this exercise that some differences are unavoidable, and indeed it would be counterproductive to overly pursue interoperability at the cost of differentiation. In other words, we sometimes just gotta let the chains cook. For that reason, I've also become more bullish about the second path -- building wallets and applications that can speak the native transaction types of each chain, and hide the complexity from users through UX abstractions. This puts a lot of onus on the wallet/application developers of course, but on the bright side, it's also an opportunity for wallets/applications to stand out and differentiate, by competing to provide great UX across chains despite the underlying fragmentation. Ethereum is the art of staying together while remaining different. We must accept that chains will succeed by innovating, and innovations will naturally result in differences. On the other hand, we must never give up on dialogue when we can achieve interoperability without compromising core product goals. As Ethereum and crypto grow to eat the world, the push and pull between innovation and collaboration will only intensify, and it's up to all of us -- builders across L1 and L2s, applications and wallets -- to determine whether diverse innovations will split Ethereum apart, or make it thrive as one.

The US going around trying to bully Ukraine into not defending itself is just pathetic. Doubly so after the embarrassingly deferential way they have gone about the meeting with Putin (and more broadly the relationship with Russia).

I am a bit confused by the Fields medalist letter, mostly in that it's a warning but a fairly vague one, with the only clear complaint being the labs very poor practices in chasing and releasing their results. Otherwise, it's not clear what the authors would like to happen?

Ethereum cannot shorten slots today. Slot times are fixed at 12 seconds. Quick Slots (EIP-8198) fixes that. The business case is clear: faster confirmations, fresher onchain prices, and faster finality. Pay the one time cost, reduce slot times to 10 seconds then ratchet lower. With Glamsterdam scaling improvements coming online, maybe it's time to reorient the performance canon towards shorter slots. In this episode of Credible Commitments @barnabemonnot makes the case for Quick Slots inclusion in Hegotá. Full episode links below.

i did a pass of H* eip's and ended up looking something like the attached. These are just my personal views, and not Teku teams, but we've also spent some time as a team as well. Im kind of hoping we can have a shorter fork, rather than spend tons of time on all of these...

I have been working on formally verifying a consensus protocol for Ethereum, with Fable orchestrating and Astra implementing. Works well, but Astra is running out of weekly usage in less than a day at this point (100 -> 34% in ~12hrs). Any tips? Pretty much blocked on this...