-
Notifications
You must be signed in to change notification settings - Fork 149
Descriptor: Add support for confidential descriptors #493
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
Merged
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
There is no need to use the node flags since the entire descriptor is either Elements or not.
This key is reused in the ELIP-150 tests so give it a short name to make the test easier to read.
These are not documented anywhere and are only implemented in rust-miniscript, which renames descriptor builtins to be prefixed with "el" - making them incompatible with any descriptor currently supported by Elements core. However the test vectors from ELIP-0150 include elsh(wpkh()) expressions in addition to elwpkh() expressions, which seems to indicate that mixing prefixed and non-prefixed builtins should be accepted. This implementation therefore allows mixing prefixed and non-prefixed builtins, with the descriptor being marked as Elements if either a prefixed builtin is given, or if the descriptor is explicitly parsed as Elements via WALLY_MINISCRIPT_AS_ELEMENTS.
Allows callers to avoid doing the private-to-public key conversion themselves.
…ddresses Add the slip77 test cases from ELIP-0150.
Confidential descriptors require tweaking - wrap it to reduce internal code duplication.
generate_ functions behave like the standard wally API calls, while generate_inplace_ functions read and possibly adjust the written parameter because they modify already generated output. Make this handling more explicit and consistent, and add a check to avoid a scan-build false positive triggered by the new ct() code.
In particular, ensure that ct() blinding keys are not returned as regular keys.
20.04 is EOL and no longer supported by github for building.
a821abb to
823f21c
Compare
2658df1 to
45a7bed
Compare
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.
Uh oh!
There was an error while loading. Please reload this page.