DPoS 3.0: Integrate DPoS with ChainedBFT #347
Merged
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
qizheng09
reviewed
Sep 6, 2019
data/config/xuper_bft.json
Outdated
| ] | ||
| }, | ||
| "bft_config": { | ||
| "netMsgChanSize": 1000 |
There was a problem hiding this comment.
Maybe it would be better to configure it as a node config.
There was a problem hiding this comment.
Removed this field from consensus config
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.
Description
This PR is to implement DPoS V3.0, which integrate with Chained-BFT to be able to deal with Byzantine Fault Tolerance. The main advantages of DPoS V3.0 are:
Fixes #309
Type of change
Please delete options that are not relevant.
Brief of your solution
By using Chained-BFT(HotStuff), DPoS core peers can collect 2/3 votes on new block in O(n) communication complexity in a chained workflow. So that each block cannot be rollback after 3 blocks' confirmation.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration