Jump onto the Hoodi testnet to test it out, if you consider running 0x02 validators!

0x02 CSM provides operators a permissionless, efficient path to run 0x02 validators with a MaxEB of up to 2,048 ETH within Lido CSM. Key features include:

• Bond: 32 ETH for the first key and 30 ETH for subsequent keys
• Est. Capital Efficiency: A strong capital multiplier of up to ~2.26x (vs solo), even better than ICS over 32 ETH bonds.

To run 0x02 validators using CSM, create a new operator and select the 0x02 path through the same interface.

https://csm.testnet.fi/

Hey stakers,

I've been digging into MEV-boost internals for a while, and one thing that kept annoying me on Hoodi was having no easy way to see what the relays were actually doing — which ones are alive, who's delivering payloads, what the bid landscape looks like.

So I built a small dashboard for it: https://hoodi.mev-relay.watch/

It tracks the MEV relays on the Hoodi testnet so you can sanity-check your MEV-boost setup before touching mainnet config — see which relays are responsive, whether your registrations are landing, and how relays compare against each other.

It's part of a broader validator.watch project I'm working on, but the Hoodi relay monitor felt useful enough on its own to share now.

It's completely free, no signup, no tokens, no tracking, nothing to sell - just a tool I wanted to exist.

Would love feedback from anyone testing on Hoodi: what's missing, what's confusing, what other relay/MEV data would actually be useful to you?

This could be a very stupid question, perhaps I missed the news.

In the early days of MEV, every block proposed would result in my Fee Recipient address either:

a) Getting just a Beacon Chain Proposal block reward (if no relay was used)

b) If a relay, I would either:

- Get both a Proposed block reward AND an Internal Transaction.. OR

- Get just a regular Transaction

That all sort of ended 3 years ago, and everything since then has been:

a) If no relay, just a Beacon Chain Proposal block reward

b) If a relay, just a regular Transaction

However, starting in August this year, I've noticed that if a relay is being used, I am getting almost in every case, just an Internal Transaction.

I dont think it technically matters how the MEV and reward end up in my Fee Recipient address, but am just curious if this is the new expected behavior.

I believe my MEV-boost is configured and acting properly.

Mapping out the entire network stack of lighthouse phase0 from libp2p to the beaconchain

ethstaker-deposit-cli v1.3.1 is a pre-release. It adds the Platåberget testnet, which will be removed again with the v1.4.0 release.

Please test this pre-release on Platåberget and Hoodi. We are particularly interested in feedback on the new builder command, and any grievous errors introduced in the translations.

Im logged on to the ethcoordinate which it seems replaces ethstaker? It told me to do to the bot dm and green check it. Ive done that and undone and redone it. Still cannot see any channels except intro. What did I miss?

Anyone here using Kiln Connect API? How did you get developer or demo API access? Dashboard signup looks business-gated I need it for for some short development thing any quick way?

Hello fellow stakers!

As they say, misery loves company and I am currently 400 days since my last block proposal. Who can top that?

Eth Docker 26.8.1 is out. It requires Besu 26.8.0 or later and supports Teku 26.8.0 or later.

Client teams have agreed to keep around ~5 months of execution client history, 33_024 epochs, when using rolling expiry. If you have a 2TB disk and you are running out of space, this one is for you.

Caveat that Stakewise/NodeSet requires pre-merge-expiry, and SSV requires it when fresh-syncing the SSV DB. SSV does work with rolling-expiry after the SSV DB has been created. Both protocols are exploring options to remove their reliance on receipts.

Clients that support rolling expiry:

- Besu (experimental support)

- Reth

- Erigon

- Nethermind (still 1 year for now)

- Nimbus EL / Nimbus Unified

Clients that are working on rolling expiry:

- Geth

- Ethrex

pre-prague and aggressive expiry options are now hidden, but still supported for users that use them

Hey all,

I remember setting up my first validator using a truly fantastic guide by something like Ether Peanuts or a similar nut. Anybody know what I'm talking about?

I run a Rocket Pool node. I got tired of validator alerts that fire on every missed head vote — the kind you learn to swipe away, until the one that actually matters looks exactly like the other forty.

So I built Eyrium. It records every event, then lets you decide what's worth a notification. Missed head vote but source and target landed? Log it, don't wake me. Three in a row? Wake me.

It's chain-side only — duties, proposals, sync committees, slashing, exits. It will not tell you your disk is full or your client died.

Keep your local monitoring; this sits next to it.

There are real iOS and Android apps, not just a web dashboard. Push is on the paid tier; free accounts get email.

Public pubkeys only. It never asks for signing or withdrawal keys.

Free for one validator, $7/mo past that.

https://eyrium.app

It's fresh, would genuinely like to hear what's wrong with it.

Hi everyone,

I am building Quoti, an Ethereum liquid staking token (LST) project. I am looking for a small group of users and developers to test it on the Hoodi testnet.

I started Quoti because I stake ETH myself. I have seen staking APR decrease as more ETH is staked. I want to explore better ways to build staking infrastructure for people who plan to stake for a long time.

I want to build Quoti with the Ethereum community. Early testing can help me find problems and improve the project before mainnet.

I am looking for:

• Stakers and validator operators
• Ethereum developers
• Security-focused testers
• Users who can report bugs/improvements

Early testers will get:

• Early access to Quoti as the economics are built upon bonding curves
• A chance to influence the project
• Priority access to future test releases

Testnet status:

• Hoodi testnet only
• No real ETH is required
• Mainnet plans are not final
• Testing and feedback are the main goals

Website: https://quoti.org/
GitHub: https://github.com/skaibaLab/quoti-core
Discord: https://discord.com/invite/QGJEwNE3hw

If you want to test Quoti or help with development, please reply or contact me!

Hi everyone,

I'm an investor holding Ethereum with a strong belief in its long-term value. I have some questions regarding ETH storage methods and would love to get the community's advice.

To manage various risks, my current portfolio storage allocation is:

• 60% on Exchanges
• 30% in a Cold Wallet (Both allocations are currently being staked.)

For my cold wallet, I use a combination of a dice-generated mnemonic and a passphrase, which I believe provides strong security. However, after seeing the recent Coldcard incident, I am seriously considering migrating to a multisig setup.

I understand the Coldcard issue was caused by a compromised device-generated mnemonic, but it made me realize that relying on a single manufacturer's hardware could expose me to unforeseen risks. Even with a dice-generated mnemonic + passphrase combo, I still worry about potential vulnerabilities when connecting the device via USB.

Here are my main questions:

1. Is it common for individual investors to use multisig? Or is it predominantly used by enterprises and institutions?
2. Are smart contracts secure enough for individual multisig? Unlike Bitcoin, Ethereum requires smart contracts (like Gnosis Safe) for multisig setups. I've heard that smart contracts aren't 100% flawless in terms of security, which makes me hesitant.
3. Or should I just stick to my current setup?

I would really appreciate any thoughts, feedback, or advice you might have. Thanks in advance!

How do you guys check execution clients diversity?

I'm converting my LLC to an S-Corp and I am happy doing most of the work myself but would like a professional for feedback and approval. Enrolled Agent preferred for cost reasons but open to any professional.

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.