fix: signer uniqueness checking #122
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
Rayerleier
previously approved these changes
Oct 11, 2024
sosaucily
reviewed
Oct 11, 2024
sosaucily
previously approved these changes
Oct 11, 2024
scolear
force-pushed
the
fix/signer-checking
branch
from
a2806b8 to
52e8b3d
Compare
Polybius93
approved these changes
Oct 16, 2024
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.
A new mapping which stores signer uniqueness for a given message hash. It ensures that the same signers can submit signatures for different messages (since the
messagefields are unique inbtcTxId), but not for the same one.