Repository navigation
NUT-29: use valid curve points in the batch mint example - #405
Merged
Merged
Conversation
Two example output B_ values were not valid secp256k1 points, which trips implementations that validate points on parse.
15 of 69 tasks
61 tasks
Collaborator
Author
|
@ye0man - this doesn't need assigning, just merging, and that needs an approving review |
8 of 70 tasks
callebtc
approved these changes
Sep 15, 2026
69 tasks
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
3 participants
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.
Two output
B_values in the batch mint request example are not valid secp256k1 points, so implementations that validate points on parse (e.g. cdk) would reject the example verbatim. Replaces them with the compressed points for the well-known test keys02and03.Found while pinning the vectors for #404.