Expose typed CheckSigFromStack builtins#132
Open
elldeeone wants to merge 2 commits into
Open
Conversation
This file contains hidden or 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
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.
Summary
Adds typed SilverScript builtins for Kaspa signature verification from stack:
CheckSigFromStack(datasig signature, byte[32] digest, pubkey publicKey)CheckSigFromStackECDSA(datasig signature, byte[32] digest, byte[33] publicKey)These expose the digest-level VM primitives directly, so contracts can choose the hashing scheme they need before passing a fixed 32-byte digest.
Changes
CheckSigFromStacktoOP_CHECKSIGFROMSTACK.CheckSigFromStackECDSAtoOP_CHECKSIGFROMSTACKECDSA.byte[32]digest instead of accepting rawbyte[]messages.Testing
npm --prefix tree-sitter run sync:highlightscargo test -p silverscript-lang checksig -- --nocapturecargo test -p silverscript-langcargo fmt --all --checkgit diff --check