CSM has transitioned from its Early Adoption phase to being fully permissionless!

- The first validator key with just 2.4 ETH as a bond.
- Subsequent validators? Bond drops to 1.3 ETH.
- Early Adoption eligible participants still enjoy a discounted bond (1.5 ETH) for their first validator.

https://csm.lido.fi/

I notice the new update available for GETH, v1.14.13. Couple questions:

1. It notes a security release to fix CVE-2025-24883. I googled that, and nothing comes up. And there is no release notes on it, that I can see. What is it? And are these sorts of vulnerabilities not supposed to be documented?

2. I ran ubuntu system updates on my geth rig. However, after completion, I noted that geth had not been updated (still at 1.14.12). Any reason it is not in the ubuntu package yet?

Full disclosure - my geth rig is just a hot backup rig, not my primary service.

Hi, I'm running a validator (besu+nimbus) on a dedicated machine. I want to query the blockchain (simple things like current block, balance in an address etc.) and I can't figure out how to do it from a separate computer on the same network. What is it I need to enable? I have used SomerEsat's guides so afaict I need to access port 8551 (because that's the port Nimbus is accessing), but I do not seem to have permission. Is there something I need to enable in my Besu config?

Now that the court reversed OFAC sanctions on tornado cash when will relays stop censoring transactions?

https://www.mevwatch.info/

We need to make some noise about this.

I see the proposal to launch permissionless CSM validators will end on January 31.

It seems a nice way to earn rewards from a whole node with just 1.5eth, which could be about 7% apy. I also notice that node operators are launching their tools manage their nodes without the need of having the hardware (www.stakely.io/simple-csm-staking or www.launchnodes.com/lido-csm-node-operator)

Isn't that too good to be true? What are the risk for the protocol, apart from slashing, if this has lot of success?

Many retail or small investor could be onboarding soon

New hardware & bandwidth proposals

The Ethereum Consensus R&D team is proposing both hardware and bandwidth requirements to be part of an EIP: https://github.com/ethereum/EIPs/pull/9270

direct links for docs:

• Hardware: https://hackmd.io/G3MvgV2_RpKxbufsZO8VVg?view
• Bandwidth: https://hackmd.io/DsDcxDAVShSSLLwHWdfynQ?view

I have no issues with hardware requirements. I think that we see that stakers are generally not constrained by hardware - any upgrades are a while off and it's quite affordable to upgrade e.g. 2 TB to 4 TB to secure a 32 ETH bond.

Bandwidth

What I do have issues with are the bandwidth proposals:

tl;dr:

• 25 Mbps upload speed for those using mevboost
• 50 Mbps upload speed for those building locally

Current usage from home staking setups, from others who have shared and also from my own, peaks around 6 Mbps usage right now. (would be useful to get more data on actual usage from any of you!)

So at the low-end ceiling, this is a 4x increase in usage. At the high end, an 8x increase. This will be used for benchmarking.

The reasoning for this is to create headroom for more blobs and a higher gas limit. Generally put: more scaling, which the Ethereum community is (justifiably) vigorously calling for in response to chains like Solana having an culture of "IBRL: increase bandwidth reduce latency" and feeling like Ethereum's not winning in the landscape.

ePBS can help

More context: home stakers can advocate for enshrined proposer-builder separation (ePBS) to be included in the fork after Pectra, which will give validators more time to process the block and therefore spread the traffic over a longer period of time and reduce the peak usage. Enshrining PBS will also give headroom for blobs and gas limit.

Current bandwidth

I think both of these numbers, 50 especially, are too high to aim for at the moment, especially without having ePBS. Cities like LA, Berlin, Sydney have median upload speeds below 25. Cities like NYC, Brussels, and Vienna are below 50 Mbps (data**). This would mean that any home stakers in those areas either wouldn't be guaranteed participation in the future, or between 25-50, they just wouldn't be able to build locally or use a min-bid flag. OBVIOUSLY, if stakers CAN pay for better internet, they should be expected to. But if they don't have the option, there's not much they can do besides drop off the network. For example, one of my nodes runs at a friend's house in California and I pay for the highest tier internet it can get, and it averages around 20 Mbps up.

