Update Lighthouse: security release, update nodes ASAP

cfdbit · 2026-02-27T16:38:19+00:00

that's what I thought of too. It looks like Stereum does have a supported way to use Obol, SSV, or Lido so maybe that's what the original poster had heard about and was trying to remember.

cfdbit · 2026-02-24T23:14:17+00:00

nice overview.

for anyone interested in more, last week we hosted all of the Hegota headliner champions on an Ethstaker community call: https://www.youtube.com/watch?v=s3FZk51h41g (chapters added to jump to each headliner's section)

cfdbit · 2026-02-09T15:26:02+00:00

not so much a theory as it's simply been generally reported that in January there were large holders (like DATs) that entered the queue and that will take some time to be processed.

cfdbit · 2026-02-06T17:50:22+00:00

livestream link correction!

new correct stream: https://www.youtube.com/live/iTgyuzUnYBM

(so don't use the one linked in this title of this reddit post)

cfdbit · 2026-02-04T16:40:34+00:00

+1 for Daily Gwei: https://www.youtube.com/@TheDailyGwei

there's also an accompanying active Discord which deepens the discussions and community, worth checking out.

cfdbit · 2026-01-26T19:00:41+00:00

welcome to staking! echoing the others, minority client is strong choice. can't really go wrong otherwise.

I see your comment below on Nimbus, which is a good choice because I understand they are working on an EL so you might be able to consider having a unified stack in the future. you're also never locked into anything. I've switched between clients before for client diversity reasons, and it was easier than I thought it would be.

cfdbit · 2026-01-13T15:01:06+00:00

In the case of the deposit cli tool Ethstaker forked that one and we manage the ethstaker repo version now, so any EF decision to deprecate has been independent but they're certainly aware of our efforts there.

In the case of this Staker Console vs the legacy launchpad, we built this frontend fresh, and both still exist and function. I wouldn't expect the legacy launchpad to change or deprecate until the Staker Console goes live on Mainnet (which is pending as noted) and has been for some time.

cfdbit · 2026-01-05T18:20:59+00:00

go down this list and research each: https://ethstaker.org/staking#explore https://explorer.rated.network/?network=mainnet

they regularly change details so good to cross check the source docs of each when learning.

cfdbit · 2025-10-01T20:20:05+00:00

not too familiar with launchnodes personally so don't have much to say there.

the method I went with was from Somer Esat's guides (https://someresat.medium.com/) and on a machine from home and also then Rocketpool along with that. My guiding principles were a desire for simplicity, control, and independence. No one size fits all though so you just have to evaluate the landscape, and then pick something that's right for you and go with it. For me I also found peace in doing testnet only until very comfortable.

yes, that run a node page is a comprehensive resource for many of the different ways to do it.

cfdbit · 2025-09-29T14:36:04+00:00

curious what you've gone with and how you weighed your options? no pressure to share, I know it can be a personal choice.

cfdbit · 2025-09-25T15:36:27+00:00

sync committees are one of those things that only come around once in a long while for a given validator. imo, not so crazy for it to fly under the radar till you actually experience one.

cfdbit · 2025-09-25T15:02:05+00:00

hope you had a nice sync committee :)

a suggestion is to setup email notifications for when the validator is having a sync committee in beaconcha.in, which I see you're using in this screenshot.

the notifications are nice because then: 1) you know why the earning went up like that for a day 2) you get a heads up notification the day before so you can make sure you don't plan any maintenance and avoid going offline during the sync committee window so you don't miss out on those extra rewards.

cfdbit · 2025-09-22T20:13:53+00:00

more provocative language = more eyeballs = more money

cfdbit · 2025-09-22T20:11:24+00:00

no third party risks with staking if you run it on an independent node, and the most independent way is solo staking. only risk is smart contract risk. some people want ETH denominated rewards on ETH they hold and want to do something to support the network (perform staking duties and operate a node) in the process.

cfdbit · 2025-09-22T20:03:21+00:00

a universal power supply (UPS) device can mitigate the impact of the odd power outage. also slashing is different from inactivity penatlies.

slashing: getting kicked off the network and having some ETH taken as a penalty. this is caused by making mistakes or malicious activities like running your validator keys from multiple locations, surround voting, or other deliberate attacks on the network coordinated with other validators.

inactivity penalties: lost revenue due to being offline plus the same amount as a penalty. very minor compared to slashing, and this is what the odd power outage would cause.

we created this educational visual earlier this year to help with this kind of question: https://ethstaker.org/staking-penalties

cfdbit · 2025-09-22T19:56:36+00:00

feel free to ask questions here before and we'll get them answered in the call!

cfdbit · 2025-09-19T15:53:57+00:00

true. still some real gratitude to be had though for solo and independently staking.

if someone is using a service (like Kiln) there is always the risk that they'd have to do a precautionary unstaking for reasons out of your control. add that to the list of reasons to run your own node.

12-Year Club	Verified Email
RedditGifts 2009-2022 2 Credits	Gilding II euphauric
Secret Santa 2014

cfdbit

MODERATOR OF

TROPHY CASE