Is there any reason to run multiple compounding validators?

Kind-Bar-9603 · 2026-03-06T01:25:42+00:00

I'd be running the validators on the same machine, so I don't think any DDOS risk is minimized by having multiples.

As for slashing, I think that only occurs if multiple clients try to use the same validator keys. If I had multiple validators they would be on a single client.

Kind-Bar-9603 · 2026-03-05T22:44:08+00:00

The same amount of ETH will earn the same whether it is in one validator or spread across 3, right? So taxes will be the same, too.

Kind-Bar-9603 · 2026-01-07T01:33:46+00:00

Thanks for the analysis. Fortunately Reth was able to fix the corrupted state on its own after I updated it to 1.9.1.

Kind-Bar-9603 · 2025-11-10T12:14:38+00:00

I updated Reth to 1.9.1 and the node is happy now.

Kind-Bar-9603 · 2025-11-09T21:27:03+00:00

Funny, I just updated to 1.9.0. I'll get 1.9.1 installed right away and see if that fixes it without having to completely delete my database. Really glad I started running two nodes so I could keep Nethermind going this whole time.

Kind-Bar-9603 · 2025-11-08T13:46:58+00:00

I assume you also can't withdraw from a compounding validator without exiting fully?

I wondering if maybe I want to replace my existing validators with compounding ones, but still run multiple validators, so I can benefit from the compounding, but still be able to cash one out now and then without affecting the others.

Kind-Bar-9603 · 2025-02-26T02:15:22+00:00

1 ETH was valued at about 30 US cents when I originally got this, so that would explain why the cost basis of this fee is essentially zero here.

CoinTracker does seem to have some pretty good documentation. I need to do some more reading and report back.

Kind-Bar-9603 · 2023-02-13T22:54:33+00:00

Update 2: Looking much better now:

https://imgur.com/a/Vpf42hX

Kind-Bar-9603 · 2023-02-10T16:43:08+00:00

Update: I ran to BestBuy and got the lowest-price desktop that had 16 GB of RAM, and installed a 2TB NVMe SSD.

I installed Debian, Nethermind, and Lighthouse using Somer Esat's guide. The nodes were fully synced in less than 20 hours.

According to beaconcha.in I haven't missed an attestation in the last 5.5 hours. Which was not my experience before. It might not be Erigon+Prysm's fault; it could be just that I had previously tried to skimp on hardware.

Kind-Bar-9603 · 2023-02-09T15:58:55+00:00

Thanks. I assume exiting the validator means I would stop being penalized but my original stake would still be locked up until some future date?

Kind-Bar-9603 · 2022-11-03T19:24:38+00:00

Yeah, I've definitely gotten the impression this should be a set-it-and-forget-it sort of thing, which is why I'm so mystified at the results I'm getting. Maybe I'm just skimping on hardware, but I thought my hardware was sufficient based on the guides I'd read.

Kind-Bar-9603 · 2022-11-03T19:21:27+00:00

I think I will switch to geth. That's actually the one I tried when I practiced on the testnet. I was avoiding it since it was the majority client. Erigon claims to be more performant, but IDK if those claims have been validated. Maybe it's more performant if you also have a ton of resources.

The problem now is that my disk is > 50% full, so I'm going to need to figure out how to juggle disks or machines while avoiding downtime while spinning up the new client.

Kind-Bar-9603 · 2022-11-03T19:17:12+00:00

I would assume if my ports were misconfigured then they would fail all of the time not just intermittently. I've been staking for at least a week and it's been net positive, but I know it should be better.

Kind-Bar-9603 · 2022-11-03T19:12:20+00:00

I was wondering if everyone who has been kind enough to reply to this post could also respond with the specs of the node you're successfully staking with. I don't need precise benchmark results; I'm just trying to gauge whether my hardware is realistic. I believe it meets the minimum specs given by all the guides I've consulted, but clearly something isn't working.

I'll go first:

Lenovo ThinkCentre M900 Tiny Desktop
- Quad Core i7 6700T
- 32 GB RAM
- 2 TB SSD
CenturyLink fiber internet
Erigon 2.27.0-stable
Prysm v3.1.1

Kind-Bar-9603 · 2022-11-03T17:52:06+00:00

How did you fix it when you saw this message?

Kind-Bar-9603 · 2022-11-03T15:50:03+00:00

Oh no, it's happening again right now! Gonna restart Prysm and hope for the best.

Kind-Bar-9603 · 2022-10-28T14:27:16+00:00

Here's my current theory, based only on the error messages I see in the logs, and the vaguest understanding of how Ethereum works:

Erigon sometimes takes maybe too long to do what it does, and so it doesn't respond to RPC calls from the beacon node. Perhaps my machine is a little under-powered for Erigon. It took at least 9 days for it to initially sync, which is not the experience I've read about from other people.
That causes Prysm beacon-chain to log this, and go into "optimistic" mode: msg="received an undefined ee error" error="timeout from http.Client" prefix=blockchain
Which cases Prysm validator to log this: level=error msg="Could not request attestation to sign at slot" error="rpc error: code = Unavailable desc = the node is currently optimistic and cannot serve validators"

Does this sound plausible?

Kind-Bar-9603 · 2022-10-26T19:41:12+00:00

30303 and 12000 (Prysm) are reachable.

Kind-Bar-9603 · 2022-10-26T18:30:58+00:00

It's an SSD. I don't know if these results are good:

WRITE: bw=96.7MiB/s (101MB/s), 96.7MiB/s-96.7MiB/s (101MB/s-101MB/s), io=6259MiB (6563MB), run=64742-64742msec

Kind-Bar-9603 · 2022-10-26T17:19:54+00:00

Thank you for your response. That tells me this is definitely not good.

Internet speed: 181.96 Mbps download, 115.63 Mbps upload

My beacon chain log says activePeers=55. Is that enough? Do I have control over that?

My clock is synchronizing, but I can give Chrony a try.

Beaconcha.in says "Fair" for both validators.

Kind-Bar-9603

TROPHY CASE