Deposits Not Being Processed - 17+ Hours Delay
Problem Description
I made 20 validator deposits on Gnosis Chain approximately 17 hours ago, but they have not been picked up by the beacon chain. The deposits are confirmed on the execution layer but are not appearing in the beacon state.
Technical Details
Deposit Information:
- Number of validators: 20
- Deposit block: 47468606
- Deposit contract: 0x0B98057eA310F4d31F2a452B414647007d1645d9
- Time elapsed: ~17 hours (as of 2026-07-31 09:00 UTC)
- Transaction hash: 0x5ceb0a1b3f5749605208c9a2d5f4f232c72d1bd1d4dec94ae32e2fe74b574d77
- Transaction status: Success (batch deposit of 20 validators in 1 transaction)
- Deposit events in logs: 22 (20 validators + 2 other events)
- From address: 0xd5dc84e04a12cd8613635f0d47e13aabc896372e
Beacon Chain Status:
- Beacon node is fully synced (sync distance: 0)
beacon_eth1_deposit_totalmetric: 0.0 (receiving zero deposits)beacon_eth1_block_cache_sizemetric: 0.0 (no eth1 monitoring)- Public explorers (dora.gnosischain.com) show “Not Found” for all validators
- Local activation queue shows 6 pending validators, none are ours
Configuration:
- Execution client: Nethermind 1.39.0
- Consensus client: Teku (latest)
What We’ve Verified
Deposit transactions are confirmed on-chain
Deposit contract address is correct
Deposit amounts are correct (1 GNO per validator)
Beacon node is synced and healthy
Execution client is synced and responding to requests
No recent deposits on the network in the last 1000 blocks
Beacon is not monitoring eth1 (cache size = 0)
Validators not appearing in beacon state
What We’ve Tried
- Restarted the entire node (Nethermind + Teku)
- Verified beacon can connect to execution engine
- Checked public explorers - validators not found
- Monitored beacon metrics - no deposit activity
Questions
- Is there a known issue with deposit processing on Gnosis Chain currently?
- Are other validators experiencing similar delays?
- Is there additional configuration needed for Teku to monitor deposits in post-merge?
- Should we wait longer, or is there an action we should take?
- Is there a way to manually trigger deposit processing?
Additional Information
- No errors in beacon logs related to deposits
- Execution client logs show normal operation
- Network appears healthy (producing blocks, finalizing)
- This is a fresh validator setup (first time depositing these keys)
Request
Any guidance on resolving this issue would be greatly appreciated. We want to ensure we don’t take any actions that could result in duplicate deposits or loss of funds.
Thank you for your help!
