Eth Docker v26.7.2 is out . It supports the "Nimbus Unified" client, with the caveat that this client is still in alpha. Give it a spin on Hoodi testnet!

"beaconstate.info" checkpoint URLs have been shut down, and Eth Docker will replace them during ethd update

Nethermind 1.39.2 fixes a whole gaggle of vulnerabilities, but also removes the bloom filters for eth_getLogs. Eth Docker now enables Nethermind's log index by default, so protocols like SSV, RocketPool, Nodeset, Stakewise &c can get their receipts, still.

Nimbus supports EraC files for its archive node, and now Eth Docker automates fetching them. This removes the need to genesis sync a Nimbus archive node.

Glamsterdam devnets are heating up, with devnet-8 likely the first time users can try ePBS parameters. Eth Docker had an extensive pass for devnet support, and it should work for all clients. NETWORK=https://github.com/ethpandaops/glamsterdam-devnets/tree/master/network-configs/devnet-7/metadata for devnet-7, for example.

Podman is supported . It requires pesto port forwarding, and I'd still consider it an experimental feature. That's more about what podman can do with networking than what Eth Docker can do.

I'm seeing a lot of these failures? Seems to have started with the last two updates...

expected 2, produced 2, included 1

But it doesn't seem related to CPU Memory or Network.

top - 18:17:39 up 1 day, 12:09,  1 user,  load average: 1.56, 0.72, 0.67

Tasks: 291 total,   1 running, 290 sleeping,   0 stopped,   0 zombie

%Cpu(s):  5.9 us,  0.5 sy,  0.0 ni, 93.4 id,  0.1 wa,  0.0 hi,  0.1 si,  0.0 st 

MiB Mem :  63971.8 total,   2023.1 free,  46360.9 used,  16357.4 buff/cache     

MiB Swap:   8192.0 total,   6467.0 free,   1725.0 used.  17610.8 avail Mem 

grep -B5 -A5 "50%" teku.log

Sample Logs

2026-07-17 16:21:12.085-0600 | beaconchain-async-0 | INFO  | teku-status-log | Attestation performance: epoch 462245, expected 2, produced 2, included 1 (50%), distance 1 / 1.00 / 1, correct target 2 (100%), correct head 2 (100%)

2026-07-17 16:21:15.100-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14791904, Block: d8824344c8015a2163ac0c8401a5caf9b4a7d0dcd20fe44fb991e497ef994a30, Justified: 462246, Finalized: 462245, Peers: 58

2026-07-17 16:21:23.096-0600 | validator-async-9970 | INFO  | teku-validator-log | Validator   *** 2 out of 2 validator registration(s) were successfully sent to the builder network via the Beacon Node.

2026-07-17 16:21:27.101-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14791905, Block: 0a2a576987b82d61c6cfde76a1d66c6d267425a1e623a539bb5f57fb95ed829b, Justified: 462246, Finalized: 462245, Peers: 60

2026-07-17 16:21:39.100-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14791906, Block: 2bbe49f4e120d10dd10bfa13c72bed03382c9379bdb00fd3d07950e214021b3f, Justified: 462246, Finalized: 462245, Peers: 59

2026-07-17 16:21:51.106-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14791907, Block: d9eee1ac4ddd11d69fd311b95230f7545065b421e4120b135d7c54eb48c3f593, Justified: 462246, Finalized: 462245, Peers: 60

--

2026-07-17 17:24:36.748-0600 | validator-async-10301 | INFO  | teku-validator-log | Validator   *** Published attestation          Count: 1, Slot: 14792221, Root: 437befade4b36d480133eff54f8433cf83c987f3f7698a8525a448e45fbad015

2026-07-17 17:24:39.001-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792221, Block: 437befade4b36d480133eff54f8433cf83c987f3f7698a8525a448e45fbad015, Justified: 462255, Finalized: 462254, Peers: 65

2026-07-17 17:24:51.093-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792222, Block: 62c63762bedf85df72ce97fe3ec517620440b725598ee49fecc4dc6e77788636, Justified: 462255, Finalized: 462254, Peers: 65

2026-07-17 17:25:03.092-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792223, Block: 3a08246ead855a146653a11c2089f8ae8a7dba8a78231a31026ef138d96f66ac, Justified: 462255, Finalized: 462254, Peers: 65

2026-07-17 17:25:11.002-0600 | TimeTickTask | INFO  | teku-event-log | Epoch Event *** Epoch: 462257, Justified checkpoint: 462256, Finalized checkpoint: 462255, Finalized root: badb8e06059b700450e9bd3a6eae076d936d27a45cee0b5bbd91973c16673d09

2026-07-17 17:25:12.342-0600 | beaconchain-async-11 | INFO  | teku-status-log | Attestation performance: epoch 462255, expected 2, produced 2, included 1 (50%), distance 1 / 1.00 / 1, correct target 2 (100%), correct head 2 (100%)

2026-07-17 17:25:15.095-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792224, Block: 21568111ea6c41dcc577b6b739f289804ae08176a4c04a9e242e3224fb99d703, Justified: 462256, Finalized: 462255, Peers: 64

2026-07-17 17:25:23.094-0600 | validator-async-10322 | INFO  | teku-validator-log | Validator   *** 2 out of 2 validator registration(s) were successfully sent to the builder network via the Beacon Node.

2026-07-17 17:25:27.096-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792225, Block: db04b46b2652ae791f3d448bb56375a6b252e4eabd34091244a219faa325c177, Justified: 462256, Finalized: 462255, Peers: 63

2026-07-17 17:25:39.100-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792226, Block: c38e63e3a9b035f7c37ba018aecd99ce76c204c96b7c16eb670ba96aefc3bc40, Justified: 462256, Finalized: 462255, Peers: 65

2026-07-17 17:25:51.097-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792227, Block: 7618f8d30f0591924d824e1094d509cdd8fa9a7de7d50d04e9fcc13b3f57bbd9, Justified: 462256, Finalized: 462255, Peers: 63

--

2026-07-17 17:37:15.096-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792284, Block: 09d8a01a0cb848f4e360ec8d0bf69176271e7e0e82e63dc0861750cf61647098, Justified: 462257, Finalized: 462256, Peers: 67

2026-07-17 17:37:27.095-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792285, Block: 6c91da72cdc95583ba928ed517274587d86c61c63ba1c8f24e8a3946259d2c74, Justified: 462257, Finalized: 462256, Peers: 66

2026-07-17 17:37:39.100-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792286, Block: 6e6f4871976a1c91b6c364051c3c576f8796af518753e93ad886b0b8a0736571, Justified: 462257, Finalized: 462256, Peers: 66

2026-07-17 17:37:51.094-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792287, Block: 2792765496241fd2a5a1221470f3a9d3bb14a08290fb32369d5ceb31c75f0516, Justified: 462257, Finalized: 462256, Peers: 64

2026-07-17 17:37:59.002-0600 | TimeTickTask | INFO  | teku-event-log | Epoch Event *** Epoch: 462259, Justified checkpoint: 462258, Finalized checkpoint: 462257, Finalized root: 21568111ea6c41dcc577b6b739f289804ae08176a4c04a9e242e3224fb99d703

2026-07-17 17:38:00.181-0600 | beaconchain-async-5 | INFO  | teku-status-log | Attestation performance: epoch 462257, expected 2, produced 2, included 1 (50%), distance 1 / 1.00 / 1, correct target 2 (100%), correct head 2 (100%)

2026-07-17 17:38:03.103-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792288, Block: aa8a7755ba0cebbdb8e922b6a3ca232e86cdc0d14947661bca946ae8914aaac3, Justified: 462258, Finalized: 462257, Peers: 63

2026-07-17 17:38:11.093-0600 | validator-async-10385 | INFO  | teku-validator-log | Validator   *** 2 out of 2 validator registration(s) were successfully sent to the builder network via the Beacon Node.

2026-07-17 17:38:15.100-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792289, Block: 138e5c2c0ac18a99f6440be86ae1a87c070be4942e4e12829b180efe203e3c25, Justified: 462258, Finalized: 462257, Peers: 71

2026-07-17 17:38:27.098-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792290, Block: fadef6be4a2479f7230db661efa66fdc49b1b61d8315e9e2524c3beb16c81e84, Justified: 462258, Finalized: 462257, Peers: 69

2026-07-17 17:38:39.099-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792291, Block: e6c950204cf29408c32267cd16bd5baca5668c7fa3efd45c5d9761933ee4066e, Justified: 462258, Finalized: 462257, Peers: 71

--

2026-07-17 17:56:27.101-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792380, Block: 7cd533600f21db8cdc38450d0b3a901e91b261ad6b23f37f79ecf320cb4ad454, Justified: 462260, Finalized: 462259, Peers: 63

2026-07-17 17:56:39.105-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792381, Block: 90f18408aef0c918ff603c0cf238a40e29ea028fd4d00f4f1e55c938ba096bb7, Justified: 462260, Finalized: 462259, Peers: 63

2026-07-17 17:56:51.104-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792382, Block: cb2ac79a8c189ab9dcaae6ae3780f3ab186d9f54e1bb70ccf6e336162e7025ad, Justified: 462260, Finalized: 462259, Peers: 65

2026-07-17 17:57:03.113-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792383, Block: 66741bdef5b7fa167a42b40f6e87bb655bc236dee24c957cea24c3f9f10c0076, Justified: 462260, Finalized: 462259, Peers: 65

2026-07-17 17:57:11.001-0600 | TimeTickTask | INFO  | teku-event-log | Epoch Event *** Epoch: 462262, Justified checkpoint: 462261, Finalized checkpoint: 462260, Finalized root: c1165c010b1284d9f76ef6648923334d9b8311e04b0a3b71d871b0bdc2781376

2026-07-17 17:57:12.165-0600 | beaconchain-async-7 | INFO  | teku-status-log | Attestation performance: epoch 462260, expected 2, produced 2, included 1 (50%), distance 1 / 1.00 / 1, correct target 2 (100%), correct head 2 (100%)

I have several validators hosted at allnodes and accessed by my ledger. The issue is they all have different accounts/withdrawl addresses.

According to the FAQ this is not an issue as you only need to sign on the sender.

The trouble is all the tools to do this (allnodes, launchpad, consolodeth, pectrastaking) have the same problem in that they can only see 1 account AT A TIME

So I can select #2 as the sender but then it can't see #1 as the receiver, I did find an old reddit post that said you could manually enter the receiver in launchpad but it seems that's not working anymore.

The only alternative is to withdraw #2 (wait ~8 days) then deposit to #1 (wait ~46 days) but obviously that's not ideal, especially as this should be possible.

Does anyone have any other ideas ?

anybody uses mac mini m4 to self stake?

I have been trying out Reth with Lighthouse.

After about two weeks of downloading, it filled my 2.2 TB ssd...

2026-07-12T23:05:52.244418Z INFO reth::cli: Status connected_peers=30 stage=Execution checkpoint=23590160 target=25438447 stage_progress=82.16%

2026-07-12T23:05:57.781492Z ERROR sync::pipeline: Stage encountered a fatal error: database integrity error occurred: No space left on device (os error 28) stage=Execution

Did I miss a configuration to activate pruning or something? Can anyone with Reth experience give me the necessary settings? I thought it was all looking ok... so tired of having clients do weird stuff. (Gave up with Besu lately after it never stayed reliable for more than a few months).

EDIT:

For reference, the Reth guidance is not clear. For example, the following is provided in the manual:

reth download --chain mainnet --minimal

reth node --authrpc.jwtsecret /path/to/secret

From my testing, if one fails to add "--minimal" to the node command, execution will fail since it is expecting the wrong block.

Looking for a similar small form factor device. Preferably utilizing DDR4 RAM since ram prices are crazy.

Hello Friends! I’m looking into updating to a 4TB SSD on my NUC10i7FNK. I currently have a SAMSUNG 970 EVO Plus 2TB NVMe M.2 w/ V-NAND. Running Nethermind + Nimbus and haven’t had any problems at all. Last time I checked it was at about 1.36TB. I’ve read that my mini pc is backwards capable to Gen3 with a Gen4 SSD. Though not capable with a Gen5 or an 8TB. Any advice in here on a replacement SSD?

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!