fix: solve wrong response for account.verifyMessage #895
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.
Motivation and Resolution
implement issue #858 about wrong answers of
account.verifyMessage()
See issue for details.
Usage related changes
Breaking change : the result myAccount.verifyMessage(typedMessage, signature) is no more a boolean. It's now :
Example of usage :
Development related changes
There is no standard in Starknet for Cairo
IsValidSignature
account function response.0
in case of wrong signature.The code is adapted in accordance.
Checklist: