Skip to content

Handle multiple proposals in a view correctly in Tendermint #1793

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

Merged
merged 2 commits into from
Sep 26, 2019

Conversation

majecty
Copy link
Contributor

@majecty majecty commented Sep 24, 2019

The previous code assumes that there is only one proposal in a
view. Tendermint was always using the first proposal even though there
are many proposals in a view. This commit makes Tendermint find the
proper proposal for that situation.

Fixes #1773

@majecty majecty requested a review from foriequal0 September 24, 2019 09:39
@majecty majecty force-pushed the f/assume-doublevote branch from d448428 to ce4d818 Compare September 24, 2019 10:07
@majecty majecty changed the title Handle double voted proposals correctly in Tendermint Handle multiple proposals in a view correctly in Tendermint Sep 24, 2019
@majecty majecty force-pushed the f/assume-doublevote branch from ce4d818 to e2dbe6b Compare September 26, 2019 05:18
@majecty majecty force-pushed the f/assume-doublevote branch from e2dbe6b to 0c68995 Compare September 26, 2019 06:18
@majecty majecty force-pushed the f/assume-doublevote branch from 27faf27 to fd162f3 Compare September 26, 2019 06:29
foriequal0
foriequal0 previously approved these changes Sep 26, 2019
Previous code assumes that there is only one proposal in a
view. Tendermint was always using the first proposal even though there
are many proposals in a view. This commit makes Tendermint find
proper proposal in the situation.
When there are multiple proposals, we want to use the first proposal
consistently. To do that the order or votes should be consistent.
@majecty majecty merged commit f805518 into CodeChain-io:master Sep 26, 2019
@majecty majecty deleted the f/assume-doublevote branch September 26, 2019 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Don't assume that valid proposal is always one in one round
2 participants