A community of Ethereum stakers providing resources, support, tooling, & helping each other learn #StakeFromHome Managed by @butta_eth & @remy_roy

r/EthStaker
Joined October 2020
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. ↓
32
59
3
144
35,613
EthStaker πŸ¦‡πŸ”Š retweeted
I had to testify in a trial I wasn't involved in. Here's my story:
28
30
23
285
110,416
EthStaker πŸ¦‡πŸ”Š retweeted
Ethereal news weekly #41 πŸ»β€β„οΈ Glamsterdam upgrade on Sepolia testnet October 6 🌏 Vitalik: the cryptographic world computer πŸ¦– @jih2nn HegotΓ‘ upgrade focil-devnet-0 live ethereal.news/ethereal-news-…
7
22
4
70
15,699
EthStaker πŸ¦‡πŸ”Š retweeted
Release v7.2.1 is now live. This release focuses on Gloas builder configuration in the validator client. The release also adds the Sepolia GAS_LIMIT_SCHEDULE, so validators default to a 200M gas limit from the Sepolia Gloas fork (epoch 353024, October 6, 2026, 13:53:36 UTC). This needs no action. To use a different gas limit, set gas_limit in your proposer settings, set it through the keymanager API, or use --suggested-gas-limit. Partial data columns (cell-level PeerDAS dissemination) are on by default. --disable-partial-data-columns turns them off. --partial-data-columns is deprecated and has no effect. [PR]. You can find the v7.2.1 release here: github.com/OffchainLabs/prys…
2
6
1
19
1,845
EthStaker πŸ¦‡πŸ”Š retweeted
The first Ethereum testnet forks to Glamsterdam tomorrow! A smooth fork will be followed by a fork to Glamsterdam on the Hoodi testnet, then mainnet. After this fork, we'll have a pretty good idea of when we're going live on mainnet. The headliners are enshrined proposer-builder separation (ePBS, EIP-7732) and block-level access lists (BAL, EIP-7928), and some other highlights are an increase in the max contract size and faster consolidation queues. When: Tuesday October 6, 13:40 UTC Join the YouTube livestream to watch the fork go live, and bring your questions to the chat. youtube.com/watch?v=T9sXJYIE…
1
13
3
55
20,476
EthStaker πŸ¦‡πŸ”Š retweeted
Staking Nerd Talk 8 is live. Learn about Type 0 validators getting the axe; keeping your 2TB SSD humming for years to come; Post Quantum Ethereum; Glamsterdam and HegotΓ‘ hardforks, and more. Join Patches and myself for an hour of mind-numbing Eth nerdery: youtube.com/watch?v=S2lEd6-7…
5
1
15
860
EthStaker πŸ¦‡πŸ”Š retweeted
I was unhappy with the current state of Ethereum crawlers, so I vibe coded and open sourced a new one. enrscout.ethnodeops.xyz/
21
21
5
185
21,193
EthStaker πŸ¦‡πŸ”Š retweeted
Replying to @mzeller
Lowering the min stake means more validators. More validators means more signatures to aggregate. This impacts how short slots can be, or, more generally, how quick we can finalize. Do you want a chain that has short slots and finalizes quicker? If not, no one blocks you from doing an EIP proposing to extend slot time, or add more slots to an epoch, thus indirectly time-to-finality and decrease min stake in parallel. The chance of going years (>=2) without a proposal is 1.73%, assuming you're a 32-ETH validator. Also, proposal rewards (incl MEV) are merely ~25% of the total reward, most is from attesting where you need no luck. Pls report your RAM problems to clients if not already done. I think testing is done on the recommended hardware (eip-7870), and those machines habe had no issues. How much work maintainance and monitoring is for (solo) stakers is individually different + debateable and probably depends how technical one is. I know validators that haven't been touched (except upgrading for forks), not even actively monitored, for years. Based on the 2026 @ethStaker survey, 43% spend less than 1h per month on it. 70% less than 2h per month. With today's apy, that's ~$80-$160/working hour.
1
2
54
1,922
EthStaker πŸ¦‡πŸ”Š retweeted
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.
1
3
14
921
EthStaker πŸ¦‡πŸ”Š retweeted
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.
27
60
20
296
51,102
EthStaker πŸ¦‡πŸ”Š retweeted
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!
6
8
1
37
4,157
EthStaker πŸ¦‡πŸ”Š retweeted
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 ⬇️
5
5
3
21
3,240
EthStaker πŸ¦‡πŸ”Š retweeted
we are live now in this @ethStaker community call about operationalizing ePBS in Glamsterdam come watch in the youtube stream and ask any questions!
Next week we'll have Community Call #70 about Operationalizing ePBS for Glamsterdam! We'll hear from a variety of teams across the staking ecosystem (core devs, builders, protocols, guides) to share how ePBS is getting put into action for the upcoming Glamsterdam hard fork and answer any questions. Join us live with Q&A: Wednesday, July 22nd at 15:00 UTC Link below
1
6
956
EthStaker πŸ¦‡πŸ”Š retweeted
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.
12
40
3
186
14,441
EthStaker πŸ¦‡πŸ”Š retweeted
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 the Ecosystem Told Us Huge thanks to all who participated πŸ™ consensus.ethereum.foundatio…
4
40
6
241
23,230
Next week we'll have Community Call #70 about Operationalizing ePBS for Glamsterdam! We'll hear from a variety of teams across the staking ecosystem (core devs, builders, protocols, guides) to share how ePBS is getting put into action for the upcoming Glamsterdam hard fork and answer any questions. Join us live with Q&A: Wednesday, July 22nd at 15:00 UTC Link below
2
2
2
9
2,259
We'll have @d_gusakov this week in Community Call #69 to talk about EIP-8148: a proposal for Custom Sweep Thresholds for Validators. When: Wednesday July 8, 15:00 UTC Join the YouTube livestream (link to follow) and ask any Q&A there!
3
11
28
3,637
EthStaker πŸ¦‡πŸ”Š retweeted
Thanks to all the stakers who keep themselves up to date via @EtherealnewsHQ πŸ™
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. ↓
2
1
8
695
EthStaker πŸ¦‡πŸ”Š retweeted
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…
3
3
1
25
1,411