txscript: implement proposed Elliptic Curve op codes #2413
+2,337
−14
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
In this commit, we create some test vector infra for the EC op tests. With this, we'll use a build tag to control if we write certian unit tests as test vectors on disk or not. If we're generating test vectors, then we make sure to always generate the same set of keys each time.
These use the same format as the Taproot ref tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In this PR, we implement op codes for a newly propoosed soft fork. Amongst other things, this suite of opcodes permits the computation of the top level Taproot output public key, which paves the way for a new breed of on-chain state machine when combined with other introspection capabilities.