1757092821 #64
Closed
jaymansfield
started this conversation in
Trace
Replies: 2 comments
-
|
Comparison against wall clock time should be disabled during fuzzing as it doesn't make much sense. Another deviation: we start from an arbitrary slot X (typically 0), we do not use the slots since Jam epoch according to wall clock. In practice, it is enough to check whether the current slot is greater than the parent. Thanks for pointing this out - these notes should be added to the fuzz protocol spec. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks @davxy |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My implementation rejects this block due to its slot being in the future.
It uses slot # 20973629, and with the jam common era as of right now brings us to approx slot #3561787.
Is this a defect for others that imported, or should this check be disabled while fuzzing @davxy ?
Beta Was this translation helpful? Give feedback.
All reactions