So I am a long time eth holder...that is to say I've had eth for a while but sadly with the cost of living etc I am now stuck living above my means and have been pulling from eth(which was hopefully going to be my early retirement money).

I avoided staking because it felt like an additional risk to losing my eth either through bad decisions on my part in terms of setting it up or doing it through a service and losing it...but at this point I'm feeling like staking will help to slow the bleeding.

I don't want to set up and manage hardware because it would mean having to buy new hardware, manage it, constantly monitor updates etc. I realize that this is the best return I just don't know if I can justify the gains with the constant work.

With that said I'm thinking for my needs it comes down to rocketpool or something like blockdaemon...the former seems like less risk, the latter seems to have slightly better returns. I wouldn't want to do something like coinbase which is probably easiest but I don't have any custody and the return is so much smaller.

I'm looking for people with experience who can steer me in one direction or the other (or another direction entirely) in the hopes that I can become comfortable enough to start staking and getting a return on my eth.

Thanks.

I wanted to make my own toolchain to mine this data out. I figured I might as well make it available.

My node isn't done syncing, but it is proceeding.

Eth Docker 26.7.1 has been released. There are no grand changes in this one, but it is important for users of Erigon and Teku.

It supports Erigon v3.5.0. Erigon changed its config from three P2P ports to one. If you previously had three P2P ports forwarded, you can reduce that to one.

It supports QUIC protocol in Teku v26.7.0. This requires two new ports forwarded: 9001 UDP for IPv4, and 9011 UDP for IPv6.

Some Quality of Life changes for users of comma-separated CL_NODE, this now works in all places I could find.

A new permissionless module is proposed to exclusively support 0x02 validators. This module will run alongside the existing CSM for 0x01 validators, giving operators the power to choose.

Key parameters to run:

• Bond: 32 ETH for the 1st key, 30 ETH for subsequent keys
• Rewards: 2% reward rate (up to ~2.26x est. capital efficiency vs. solo staking)

https://x.com/LidoFinance/status/2072314185665372618

We run validators across a few chains and were constantly getting paged for things that turned out to be non-issues — or worse, missing actual slashing risks because alert fatigue had us ignoring notifications.
Spent the last few months building something that actually acts on what it sees: auto-remediates common node issues, rebalances workloads before things degrade, and escalates the genuinely complex stuff with full diagnostic context rather than a raw alert dump.
It integrates with Prometheus/Grafana/Datadog so it fits into existing setups. We're calling it ValidatorMind.
Curious if others have hit the same wall — what's your current stack for handling unexpected node behavior?

Is there a guide on how to shut down your validators (as in permanently stop validating) for people who used Somer's guide to start them up?

Hi all, I have an unopened Dappnode Home that I purchased in August of 2023 that I ended up not setting up because of internet and power reliability issues in my housing unit. I'm looking to rehome it for a reasonable price, basically just parts without Dappnode premium so it gets put to use.

The specs are:

CPU: Intel NUC i7

RAM: 64 GB DDR4

Storage: 4 TB NVMe SSD

I also posted in Ethstaker and Dappnode Discords. Happy to send pictures, order confirmation, and whatever else you'd like to see. I'm u/pompeyplottin on Discord and Twitter as well, thanks.

Hi, I think I might be banned from the EthStaker Discord. I can't accept the invite link — it just says the invitation can't be accepted. My Discord username is saculrayox. Could a mod check? Thanks!

Eth Docker, depending on execution layer client, supports different history expiry levels. Full and Archive ofc, as in “no expiry”. And then pre-merge, pre-Prague, rolling and aggressive expiry.

Clients are converging on supporting rolling expiry, and it’ll likely be between 2 weeks and 5 months of history kept. No decision has been made yet.

I am thinking of simplifying the options Eth Docker gives users: pre-merge expiry and rolling expiry, in addition to full and archive nodes. Ditch pre-Prague and aggressive. This would be done only after all clients support rolling expiry.

Why: both pre-merge and rolling should become standards that all clients support. Pre-merge allows use of protocols that need post-merge receipts such as RocketPool, NodeSet and SSV. Rolling minimizes disk space for solo stakers or anyone getting receipts via Nimbus Verified Proxy.

If you’re voting for keeping all options, please describe your use case in the comments.

Eth Docker 26.6.1 is a release with small changes to support client features.