** ^(to see this data on the website, toggle to "city", then click into the city to view both download and upload for both mobile and broadband. only broadband is relevant here)

• New York City: 36.14 Mbps
• Los Angeles: 21.56 Mbps
• Helsinki: 46.28 Mbps
• Berlin: 22.65 Mbps
• Rome: 46.83 Mbps
• Brussels: 27.77 Mbps
• Buenos Aires: 42.96 Mbps
• Vienna: 32.38 Mbps
• Montreal: 51.18 Mbps
• Dublin: 47.30 Mbps
• Sydney: 18.62 Mbps

pls speak up

If this affects you, i.e. if the maximum available upload speeds in your area are below 50 Mbps (or 25 for that matter), please speak up! If the majority of home stakers are above this threshold and we're okay to lose the few who are below that threshold, we also want to hear that!

This will be a topic of conversation at the All Core Devs call this Thursday where people will essentially decide if these values are reasonable to be "official" values put forth by the EF

Hoping someone on this thread can help me. I'm at the step of funding two validators through the https://launchpad.ethereum.org/en/ (fully synced and ready for deposit). When in the process of depositing the 64 ETH, one of the transactions failed (not sure why) and the other was successful. I tried refreshing the page and going through the process again but I'm blocked as my wallet doesn't have 64 ETH (only has 32.1 ETH now). I'm not able to even select 1 validator within launchpad at this point with the same deposit-data file as it still recognizes that I originally created the file with the idea of using 2 validators. The successful validator appears to be working and I can see it pending within beaconcha.in so I believe I'm good with that one. Any thoughts or insights on what I can do to fund the second validator at this point?

UPDATE: Fixed! Solution was to manually modify the deposit file to only include the failed validator and resubmit a single validator within launchpad.

If the chance of proposing a block decreases as more validators are added, doesn't this remove the incentive to run a validator node as the # of validators increase?

eg in early 2024 it was approx one proposal every 4 months, now in early 2025 it seems to be one proposal every 6 months

On Beaconcha.in my AIE is ar 75%. How can I increase it?

My attestation assignments are at 98%. I'm running Besu/Teku.

EDIT: I updated Besu/Teku from 24.12.0 to 25.1.0 and restarted my machine (it had been on nonstop for like 6 months). Now my effectiveness is at 98.7%.

I'm very interested in becoming a validator but don't have 32 ETH. I've heard of Rocket Pool as the alternative, but recently there's new options as well: Lido CSM, Obol, Stakewise.

Wondering if someone has a good comparison of these? What are the differences and things to consider when picking?

I tried claiming the airdrop today, but the gas fees is quite high (~$50), and that's just the first signing transaction. Considering the token is locked until a future governance vote, I'm not sure if I feel like going through with the claim. What are people here thinking?

I have two questions regarding staking post Pectra...

1. If a validator has e.g. 33 eth does the validator earn rewards on the entire 33 eth or just the 32 eth?
2. If a validator has e.g. 65 eth can the owner withdraw any amount of eth as long as there is at least 32 eth remaining?

Hi everyone! I'm experiencing an "error in block freeze operation", very similar to one reported by others in the past (example from u/tamastorok), and unfortunately none of the reported fixes seem to be working for me (for instance, my UPnP is already turned on in my router settings).

Errors highlighted in yellow

This error appears every minute. Usually it does not disrupt the chain being updated, but occasionally (once a day, or every few days) the error seems to create a pile-up, and prevents any further updates until I manually restart the Geth and Teku DApps.

I'm running Geth Execution Client (10.0.68), ETH Staking MEV-Boost (0.0.13), Teku Consensus Client (0.0.56), and the ETH Withdrawal address too (0.0.5)

Does anyone know of a fix?

Thanks!

If I have 32 ethereums in theory. If I deploy them in the lido, will I get 1 eth in a year, and if I launch a solo validator, will I get 1.4 eth in a year?

I'm new to this and am having difficulty obtaining Validator Keys. As you can see I downloaded AMD64 file from: https://github.com/ethereum/staking-deposit-cli/releases but it appears to be arm64 architecture. What do I do now as this won't run on my iMacPro?

