-
Notifications
You must be signed in to change notification settings - Fork 205
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
Optimistic signature aggregation by leader #4123
Merged
AdoAdoAdo
merged 26 commits into
feat/optimise-consensus-sigcheck
from
optimistic-sig-aggregation-on-consensus
Jun 27, 2022
Merged
Changes from 24 commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
43e7961
verify aggregated sig on end round by leader
ssd04 1125da5
verify aggregated sig on end round by leader: use current multi signer
ssd04 bd320be
added verify signature share if aggregated sig failed
ssd04 cdc4cd2
remove unit test for verify signature share
ssd04 af62643
verify sig share on fail, for nodes based on bitmap
ssd04 d8827be
handle err case on setInderInBitmap
ssd04 4b89afd
use signature subround jobs state instead of using custom bitmap
ssd04 b04812a
added unit tests for verify signature shared on agg sig verification …
ssd04 33e778b
use new temp multisigner to store only valid sig shares
ssd04 fcfee88
fix issues with multisigner saved state
ssd04 c222360
avoid resetting multiSigner data
ssd04 a3d5e90
return updated bitmap and aggregated signature
ssd04 f649a5f
remove store signature since multisigner is not reset anymore
ssd04 331bea8
update unit test to return more variables
ssd04 9973538
added separate function for agg sig after verification fail
ssd04 4650415
handle lower than threshold case when verification fail; remove log d…
ssd04 1b77058
unit tests for compute agg sig on valid nodes
ssd04 c5a24ad
cleanup log debug messages
ssd04 cdc7a39
added TODO for invalid sig shares slashing
ssd04 cc06e98
unit test for endround job by leader with verification fail
ssd04 b566237
fix commented unit test
ssd04 e129882
endRound unit test: verify num calls for verifySigShare
ssd04 4961c7a
fixes after review:
ssd04 291b6f9
decrease peer honesty for malicios signer, since it has been increase…
ssd04 fd192e7
include also increase factor since it was added optimistically
ssd04 31114b8
revert: use only increase factor
ssd04 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
also the sr.PeerHonestyHandler() should be decreased? maybe twice? It was increased once on the receivedSignature and now it was found it is invalid.
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.
👍 will include in the next PR when slashing will be applied
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.
as discussed, decreased peerHonesty here to be in line with the old setup, since the peerHonesty has been increased optimistically for the malicious signer