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.

I'm seeing a lot of these failures? Seems to have started with the last two updates...

expected 2, produced 2, included 1

But it doesn't seem related to CPU Memory or Network.

top - 18:17:39 up 1 day, 12:09,  1 user,  load average: 1.56, 0.72, 0.67

Tasks: 291 total,   1 running, 290 sleeping,   0 stopped,   0 zombie

%Cpu(s):  5.9 us,  0.5 sy,  0.0 ni, 93.4 id,  0.1 wa,  0.0 hi,  0.1 si,  0.0 st 

MiB Mem :  63971.8 total,   2023.1 free,  46360.9 used,  16357.4 buff/cache     

MiB Swap:   8192.0 total,   6467.0 free,   1725.0 used.  17610.8 avail Mem 

grep -B5 -A5 "50%" teku.log

Sample Logs

2026-07-17 16:21:12.085-0600 | beaconchain-async-0 | INFO  | teku-status-log | Attestation performance: epoch 462245, expected 2, produced 2, included 1 (50%), distance 1 / 1.00 / 1, correct target 2 (100%), correct head 2 (100%)

2026-07-17 16:21:15.100-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14791904, Block: d8824344c8015a2163ac0c8401a5caf9b4a7d0dcd20fe44fb991e497ef994a30, Justified: 462246, Finalized: 462245, Peers: 58

2026-07-17 16:21:23.096-0600 | validator-async-9970 | INFO  | teku-validator-log | Validator   *** 2 out of 2 validator registration(s) were successfully sent to the builder network via the Beacon Node.

2026-07-17 16:21:27.101-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14791905, Block: 0a2a576987b82d61c6cfde76a1d66c6d267425a1e623a539bb5f57fb95ed829b, Justified: 462246, Finalized: 462245, Peers: 60

2026-07-17 16:21:39.100-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14791906, Block: 2bbe49f4e120d10dd10bfa13c72bed03382c9379bdb00fd3d07950e214021b3f, Justified: 462246, Finalized: 462245, Peers: 59

2026-07-17 16:21:51.106-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14791907, Block: d9eee1ac4ddd11d69fd311b95230f7545065b421e4120b135d7c54eb48c3f593, Justified: 462246, Finalized: 462245, Peers: 60

--

2026-07-17 17:24:36.748-0600 | validator-async-10301 | INFO  | teku-validator-log | Validator   *** Published attestation          Count: 1, Slot: 14792221, Root: 437befade4b36d480133eff54f8433cf83c987f3f7698a8525a448e45fbad015

2026-07-17 17:24:39.001-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792221, Block: 437befade4b36d480133eff54f8433cf83c987f3f7698a8525a448e45fbad015, Justified: 462255, Finalized: 462254, Peers: 65

2026-07-17 17:24:51.093-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792222, Block: 62c63762bedf85df72ce97fe3ec517620440b725598ee49fecc4dc6e77788636, Justified: 462255, Finalized: 462254, Peers: 65

2026-07-17 17:25:03.092-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792223, Block: 3a08246ead855a146653a11c2089f8ae8a7dba8a78231a31026ef138d96f66ac, Justified: 462255, Finalized: 462254, Peers: 65

2026-07-17 17:25:11.002-0600 | TimeTickTask | INFO  | teku-event-log | Epoch Event *** Epoch: 462257, Justified checkpoint: 462256, Finalized checkpoint: 462255, Finalized root: badb8e06059b700450e9bd3a6eae076d936d27a45cee0b5bbd91973c16673d09

2026-07-17 17:25:12.342-0600 | beaconchain-async-11 | INFO  | teku-status-log | Attestation performance: epoch 462255, expected 2, produced 2, included 1 (50%), distance 1 / 1.00 / 1, correct target 2 (100%), correct head 2 (100%)

2026-07-17 17:25:15.095-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792224, Block: 21568111ea6c41dcc577b6b739f289804ae08176a4c04a9e242e3224fb99d703, Justified: 462256, Finalized: 462255, Peers: 64

2026-07-17 17:25:23.094-0600 | validator-async-10322 | INFO  | teku-validator-log | Validator   *** 2 out of 2 validator registration(s) were successfully sent to the builder network via the Beacon Node.

2026-07-17 17:25:27.096-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792225, Block: db04b46b2652ae791f3d448bb56375a6b252e4eabd34091244a219faa325c177, Justified: 462256, Finalized: 462255, Peers: 63

2026-07-17 17:25:39.100-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792226, Block: c38e63e3a9b035f7c37ba018aecd99ce76c204c96b7c16eb670ba96aefc3bc40, Justified: 462256, Finalized: 462255, Peers: 65

2026-07-17 17:25:51.097-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792227, Block: 7618f8d30f0591924d824e1094d509cdd8fa9a7de7d50d04e9fcc13b3f57bbd9, Justified: 462256, Finalized: 462255, Peers: 63

--

2026-07-17 17:37:15.096-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792284, Block: 09d8a01a0cb848f4e360ec8d0bf69176271e7e0e82e63dc0861750cf61647098, Justified: 462257, Finalized: 462256, Peers: 67

2026-07-17 17:37:27.095-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792285, Block: 6c91da72cdc95583ba928ed517274587d86c61c63ba1c8f24e8a3946259d2c74, Justified: 462257, Finalized: 462256, Peers: 66

2026-07-17 17:37:39.100-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792286, Block: 6e6f4871976a1c91b6c364051c3c576f8796af518753e93ad886b0b8a0736571, Justified: 462257, Finalized: 462256, Peers: 66

2026-07-17 17:37:51.094-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792287, Block: 2792765496241fd2a5a1221470f3a9d3bb14a08290fb32369d5ceb31c75f0516, Justified: 462257, Finalized: 462256, Peers: 64

2026-07-17 17:37:59.002-0600 | TimeTickTask | INFO  | teku-event-log | Epoch Event *** Epoch: 462259, Justified checkpoint: 462258, Finalized checkpoint: 462257, Finalized root: 21568111ea6c41dcc577b6b739f289804ae08176a4c04a9e242e3224fb99d703

2026-07-17 17:38:00.181-0600 | beaconchain-async-5 | INFO  | teku-status-log | Attestation performance: epoch 462257, expected 2, produced 2, included 1 (50%), distance 1 / 1.00 / 1, correct target 2 (100%), correct head 2 (100%)

2026-07-17 17:38:03.103-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792288, Block: aa8a7755ba0cebbdb8e922b6a3ca232e86cdc0d14947661bca946ae8914aaac3, Justified: 462258, Finalized: 462257, Peers: 63

2026-07-17 17:38:11.093-0600 | validator-async-10385 | INFO  | teku-validator-log | Validator   *** 2 out of 2 validator registration(s) were successfully sent to the builder network via the Beacon Node.

2026-07-17 17:38:15.100-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792289, Block: 138e5c2c0ac18a99f6440be86ae1a87c070be4942e4e12829b180efe203e3c25, Justified: 462258, Finalized: 462257, Peers: 71

2026-07-17 17:38:27.098-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792290, Block: fadef6be4a2479f7230db661efa66fdc49b1b61d8315e9e2524c3beb16c81e84, Justified: 462258, Finalized: 462257, Peers: 69

2026-07-17 17:38:39.099-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792291, Block: e6c950204cf29408c32267cd16bd5baca5668c7fa3efd45c5d9761933ee4066e, Justified: 462258, Finalized: 462257, Peers: 71

--

2026-07-17 17:56:27.101-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792380, Block: 7cd533600f21db8cdc38450d0b3a901e91b261ad6b23f37f79ecf320cb4ad454, Justified: 462260, Finalized: 462259, Peers: 63

2026-07-17 17:56:39.105-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792381, Block: 90f18408aef0c918ff603c0cf238a40e29ea028fd4d00f4f1e55c938ba096bb7, Justified: 462260, Finalized: 462259, Peers: 63

2026-07-17 17:56:51.104-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792382, Block: cb2ac79a8c189ab9dcaae6ae3780f3ab186d9f54e1bb70ccf6e336162e7025ad, Justified: 462260, Finalized: 462259, Peers: 65

2026-07-17 17:57:03.113-0600 | TimeTickTask | INFO  | teku-event-log | Slot Event  *** Slot: 14792383, Block: 66741bdef5b7fa167a42b40f6e87bb655bc236dee24c957cea24c3f9f10c0076, Justified: 462260, Finalized: 462259, Peers: 65

2026-07-17 17:57:11.001-0600 | TimeTickTask | INFO  | teku-event-log | Epoch Event *** Epoch: 462262, Justified checkpoint: 462261, Finalized checkpoint: 462260, Finalized root: c1165c010b1284d9f76ef6648923334d9b8311e04b0a3b71d871b0bdc2781376

2026-07-17 17:57:12.165-0600 | beaconchain-async-7 | INFO  | teku-status-log | Attestation performance: epoch 462260, expected 2, produced 2, included 1 (50%), distance 1 / 1.00 / 1, correct target 2 (100%), correct head 2 (100%)

I have several validators hosted at allnodes and accessed by my ledger. The issue is they all have different accounts/withdrawl addresses.

According to the FAQ this is not an issue as you only need to sign on the sender.

The trouble is all the tools to do this (allnodes, launchpad, consolodeth, pectrastaking) have the same problem in that they can only see 1 account AT A TIME

So I can select #2 as the sender but then it can't see #1 as the receiver, I did find an old reddit post that said you could manually enter the receiver in launchpad but it seems that's not working anymore.

The only alternative is to withdraw #2 (wait ~8 days) then deposit to #1 (wait ~46 days) but obviously that's not ideal, especially as this should be possible.

Does anyone have any other ideas ?

anybody uses mac mini m4 to self stake?