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
We saw the same thing on https://prylabs.net. I think this might be an issue with grpc / json transcoding. It is likely that the beacon node reported 0 as the genesis start time and it was somehow converted to this ridiculous timestamp.
In any case, this is unacceptable behavior for pre-genesis beacon node reporting. We'll have to find some alternative solution.
i've just setup a new node and tried to query for the genesis timestamp
the http api gives me
and over grpc
GetGenesis(...).GetGenesisTime().GetSeconds()
returns-62135596800
neither is ideal :D
The text was updated successfully, but these errors were encountered: