feat: verify the block delay on broadcasted blocks #193
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
minh-bq
force-pushed
the
feat/check-header-time
branch
from
8d55479 to
7df949f
Compare
trantienduchn
approved these changes
Jan 5, 2023
minh-bq
force-pushed
the
feat/check-header-time
branch
from
7df949f to
0be2453
Compare
linh-1
approved these changes
Jan 5, 2023
This commit follows the approach of Ramanujan in BSC which includes the block delay in block timestamp for verification on the recipients. The block timestamp is calculated by the formula - block timestamp = max(parent timestamp + block duration + backoff time, current timestamp) The block duration is 3s in the current configuration. When the validator is inturn, the backoff time is 0, otherwise, each out of turn validator has a different delay. The delay equals to - delay = wiggle + (random multiplier * wiggle/2) The random multiplier is in range [1, len(current validators)]. The random seed is the block number, the recipient can use the same seed to get the same random result for verification.
minh-bq
force-pushed
the
feat/check-header-time
branch
from
0be2453 to
9bf6470
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit follows the approach of Ramanujan in BSC which includes the block
delay in block timestamp for verification on the recipients.
The block timestamp is calculated by the formula
current timestamp)
The block duration is 3s in the current configuration. When the validator is
inturn, the backoff time is 0, otherwise, each out of turn validator has a
different delay.
The delay equals to
The random multiplier is in range [1, len(current validators)]. The random seed
is the block number, the recipient can use the same seed to get the same random
result for verification.