Multi-input PSBT spend for homogeneous input asset ID #743
Conversation
This file contains 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 modify the `AnchorVirtualPsbts` RPC endpoint to enable support for multi-input vPSBT.
This commit adds support for multi-input full value interactive send where each input asset shares the same asset ID.
This commit adds a tests to ensure that we can correctly construct and spend a multi-input full value PSBT where each input has the same asset ID.
ffranr
force-pushed
the
anchorvp-multi-inputs
branch
from
b671807 to
820f4a8
Compare
jharveyb
approved these changes
Dec 20, 2023
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.
This PR solves #297 for the case were each input asset ID is the same.
This PR modifies our asset send procedure such that we can spend a multi-input full value PSBT where each input has the same asset ID. The PR adds an itest to test the new changes.
There are more things we should test:
But lets keep this PR small if we can and open another (if that makes sense).
This PR replaces #741
I've moved the branch to repo
lightninglabs/taproot-assetsso that I can base another branch on top of it.Fixes #297