-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add configurable threshold for 'future block' check #800
Add configurable threshold for 'future block' check #800
Conversation
… issue-792-add-allowedFutureBlockTime
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some nitpicks in code. Also please run goimports
for the modified files
….com/SatpalSandhu61/quorum into issue-792-add-allowedFutureBlockTime
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Temporarily closing this PR as I want to make the parameter name generic, not just for Istanbul. |
…Time' into issue-792-add-allowedFutureBlockTime
PR has been reopened with changes to make it more generic and include Clique. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes #792
Added configurable threshold for 'future block' check, in order to avoid spurious "block in the future" messages for Istanbul and Clique.
Threshold is specified in seconds, using
--allowedfutureblocktime
command line argument.Note that there is a similar change for ethash in upstream geth (albeit a fixed threshold, not configurable): https://github.com/ethereum/go-ethereum/blob/master/consensus/ethash/consensus.go#L248