The 2026 EthStaker staking survey results are out! 528 stakers told us how they run their validators and what they are worried about, and we analyzed that across the last 3 years of surveys. Link to full analysis with charts in the next tweet and more in thread. ↓

I was unhappy with the current state of Ethereum crawlers, so I vibe coded and open sourced a new one. enrscout.ethnodeops.xyz/

RT @nero_eth: @mzeller Lowering the min stake means more validators. More validators means more signatures to aggregate. This impacts how s…

We’re looking for your feedback - and we’re offering 1 ETH for it! Complete the StakeWise Satisfaction Survey in our app before September 30th for a chance to win 1 ETH, sent directly to your wallet 💸 Terms apply.

Enter: EthCoordinate. tl;dr: EthCoordinate is a crypto-native organization born inside the EthStaker community, bringing together separate efforts under one umbrella to help with Ethereum governance coordination, support Forkcast, increase stakeholder engagement on proposed or upcoming EIPs and, of course, continue providing software, tooling, and technical support for home stakers. EthStaker started in 2020 when a loosely connected group of Ethereum enthusiasts joined efforts to speed up the development of the beacon chain. The organization steadily evolved, incorporating as a 501(c)4 nonprofit and taking up initiatives around independent participants of Ethereum's consensus mechanism, aka home stakers. Throughout the years, it has played a decisive role in coordinating the launch and operation of devnets, testnets, and mainnet hard fork upgrades; facilitating information flows and generally connecting dots that needed connecting. This year's tectonic organizational changes in the ecosystem have opened up functional gaps in Ethereum coordination. To close these gaps and continue supporting the network, EthStaker's core members are joined by mission-aligned fresh blood to aggregate efforts under one name to produce greater results than operating independently. EthCoordinate is a natural evolution of EthStaker; as Ethereum mainnet heads to its third radical consensus protocol change at a steady pace, it’s time for EthStaker to recalibrate around what Ethereum’s evolving community needs. Our mission is to facilitate interaction between stakeholders of the ecosystem to accelerate the adoption of the Ethereum network and to provide continuity for governance operations. We believe that the Ethereum mainnet is an unparalleled bedrock for the augmentation of humanity's productivity output and that ETH, the asset, is the token that aligns the incentives of all actors involved. We stand up for our values, combining technical rigor with pragmatism for Ethereum to continue being the most accessible and credibly neutral global blockchain. The team is 10 long-tenured Ethereum professionals and currently our main work streams are: ⇥ Maintain a high-quality venue for independent stakers to remain engaged and informed ⇥ Facilitate coordination around core protocol development and adjacencies ⇥ Develop and steward Forkcast, the most popular platform to track the research and engineering initiatives around Ethereum's core protocol ⇥ Facilitate research, discussion, and coordination around protocol economics in support of Ethereum's long-term economic health ⇥ Maintain open source tools and documentation used by participants of the consensus set We're energized for this chapter in Ethereum coordination & our role in it.

Correlated downtime penalties got their first update in ~2 years as they're considered for inclusion in Hegota! Tl;dr: - This EIP increases downtime penalties temporarily if a large amount of the network goes offline together. The goal is to penalise all stake piling onto the same few operators and datacenters, which has become a significant issue over the last 5 years. - The original design was a tiny blip of penalties, not enough to change behaviour, nor enough to justify the dev effort. Now the penalties can scale up to 128x from the baseline penalty. - This is still pretty small in terms of your principal, but can set you back weeks or more of rewards if you stake in a centralised manner that has an extended outage. (Worst case is ~0.38% of principal per day if you and a third of the network are offline, which is more than a month of lost rewards) - Focusing on the source + target vote ensures short term failures in block production won't trigger this penalty. - This penalty caps at 33% of stake offline, after that, its the existing inactivity leak that punishes you further, (which has a lot more teeth!). Check out some example payback times, and a new vs old graph to show why the update is needed. Hopefully the Core Devs will include EIP-7716 in Hegota, and Ethereum can start to value its decentralisation rather than taking it for granted before its all gone. Ask your local core dev to SFI EIP-7716!

ethrex has been running in production on Ethereum mainnet for six months. Independent staking operators validate through it, and we wrote up what those months actually looked like. The short version: @SerenitaIO, @Stakely_io, and @RockLogicGmbH (among Lido's curated operators) run ethrex alongside the other execution clients. @LeastAuthority audited the full stack, and every finding is addressed. Thirteen stable releases since January, weekly since May, and every upgrade is a drop-in restart with no resync. The write-up also covers what a young client's first months really involve: getting shipped by eth-docker from @ethStaker, Stereum from @stereumdev, and @EthereumOnARM, getting marked stable on clientdiversity (.org), first interop as a participating client, and the parts that aren't solved yet. Market share is still minimal, some packagers lag a few versions behind, and a couple of integrations are still open PRs. Our conformance and Hive results stay public, whether they flatter us or not. If you run validators and want a second (or fifth) execution client: ethrex syncs mainnet in about an hour and a half on 4-8 cores, 32 GB RAM, and a 1 TB NVMe. Read the full story in our new blog post ⬇️

we are live now in this @ethStaker community call about operationalizing ePBS in Glamsterdam come watch in the youtube stream and ask any questions!

Glamsterdam devnet-7 is live. More progress on the road to testnet 🚢 On the CL side: - EIP-7688 progressive containers - Updated payload deadlines and builder lifecycle parameters On the EL side: - EIP-2780 and 8037 → state-dependent charges moved from intrinsic gas to runtime, with updated account-creation and calldata-floor accounting - EIP-7928 and 8038 → BAL and SSTORE access-ordering fixes - EIP-8282 → finalized builder deposit and exit contracts, limits, fees, and disable controls Onward.

RT @benjaminion_xyz: I know it's totally weird for core devs to talk to users, but I've only gone and done it. Upgrading Finality 2: What…

Thanks to all the stakers who keep themselves up to date via @EtherealnewsHQ 🙏

Tracking of CL/EL client usage is critical for understanding network resilience, but there’s no reliable reporting solution. I'm proposing a new 32 byte beacon block body data field that can track client usage and setup details with the ability to expand to monitoring zkCL proof diversity in the future. ethresear.ch/t/in-protocol-c…

Ethereal news weekly #30 🏦 @ethereumfndn Ethereum basics for governments & institutions 🌱 @ethereuminsti launched 🪶 @RobinhoodApp Robinhood Chain live ethereal.news/ethereal-news-…

I am beyond thrilled to see the diversity in usage of various clients and, in particular, the growth in adoption of @ethnimbus among the staker community in the last two years! It feels like we have come a long way. I honestly had no idea we’d see this kind of traction when we started engaging the community on Nimbus CL a few years ago. Grateful to the community and kudos to the stakers for doing what is right for the network.

Release v7.1.5 is now live! This release is dominated by Gloas (ePBS) fork development, alongside broad performance and memory optimizations, additional Beacon API event and endpoint support, and a round of gossip-validation and concurrency hardening. Operators can update at their convenience. You can find the v7.1.5 release here: github.com/OffchainLabs/prys…