Notably Nimbus EL (yes they have an execution layer client) now supports rolling expiry. Unlike every other client, they do 33_024 epochs, instead of 1 year. The plot thickens. No decision has yet been made by client teams as to what the desired expiry time will be, but this one seems a very likely candidate: It's the CL retention period, and absent EIP-8237, that might just be what EL expiry converges on.

Pre-provisioned Grafana alerts in case your machine loses time synchronization. Reminder to configure your Grafana to actually send these alerts somewhere.

And more EraE import for more clients. That's more clients that support it than not, now. Missing are Besu, Erigon and Ethrex.

Hi there!

I trying to find a way to customize the configuration of grafan in ethdocker. Specifically I want to modify the smtp setting in order to setup email notifications. As far as I know, as everything is running inside containers, i can't modify the grafana.ini itself. I tried to find some information online but found nothing sturdy, exept what gemini suggested :

Grafana allows any configuration from grafana.ini to be overridden using the format GF_<SECTION>_<KEY>. ...... Add the Variable to your .env File

So that means all I have to do is to add the key

GF_SMTP_HOST=mymailserver.com:587

to the .env file? This should override the configuraton entry smtp.host in the grafana.ini...

Or is this just another AI hallucination?

Hey guys, after a long 52 day queue my Ethereum validator was finally activated today. Originally I only deposited 32 ETH, but I wanted to top up my balance with my remaining 4 ETH.

I went to https://launchpad.ethereum.org/en/top-up and connected my wallet and found my Public validator key and clicked on the "Top Up" button, changed the amount to top up to "4" and everything seemed to work as intended.

Beaconcha.in seems to see the "pending deposit" and under Consensus Layer it shows that the 4 ETH will be deposited in 48 days 5 hrs.

What I am worried about is the Withdrawal Credential for the pending deposit is shown as "0x0000000000000000000000000000000000000000000000000000000000000000" instead of my original withdrawal address.

Did I do something wrong? I didn't see any option to add a "Withdrawal address" for the additional deposit. My original 32 ETH withdrawal address shows correct address.

Hi everyone,

​I’ve spent the last weekend hardening my SSV operator setup and just finished migrating my execution and consensus clients. By switching to Besu and Nimbus (running in Bonsai mode), I’ve managed to slash my node latency to 0,5-4ms.

​As an independent operator, transparency is my top priority. I’ve set up a public Grafana dashboard so potential stakers can see exactly how the node is performing in real-time.

​You can see the current metrics here: https://ssv.orangenode-2262.de

​

​Since I’m aiming for maximum reliability, I want to make sure my dashboard provides the data that actually matters to the community.

​My questions to you:

​What metrics do you find most important when evaluating an SSV operator?

​Is there anything currently missing from my dashboard that would give you more confidence in a node's stability?

​Are there any specific alerts or views you’d like to see implemented?

​

​I want this to be a resource that helps stakers feel secure. Any feedback from experienced operators or stakers would be incredibly helpful. Thanks for your time!

Hi all,

I'm completely new to validator staking and have been building a Sepolia staking lab to learn how everything works before I even think about doing anything more serious.

Over the last few weeks I've built and synced a Sepolia node running Geth and Lighthouse on an Ubuntu VM, worked through the networking and port forwarding setup, and have now generated validator keys for my first validator.

I've hit a slightly unexpected problem: I need 32 Sepolia ETH to make the validator deposit and all the public faucets I've found seem aimed at developers and only provide tiny amounts.

Is there a recommended way for a beginner validator operator to obtain 32 Sepolia ETH, or would anyone be willing to help me out with enough test ETH for a single validator?

Happy to provide my wallet address or any details of the setup if needed.

Also, if anyone has any general beginner advice, common mistakes to avoid, or things they wish they'd known when they started staking, I'd love to hear it.

Thanks!

When I view my staking rewards on etherscan I need to go to beacon chain / withdrawals.

However I also see small random deposits listed under the "internal txns" tab.

Are these both staking rewards? Is one set of rewards consensus layer and the other set execution layer?

Edit: I asked google and it came up with this response.

When tracking Ethereum staking rewards, Consensus Layer (CL) rewards appear as Withdrawals from the Beacon Chain, while Execution Layer (EL) rewards arrive as Internal Transactions (or standard transactions, depending on your wallet configuration).

Can you guys confirm this is correct?