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
At the time of writing, this validator has been offline for ~3 days. The UI correctly shows the last successful attestation at slot 3385673 (correct):
However, the API response is reporting this validator as active_online (rather than active_offline) with the last successful attestation at slot 3407476 (incorrect):
Thanks for reporting this issue. After an internal investigation we have identified and fixed the relevant bug that triggered this issue, see gobitfly/beaconchain#1264 for further details.
We are sorry for the inconvenience this bug may have caused.
Example Holesky validator:
0x91d82644e98c3ed65acc6d4f795c13ad40a7067fdad5fb24193a5fc3dd48dfe6a8c0a82a944faf81b341caa0a4f723f9
At the time of writing, this validator has been offline for ~3 days. The UI correctly shows the last successful attestation at slot
3385673
(correct):However, the API response is reporting this validator as
active_online
(rather thanactive_offline
) with the last successful attestation at slot3407476
(incorrect):If I had to estimate, I would say this issue started within the last week or so.
The text was updated successfully, but these errors were encountered: