Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

weird genesis timestamp for topaz #5448

Closed
tzapu opened this issue Apr 15, 2020 · 2 comments
Closed

weird genesis timestamp for topaz #5448

tzapu opened this issue Apr 15, 2020 · 2 comments
Labels
Bug Something isn't working Help Wanted Extra attention is needed

Comments

@tzapu
Copy link
Contributor

tzapu commented Apr 15, 2020

i've just setup a new node and tried to query for the genesis timestamp
the http api gives me

$ curl -X GET "http://localhost:3001/eth/v1alpha1/node/genesis" -H  "accept: application/json"
{"genesisTime":"0001-01-01T00:00:00Z","depositContractAddress":"XKHgAAQ2ashfSSiHqqsS0OZBiHY="}

and over grpc GetGenesis(...).GetGenesisTime().GetSeconds() returns -62135596800

neither is ideal :D

@prestonvanloon
Copy link
Member

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.

@prestonvanloon prestonvanloon added Bug Something isn't working Help Wanted Extra attention is needed labels Apr 16, 2020
@rauljordan
Copy link
Contributor

Done by #6031

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Help Wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants