We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
macroblock
window_size
I have observed that the election block timestamp is shifting backwards ~10 minutes every day.
Block: 4665600 Timestamp: 1733322410163 Date: 2024-12-04T14:26:50.163Z Block: 4708800 Timestamp: 1733364958635 Date: 2024-12-05T02:15:58.635Z Block: 4752000 Timestamp: 1733407518777 Date: 2024-12-05T14:05:18.777Z Block: 4795200 Timestamp: 1733450065261 Date: 2024-12-06T01:54:25.261Z Block: 4838400 Timestamp: 1733492613389 Date: 2024-12-06T13:43:33.389Z
By @Albermonte
Knowing that the epoch last 11 hours and 50 minutes instead of 12 hours, should we modify the VTS algorithm?
Currently the window size is being calculated as follows:
I would suggest to modify epoch_duration to use microblocks only:
epoch_duration
microblocks
$$ epoch duration = block duration * microblocks per epoch $$
The text was updated successfully, but these errors were encountered:
Albermonte
No branches or pull requests
I have observed that the election block timestamp is shifting backwards ~10 minutes every day.
By @Albermonte
Knowing that the epoch last 11 hours and 50 minutes instead of 12 hours, should we modify the VTS algorithm?
Currently the window size is being calculated as follows:
I would suggest to modify
epoch_duration
to usemicroblocks
only:The text was updated successfully, but these errors were encountered: