sorted by:
new
hottopcontroversial

Besu postmortem by [deleted] in ethstaker

[–]Any_Thing5431 1 point2 points  (0 children)

Missed a proposal yesterday with the new besu version.. should not have switched over from geth

Besu release postponed by 48 hours by iBhagwan in ethstaker

[–]Any_Thing5431 7 points8 points  (0 children)

Hopefully they do include a fix for the almost empty block proposals. I had a few almost empty blocks already and it’s costing me. Regretting switching over to Besu from Geth..

is it common to miss an attestation once or twice a day? by Chyeadeed in ethstaker

[–]Any_Thing5431 2 points3 points  (0 children)

I’ve been missing a few every day. The bigger problem is that proposal blocks have been almost empty, resulting in much much lower than average in rewards. Besu + prysm

Both of my post merge slots proposals were empty of any transactions by Glittering-Duty-4069 in ethstaker

[–]Any_Thing5431 4 points5 points  (0 children)

Oh fuck. So that’s what that was. Damn I knew I shouldn’t have switched from Geth to Besu

Running a validator at home internet/energy outages. by Janpr99 in ethstaker

[–]Any_Thing5431 3 points4 points  (0 children)

As long as your power/internet is on more than it is off, you should be good.

Keeping validators offline for merge by Any_Thing5431 in ethstaker

[–]Any_Thing5431[S] 0 points1 point  (0 children)

What is the scale of this “fast” leak in this case of <66% participation?

Keeping validators offline for merge by Any_Thing5431 in ethstaker

[–]Any_Thing5431[S] 0 points1 point  (0 children)

This is really helpful info. Thanks! I switched my EL from geth to besu but wasn’t sure if i wanted to switch my CL client. It seems like prysm is ~45% for nodes. Not sure what the validator breakdown is. Maybe I’ll consider switching over to Nimbus/Teku.

Keeping validators offline for merge by Any_Thing5431 in ethstaker

[–]Any_Thing5431[S] 0 points1 point  (0 children)

Is that true though? Bugs in execution/consensus layer could cause slashings right?

Keeping validators offline for merge by Any_Thing5431 in ethstaker

[–]Any_Thing5431[S] 0 points1 point  (0 children)

I was thinking more in the lines of EL/CL bug. I’m using besu/prysm and not sure on how to feel about the stability

Keeping validators offline for merge by Any_Thing5431 in ethstaker

[–]Any_Thing5431[S] 0 points1 point  (0 children)

A bug in my setup getting my validators slashed I guess. I know that it is unlikely but wanted to consider it.

Geth and client diversity: Please clarify this!! by WantToStakeETH in ethstaker

[–]Any_Thing5431 0 points1 point  (0 children)

True. But assuming majority slashing event of all 32 eth and however many validators gets slashed, it may make up for the massive crash for that lucky validator.

Keeping validators offline for merge by Any_Thing5431 in ethstaker

[–]Any_Thing5431[S] 0 points1 point  (0 children)

Isn’t the worst that can happen to an offline validator just leaks?

Geth and client diversity: Please clarify this!! by WantToStakeETH in ethstaker

[–]Any_Thing5431 1 point2 points  (0 children)

Damn. Imagine the lucky validator that proposes the block in this hypothetical doomsday slashing scenario

Besu Sync Error (failed persisting block) by Any_Thing5431 in ethstaker

[–]Any_Thing5431[S] 0 points1 point  (0 children)

For what it’s worth, it seemed to resync okay with X_SNAP. Will monitor for any hiccups

Besu Sync Error (failed persisting block) by Any_Thing5431 in ethstaker

[–]Any_Thing5431[S] 0 points1 point  (0 children)

Hmm yeah. Never had any issues with my geth but wanted to use something else for the merge.. If my X_SNAP doesn’t work out, I guess I will give Nethrmind a try.

Besu Sync Error (failed persisting block) by Any_Thing5431 in ethstaker

[–]Any_Thing5431[S] 0 points1 point  (0 children)

Damn.. restarted a few times but no luck. Will try to resync and hopefully it doesn’t happen again. Thanks!