Fix locked change output-bug #2485
Merged
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
…adding info to locked utxos
✅ Deploy Preview for specter-desktop-docs canceled.
|
This was
linked to
issues
Jan 2, 2025
Closed
turkycat
approved these changes
Jan 2, 2025
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.
All kudos to @leon-costa and his PR: #2467
I could replicate / narrow down the issue by creating a transaction with the recipient address belonging to my wallet.
Locking / freezing the UTXO belonging to the receive address created no issue but locking the UTXO for the change created the issue described in Leon's PR. The reason for this: gettransaction result does not include change outputs.
I am pressed for time to make a release, otherwise I would have commented in the OP PR and iterated there.