You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't believe this is a bug, it'll return "el_offline":true if it's not synced to head. if the execution client returns any errors it'll retry and the endpoint will return "el_offline":true
I've tested this endpoint with several clients before reporting it. lighthouse, lodestar, nimbus-eth2, and teku all report true initially, then false; however, prysm seems inconsistent with the other clients.
I have a work-in-progress branch where I test client configs against each other; if that helps, please check it out.
@james-prysm I don't think the sync status has anything to do with el_offline. All other clients initially return (true) then when execution client is connected they return false. If you disconnect (shut down the client), they change the status back to true.
I'm basing this on what I see happening when values are returned.
Describe the bug
Prysm returns true for
el_offline
after el connected, this should be false.Has this worked before in a previous version?
🔬 Minimal Reproduction
Connected to new endpoint endpoint=http://localhost:8551
See that the
el_offline
is true instead of falseFor this test, I have included besu, but same result with erigon/geth/nethermind/reth. All other CL client will return
false
when EL is connected.Error
No response
Platform(s)
Linux (x86)
What version of Prysm are you running? (Which release)
beacon-chain version Prysm/v5.0.4/3b184f43c86baf6c36478f65a5113e7cf0836d41. Built at: 2024-06-21 00:26:00+00:00
Anything else relevant (validator index / public key)?
No response
The text was updated successfully, but these errors were encountered: