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

Bug: Timestamp is 19 seconds off #50

Closed
gitmachtl opened this issue Jan 11, 2022 · 3 comments · Fixed by #101
Closed

Bug: Timestamp is 19 seconds off #50

gitmachtl opened this issue Jan 11, 2022 · 3 comments · Fixed by #101
Assignees
Labels
bug Something isn't working
Milestone

Comments

@gitmachtl
Copy link

gitmachtl commented Jan 11, 2022

Testnet Example:
The output for block 3226895 is reported with the timestamp 1641849006.
If i convert this back into an actual date like date --date="@1641849006" i get the date Mon, 10 Jan 2022 22:10:06.
DB-Sync/Explorers report Mon, 10 Jan 2022 22:10:25

So there is a 19 seconds offset. And its for all the reported blocks. So either i am converting it wrong, or there is a Bug?

@mark-stopka
Copy link
Collaborator

Probably mistake in well known info...

shelley_known_time: 1595967596,

@mark-stopka mark-stopka added the bug Something isn't working label Jan 11, 2022
@gitmachtl
Copy link
Author

Its also off 19 seconds on mainnet.

@scarmuega
Copy link
Member

Event timestamps are inferred from the slot number of the block, but there seems to be some ambiguity on how to translate the interval length between blocks (~20 secs ATM). I found this comment by @KtorZ very insightful:

CardanoSolutions/ogmios#3 (comment)

TBH, I'm not happy with the current approach in Oura. I'll do some reverse engineering on db-sync to understand the logic it uses.

@scarmuega scarmuega moved this to Refinement in Oura Development Jan 24, 2022
@scarmuega scarmuega moved this from Refinement to Todo in Oura Development Jan 24, 2022
@scarmuega scarmuega moved this from Todo to In Progress in Oura Development Jan 24, 2022
@scarmuega scarmuega added this to the v1.1 milestone Jan 24, 2022
@scarmuega scarmuega self-assigned this Jan 24, 2022
@mark-stopka mark-stopka linked a pull request Jan 25, 2022 that will close this issue
Repository owner moved this from In Progress to Done in Oura Development Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants