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

Byzantine faulty nodes #83

Open
chenkung opened this issue Feb 2, 2017 · 0 comments
Open

Byzantine faulty nodes #83

chenkung opened this issue Feb 2, 2017 · 0 comments

Comments

@chenkung
Copy link

chenkung commented Feb 2, 2017

When there are Byzantine faulty nodes, the consensus process may hang under certain situation.
Specifically, when the non-faulty nodes are divided into Quorum and QuorumPossible states, respectively, and the next proposer node is one that in QuorumPossible state, the consensus process will hang. Please refer to the attached file for an example scenario with four nodes.

HydrachainProblem.pptx
We suspect that this is due to the kind-of optimization for normal cases that Hydrachain consensus introduced to BFT consensus. That is, nodes with Quorum state may commit the block directly. We propose to resolve this issue as follows. When the nodes with QuorumPossible state receive VoteNil from nodes of Quorum state (H+1), they should not ignore them, but, instead, request block-sync from those Quorum nodes so that they will reach height H+1, too.

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

No branches or pull requests

1 participant