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

Investigate and mitigate the affect on block time a single validator can have #1038

Open
cmwaters opened this issue Jul 19, 2023 · 1 comment
Labels
ice-box issues are automatically assigned this label until they are planned.

Comments

@cmwaters
Copy link
Contributor

There's evidence in the mocha-3 network that a single validator (with less than a third of the voting power) can alter the block intervals of the blocks they produce by changing their local TimeoutCommit.

It is expected that at least 1/3 and as much as 2/3 (depending on how may signatures are present in the commit) of voting power should be required to alter block intervals. The fact that we can get a 3 second block when all but one validator has a TimeoutCommit set to 11 seconds is indicative that validators are continuing to vote on newly arrived proposals even while waiting for TimeoutCommit period from the previous height to pass.

It should be made mandatory that a node respect the full TimeoutCommit period before engaging in round 0 of the following height.

@cmwaters cmwaters self-assigned this Jul 19, 2023
@evan-forbes evan-forbes added this to the Post-mainnet milestone Jul 31, 2023
@evan-forbes evan-forbes added the ice-box issues are automatically assigned this label until they are planned. label Feb 21, 2024
@evan-forbes
Copy link
Member

can we close this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ice-box issues are automatically assigned this label until they are planned.
Projects
None yet
Development

No branches or pull requests

2 participants