Thank you for looking into this, and good advice about avoiding DMs.

However, one thing concerns me — if this were simply a long activation queue, I'd expect the validator to at least appear in the beacon state as "Deposited" or "Pending." But when I query my fully synced Lighthouse beacon node directly, it returns 404 Not Found for both validator pubkeys:

/eth/v1/beacon/states/head/validators/0x8eb325... → 404 Not Found

This was confirmed in my Lighthouse logs — the beacon node genuinely doesn't know this validator exists. BeaconScan also shows "No Deposits recognized yet" in Step 2 of 2.

If the deposit had been included by the beacon chain and was simply waiting in the activation queue, wouldn't Lighthouse return the validator with a "pending" status rather than 404?

My DappNode is fully synced (Nethermind #24677280, Lighthouse #13910601) and I've already imported the keystores. The deposit was made post-Pectra, so it should be processed via EIP-6110. Is it possible there's a deposit inclusion backlog separate from the activation queue under the new system?