Butta.eth

“Ethereum is a product/Ethereum is not a product” is a strawman imo. More important to me is how to make Ethereum development more user- and product-centric, for both protocol and non-protocol development. For one, the protocol has a roadmap, so product thinking applies here too. Ethereum is also a platform, this is a viewpoint adapted to thinking about the services it provides, for the users (maybe infra) of these services. And thinking of it as a product also helps convey that work needs to happen on the adoption of its affordances. Shipping MaxEB does not automatically consolidate validators. Shipping native AA does not automatically transform Ethereum accounts into superior accounts. From my corner of the world, three places where product thinking are currently benefiting development and adoption: - @corcoranwill and @_julianma are coordinating a strong outreach to possible users of the Fast Confirmation Rule, a rule derived from validator votes in the current protocol that provides strong guarantees of confirmation, towards faster user deposits and withdrawals in and out of L2s or other offchain services. - @benjaminion_xyz is working to tailor the R&D, features and delivery of fast finality to the needs of its users and suppliers (validators). Get in touch! - Our current interop work has benefited from multiple conversations with wallets, chains and users, with our efforts currently directed towards the interop-sdk developed with @Wonderland (see interoperable addresses in action here: interopaddress.com and the recent exciting news of the on.eth chain registration contract: x.com/rudolf6_/statu… + h/t to the @unruggable_eth folks) and the Open Intents Framework developed with @OpenZeppelin and many others. A final hat tip to @Butta_eth moving mountains to get more validators consolidated, a critical step towards faster finality x.com/trent_vanepps/… There’s a lot more to build!

@vdWijden 🥰

Didn't even manage to make it the whole weekend, but it was very healing! Now I'm back and more bullish than ever. Ethereum needs to stand for something and I want to be part of it. Part of something that matters, that cuts through the bullshit and slop, that empowers humans in

@JSeyff LFG

NEW: BlackRock is launching their Ethereum Staking ETF today -- $ETHB. It will have the same fee as $ETHA at 0.25% bps but has a fee waiver down to 0.12% for the first year or first $2.5 billion in assets.

Vibe coders can now easily build their own dashboard, overview, and insights 😎

Sorry to hear that, but depending on what you're for, that might be the right call. beaconcha.in only looks at on-chain data. By that measure, @LidoFinance landed in the middle and @Figment_io came out on top. The goal is to be as neutral as possible by relying on onchain data that anyone can reproduce, but I’m open to feedback if you think the BeaconScore metric could be improved. (docs.beaconcha.in/validator-dash…) We've added docs so it's easy to vibe code the next version. Do you wanna give it a try? 👀 docs.beaconcha.in/use-cases/enti…

@beaconcha_in @LidoFinance @binance @ether_fi @coinbase @Figment_io @krakenfx i hate it, it just feels so disingenuous. Anyone who didn't know is going to look at that chart and conclude that lido staking is best and rocket pool staking is worst. It needs real context to understand how those providers are different.

🏆 Ethereum Staking Leaderboard Network BeaconScore (30d): 99.2621% Top performers vs avg: 🟢 @Figment_io — 99.6494% (+0.39pp) 🟢 @everstake_pool — 99.6268% (+0.36pp) 🟢 @krakenfx — 99.5849% (+0.32pp) 🟢 @Kiln_finance — 99.5805% (+0.32pp) Thread covers BeaconScore breakdown, APY, and missed rewards 🧵

awesome dashboard from @Butta_eth! after a slow start in 2025, usage of MaxEB / 0x02 withdrawal / "accumulating validators" is over 20% dune.com/butta_ethereum…

Still on our V1 API? Here's why V2 is worth the switch: 👉 All new features ship on V2 only 👉Query by index, pubkey, deposit address, withdrawal address, entity, or dashboard 👉 Cursor-based pagination for cleaner data flows Migration guide in next tweet 👇

1/ We surveyed 21 stakeholders across 16 major DeFi & protocol teams on Ethereum's gas repricing meta EIP-8007 Here's what builders actually think about each proposal👇

Beaconcha.in continues to be one of the most valuable assets in the Ethereum ecosystem. ♥️

Our Website has a new look and organization We have updated our website with a new design and a restructured navigation system. The site is now organized into a search-first landing page and four primary pillars: API, Monitoring, Explorer, and Resources 🎨

AI agents need privacy, and Ethereum can provide it. Here’s a clip of two autonomous agents discovering each other, generating stealth addresses, and interacting privately on Ethereum. More details in the 🧵👇

Guide on how to setup AndyClaw:

