-
Notifications
You must be signed in to change notification settings - Fork 14
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
[multikey] Add multikey support #26
Conversation
Add multikey support, and deprecate JSON payloads. They're obsolete with BCS payloads.
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.
I guess I spent more of my time writing the multi ed.
Do we not have any serialized byte examples anywhere? Would love a unit test...
01fdcca
to
99673e4
Compare
I'm going to come back with some specs to verify the serialized byte examples. We unfortunately don't really have any / I need to make some |
data, signature | ||
), "Unable to verify signature" | ||
|
||
except Exception: |
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.
I think we shouldn't catch the exception here, otherwise the assert above will have no effect (don't know what happened)?
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.
I copied this from MultiEd25519, it's definitely not a great pattern to use. Will follow up with a PR afterwards to move this and MultiEd25519 into a two step process:
- One function to verify the signature and throw exceptions
- One function that wraps it and returns true or false
Co-authored-by: fishronsage <[email protected]>
Description
Add multikey support, and deprecate JSON payloads. They're obsolete with BCS payloads.
Test Plan
See example
Related Links