S@iMac-Pro staking_deposit-cli-948d3fc-darwin-amd64 % file deposit

deposit: Mach-O 64-bit executable arm64

https://preview.redd.it/k0zulcjlqtee1.png?width=1812&format=png&auto=webp&s=4e41a561086d27b630b63f6fd64941f52bb521e7

Is this the best thing to do if you are going to HODL for the long run? Say i've already been staking my ETH, would it be worth it to turn it into a LST and restake it or is the hassle not worth it? So if i were to do this I would swap my ETH for ETHx and then take that ETHx to EigenLayer, but if I go to restake it it doesnt show me what kinda APY were looking at. I would hate to do all this just to find out I was getting less APY than where I started.

Hi All,

My ledger and exodus wallet has been compromised and lost all my crypto except some staked ETH . Can someone help me if I can save that from the attacker because I cannot transfer that without unstaking and once unstake the attacker will drain that aswell..Any help will be deeply appreciated

I'm in Australia,

I've had some ETH (under 10 ETH) staking in Kraken for a few years now under the 2-5% APR.

I just noticed I can re stake for 2.5 - 7% APR but when I select the option I get the below warning

On-chain staking services are provided by Payward Commercial Limited, a British Virgin Islands incorporated company. On-chain staking services are not provided by Bit Trade Pty Limited or any other Australian entity, and are not intended for Australian users.

If you participate in on-chain staking services, you do so at your own risk and will not receive the benefit of any regulatory protections in Australia. The on-chain staking service is governed by specific contractual terms.

Can someone ELI5 this for me? Does my current 2-5% Staking carry the same risk? As I never got that warning when I initially started staking.

I'm not interested in solo staking as I don't have the technical knowledge to do so. Any other advise would be appreciated Thanks

Hey all,

First off, thanks a ton for the help over the years.

I’ve been staking with a NUC since the beginning, but over the past couple years I’ve had issues with my machine. Running Linux, recently upgraded to 22.04 I believe, but it also happened plenty before then.

My system will randomly lock up/freeze after some unknown amount of time. Fully black screen (monitor will eventually say no input detected), moving mouse or pressing keyboard does nothing, but machine is still powered on, fans running etc. When this happens my validator goes offline. Only fix is holding the power button down for a while then starting up again.

Original research said overheating could cause this, so I upgraded to a fanless cooling case and temps look great now.

However, when I opened my machine to do the upgrade I noticed a lot of oil on the internals (yuck). I had to keep the machine on a high shelf in a shared kitchen with awful ventilation, so without me realizing, oil accumulated over a couple years… Fortunately I’ve upgraded my SSD and RAM so those are clean. But, I did notice some residue on my CPU as I did the upgrade to the new case.

Post-upgrade, things ran smoothly for several months, but now the freezing is happening way too often.

I’ve tried a variety of things to diagnose the crashing, including a kernel upgrade, but I can’t seem to pin down a cause…

In short, this post is mostly just a sanity check: do smart folks think it’s a reasonable idea to buy a new board/CPU to replace the yucky one? I’d like to just upgrade CPU but apparently it’s soldered so I’ll need a new board. Moreover, I won’t run into any file systems issues with that right? Since my key stores and everything are on the SSD I think I’m safe to just swap the boards, but please call me out if that’s false.

Thanks in advance for your time everybody. Always updoot the diddly.

If you had 64 ETH and had to pay for 2 servers in the past, does that mean you can consolidate it into one and only pay for 1 server?

Started my home solo staking journey. At first, it was quite overwhelming. I loved how it refreshed my memory of Linux and how to use terminal. I started out with https://launchpad.ethereum.org/en/ but found it a bit difficult. So I jumped on here and found the Someresat guide.

https://someresat.medium.com/guide-to-staking-on-ethereum-ubuntu-lighthouse-773f5d982e03

Followed the guide and got my Lighthouse+BESU staking node running. (No deposit yet)