Introducing strawmap, a strawman roadmap by EF Protocol. Believe in something. Believe in an Ethereum strawmap. Who is this for? The document, available at strawmap[.]org, is intended for advanced readers. It is a dense and technical resource primarily for researchers, developers, and participants in Ethereum governance. Visit ethereum[.]org/roadmap for more introductory material. Accessible explainers unpacking the strawmap will follow soon™. What is the strawmap? The strawmap is an invitation to view L1 protocol upgrades through a holistic lens. By placing proposals on a single visual it provides a unified perspective on Ethereum L1 ambitions. The time horizon spans years, extending beyond the immediate focus of All Core Devs (ACD) and forkcast[.]org which typically cover only the next couple of forks. What are some of the highlights? The strawmap features five simple north stars, presented as black boxes on the right: → fast L1: fast UX, via short slots and finality in seconds → gigagas L1: 1 gigagas/sec (10K TPS), via zkEVMs and real-time proving → teragas L2: 1 gigabyte/sec (10M TPS), via data availability sampling → post quantum L1: durable cryptography, via hash-based schemes → private L1: first-class privacy, via shielded ETH transfers What is the origin story? The strawman roadmap originated as a discussion starter at an EF workshop in Jan 2026, partly motivated by a desire to integrate lean Ethereum with shorter-term initiatives. Upgrade dependencies and fork constraints became particularly effective at surfacing valuable discussion topics. The strawman is now shared publicly in a spirit of proactive transparency and accelerationism. Why the "strawmap" name? "Strawmap" is a portmanteau of "strawman" and "roadmap". The strawman qualifier is deliberate for two reasons: 1. It acknowledges the limits of drafting a roadmap in a highly decentralized ecosystem. An "official" roadmap reflecting all Ethereum stakeholders is effectively impossible. Rough consensus is fundamentally an emergent, continuous, and inherent uncertain process. 2. It underscores the document's status as a work-in-progress. Although it originated within the EF Protocol cluster, there are competing views held among its 100 members, not to mention a rich diversity of non-EFer views. The strawmap is not a prediction. It is an accelerationist coordination tool, sketching one reasonably coherent path among millions of possible outcomes. What is the strawmap time frame? The strawmap focuses on forks extending through the end of the decade. It outlines seven forks by 2029 based on a rough cadence of one fork every six months. While grounded in current expectations, these timelines should be treated with healthy skepticism. The current draft assumes human-first development. AI-driven development and formal verification could significantly compress schedules. What do the letters on top represent? The strawmap is organized as a timeline, with forks progressing from left to right. Consensus layer forks follow a star-based naming scheme with incrementing first letters: Altair, Bellatrix, Capella, Deneb, Electra, Fulu, etc. Upcoming forks such as Glamsterdam and Hegotá have finalized names. Other forks, like I* and J*, have placeholder names (with I* pronounced "I star"). What do the colors and arrows represent? Upgrades are grouped into three color-coded horizontal layers: consensus (CL), data (DL), execution (EL). Dark boxes denote headliners (see below), grey boxes indicate offchain upgrades, and black boxes represent north stars. An explanatory legend appears at the bottom. Within each layer, upgrades are further organized by theme and sub-theme. Arrows signal hard technical dependencies or natural upgrade progressions. Underlined text in boxes links to relevant EIPs and write-ups. What are headliners? Headliners are particularly prominent and ambitious upgrades. To maintain a fast fork cadence, the modern ACD process limits itself to one consensus and one execution headliner per fork. For example, in Glamsterdam, these headliners are ePBS and BALs, respectively. (L* is an exceptional fork, displaying two headliners tied to the bigger lean consensus fork. Lean consensus landing in L* would be a fateful coincidence.) Will the strawmap evolve? Yes, the strawmap is a living and malleable document. It will evolve alongside community feedback, R&D advancements, and governance. Expect at least quarterly updates, with the latest revision date noted on the document. Can I share feedback? Yes, feedback is actively encouraged. The EF Protocol strawmap is maintained by the EF Architecture team: @adietrichs, @barnabemonnot, @fradamt, @drakefjustin. Each has open DMs and can be reached at first.name@ethereum[.]org. General inquiries can be sent to strawmap@ethereum[.]org.

New updates to our v2 API 🥳 We've rolled out new endpoints to give you deeper insights into network state, entity performance, and validator duty history.

📣 Fill in the gas repricing survey x.com/EFprotocol/sta… (1/2)

1/ The Ethereum Foundation has begun staking a portion of its treasury, in line with its Treasury Policy announced last year. Today, the EF made a 2016 ETH deposit. Approximately 70,000 ETH will be staked with rewards directed back to the EF treasury.

the Protocol Support team at the @ethereumfndn now has a website, thanks to the EF's phenomenal Digital Studio team! Particularly excited for this because it helps you navigate & understand the resources we maintain to support Ethereum core development: ⑅ Forkcast ⑅ the Project Management repo ⑅ ACD calls ⑅ breakout calls ⑅ the Ethereum Protocol Fellowship ⑅ the Ethereum Study Group (which kicked off with 150+ participants today!) you no longer have to navigate a Github repo to find a list of active breakout calls! ⏦ link in next tweet ⏦