Taproot multisig sample #38
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
Member
|
Oh shoot I never got back to this and reviewed sorry! Would you mind squashing the two commits here? Otherwise looks good! |
ItoroD
force-pushed
the
add-taproot-sample
branch
from
b791464 to
0ce0ec3
Compare
ItoroD
force-pushed
the
add-taproot-sample
branch
from
0ce0ec3 to
81fa803
Compare
Collaborator
Author
Updated!. Thank for the review |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This example is similar to our
MultisigTaprootTransaction. Here we use taproot script to show we can spend from taproot. This also shows what the psbt looks like after each major update like signing and finalizing. We can also see the taproot fields populated in this example.