```Output for sudo journalctl -fu besu

Jan 17 10:13:37 besu[2114]: 2025-01-17 10:13:37.177+02:00 | vert.x-worker-thread-0 | INFO  | AbstractEngineNewPayload | Imported #21,642,947  (ec1d9.....67b62)|  117 tx| 16 ws| 5 blobs| base fee   4.34 gwei| gas used   8,548,484 ( 28.4%)| exec time 0.173s| mgas/s  49.41| peers: 25

Jan 17 10:13:49 besu[2114]: 2025-01-17 10:13:49.495+02:00 | vert.x-worker-thread-0 | INFO  | AbstractEngineNewPayload | Imported #21,642,948  (3112d.....ffcd0)|  247 tx| 16 ws| 4 blobs| base fee   4.11 gwei| gas used  23,462,124 ( 78.1%)| exec time 0.377s| mgas/s  62.23| peers: 25

Jan 17 10:14:01 besu[2114]: 2025-01-17 10:14:01.563+02:00 | vert.x-worker-thread-0 | INFO  | AbstractEngineNewPayload | Imported #21,642,949  (dbc03.....bc390)|  148 tx| 16 ws| 0 blobs| base fee   4.40 gwei| gas used  14,932,980 ( 49.7%)| exec time 0.292s| mgas/s  51.14| peers: 25

Jan 17 10:14:14 besu[2114]: 2025-01-17 10:14:14.438+02:00 | vert.x-worker-thread-0 | INFO  | AbstractEngineNewPayload | Imported #21,642,950  (e1708.....39a0b)|  172 tx| 16 ws| 4 blobs| base fee   4.39 gwei| gas used  12,313,276 ( 41.0%)| exec time 0.294s| mgas/s  41.88| peers: 25

Jan 17 10:14:25 besu[2114]: 2025-01-17 10:14:25.816+02:00 | vert.x-worker-thread-0 | INFO  | AbstractEngineNewPayload | Imported #21,642,951  (85d26.....a6ddc)|  145 tx| 16 ws| 5 blobs| base fee   4.30 gwei| gas used  29,791,121 ( 99.1%)| exec time 0.333s| mgas/s  89.46| peers: 25

Jan 17 10:14:26 besu[2114]: 2025-01-17 10:14:26.081+02:00 | vert.x-worker-thread-0 | INFO  | AbstractEngineForkchoiceUpdated | FCU(VALID) | head: 85d26.....a6ddc | finalized: b3fe3.....05210 | safeBlockHash: 97599.....c3c08

```Output for sudo journalctl -fu lighthousevalidator

Jan 17 10:19:29 lighthouse[2118]: Jan 17 08:19:29.000 INFO Connected to beacon node(s)             synced: 1, available: 1, total: 1, primary: http://localhost:5052/, service: notifier

Jan 17 10:19:29 lighthouse[2118]: Jan 17 08:19:29.000 INFO Awaiting activation                     slot: 10856495, epoch: 339265, validators: 1, service: notifier

Now I went back to the Someresat guide "Step 13 — Fund the Validator Keys" This sent me back to https://launchpad.ethereum.org/en/

I clicked through the 10 steps and then selected BESU as my execution client. This, however, showed me a setup guide which was different from the one I followed.

"Setup

Make sure you do the following to get your execution client working properly.

JSON RPC endpoint

Use -rpc-http-enabled to connect your consensus node to the JSON RPC endpoint. This will enable the JSON RPC services on the default 8545 port.rpc-http-enabled documentationSetup"

Never saw this in the Someresat guide. Now I'm very much confused and would like to get confirmation before funding my node. Is the Someresat guide good to follow or should I try to rebuild my node following the BESU site? Sorry for long post.

I think it is high time to raise the gas limit!

We should have done it a long time ago !

As an Ethereum solo staker and a daily user of the network, I think that the gas limit should be increased several times the current level in a short time ...!

I have followed the instuctions on the https://pumpthegas.org/ website!

I run Geth as execution client and I use the "--miner.gaslimit 60000000" parameter.

I have produced a block locally (without mevboost) and I see that the gas limit of my block is only: 30029295 according beaconcha.in.

WHY?

Hey guys just here posting from Mexico

Any opinions/insights/hot takes on staking in Mexico?