spend 2 assets with different close methods #24
Merged
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 adds a new test that uses 2 taproot wallets to issue 2 assets on the same UTXO, spends the first one and checks that the second one is still spendable after going through a blank transition.
The second
pay()
(which should spend the blank allocation from the previous transfer) fails in some cases, with different errors depending on the selected close methods for the two assets:pay()
fails withComposition(Stock("the spent UTXOs contain too many seals which can't fit the state transition input limit."))
pay()
fails withComposition(Stock("the spent UTXOs contain too many seals which can't fit the state transition input limit."))
pay()
fails withComposition(Construction(NoInputs))