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 feedback for peer honesty in consensus #1979
Add feedback for peer honesty in consensus #1979
Conversation
SebastianMarian
commented
Jun 18, 2020
- Added a consensus rating mechanism to handle the situation when some peers would flood the consensus topic with invalid messages
- Fixed an uncovered situation in which a blacklist should be applied for both, originator and the connected peer, if an invalid message would be received on consensus topic
…e peers would flood the consensus topic with invalid messages * Fixed an uncovered situation in which a blacklist should be applied for both, originator and the connected peer, if an invalid message would be received on consensus topic
consensus/spos/bls/subroundBlock.go
Outdated
@@ -589,3 +559,21 @@ func (sr *subroundBlock) getRoundInLastCommittedBlock() int64 { | |||
|
|||
return roundInLastCommittedBlock | |||
} | |||
|
|||
func (sr *subroundBlock) updateLeaderPeerHonesty(node string) { |
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.
Duplicate code with subroundEndRound. Suggestion to move this in Subround struct.
@@ -279,3 +269,21 @@ func (sr *subroundSignature) remainingTime() time.Duration { | |||
|
|||
return remainigTime | |||
} | |||
|
|||
func (sr *subroundSignature) updateValidatorPeerHonesty(node string) { |
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.
This can also be moved in Subround struct
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.
Forgot to say anything about testing the 2 new functions UpdateValidatorPeerHonesty and UpdateLeaderPeerHonesty. Can be done later.
* Refactored Increase adn Decrease mechanism * Fixed a blcklisted situation which should not be done
aabbad1
…huffling out state (self shard ID could be reported differently for a while, max. 25% from an epoch time, by shard coordinator and by nodes coordinator)
…-consensus' into add-feedback-for-peer-honesty-in-consensus
…ocess on time the epoch start block
…-consensus' into add-feedback-for-peer-honesty-in-consensus
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.
System tests passed.