BlockNuggets Logo

BlockNuggets

Home
/
Technology updates
/
Decentralized applications
/

64 eth stuck: two validator deposits ignored for 35 days

64 ETH Stuck | Validator Deposits Ignored for Over a Month

By

Maximilian Müller

Mar 22, 2026, 06:19 AM

Edited By

Oliver Brown

Updated

Mar 22, 2026, 01:45 PM

2 minutes needed to read

A frustrated solo staker looks at his screen, showing 64 ETH stuck in pending deposits, with charts and data in the background.

A solo staker is in a frustrating predicament as two validator deposits of 64 ETH are trapped, unprocessed by the Beacon Chain for more than 35 days. This situation highlights ongoing concerns about the Ethereum staking system's reliability and challenges users face.

The Situation Unfolds

On February 15, 2026, the staker, utilizing DappNode with Nethermind and Lighthouse, made the two deposits. Despite multiple verifications indicating everything is correct—from BLS signatures to on-chain data—neither deposit has registered on the Beacon Chain.

Transaction Details

  • Validator 1 TX Hash: 0x99cc4593e95ea771a3f3a2186ab09468c88e4de9d7a15a55ffab56c8dc491b42

  • Validator 2 TX Hash: (Details available, ensuring transparency.)

Verification Efforts

Efforts to confirm the integrity of the deposits reveal:

  • BLS Signatures: Validated for both validators.

  • Transaction Matching: On-chain data has matched all required fields.

  • Deposit Events: Valid DepositEvent emitted confirming deposit details.

User Insights and Concerns

Feedback from forums indicates shared frustrations:

"35 days with 64 ETH in limbo is brutal, sorry you’re dealing with this."

Several commenters pointed out issues like:

  • Processing Bottlenecks: The entry queue for ETH shows a backlog of 3,020,450, with estimated waiting times of 52 days.

  • System Delays: A user mentioned that delays are common with some deposits taking over 70 days and advised ensuring full node synchronization.

  • Seeking Help: Users suggested checking if the Beacon Chain recognizes the public keys and posting in the Lighthouse Discord, noting that their team responds promptly to edge case issues with certain credentials.

Theories Behind the Delay

Discussions in the community propose several theories:

  1. Client Implementation Issues: Delays could stem from processing validator deposits using 0x02 withdrawal credentials.

  2. Execution Layer Delays: The current system likely has a backlog affecting recent deposits made post-Pectra upgrade.

  3. Compatibility Issues: Users speculate that issues may arise from using both Nethermind and Lighthouse together.

What’s Next?

With no substantial resolution insights, the staking community awaits clarity from the Ethereum team. This ongoing incident could either lead to continual delays for the staker's 64 ETH or spark necessary adjustments in the processing system to prevent future issues.

Key Takeaway Points

  • 🔍 Average waiting time for deposits is currently at around 52 days, with some users facing delays over 70 days.

  • ⚡ Community voices urge exploration of alternative solutions while this problem persists.

  • 💬 "You should cross-reference the tx to see if the Beacon chain recognizes the pubkeys, there are solutions out there" - A forum user suggests.

Ethereum’s staking framework is under pressure as the complexities of validator deposit processing come to light. If these issues persist, new stakers may seek alternatives, potentially shaking up the demographic landscape of the Ethereum network.