-
Notifications
You must be signed in to change notification settings - Fork 26
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
Added verify_signature
function to kernel
#800
base: main
Are you sure you want to change the base?
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Would be nice to have an on-chain test for this |
On chain test was done using separate repo. |
Motivation
Add
verifiy_signature
function that is used to validate if given message is signed by specified address.Implementation
secp256k1_verify
function to verify thatmsg
was signed bysigner_addr
public_key
is used forsignature
validationInvalidSigner
error in case address generated frompublic_key
does not matchsigner_addr
address_prefix
is currently used for address generating process usingpublic_key
Testing
verify_signature
function