fix: set internal=false on recovery key descriptor import #4451
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
Fixes recovery key UTXOs not appearing in listunspent. The default (None) treats descriptors as internal/change addresses, hiding them from listunspent. Setting internal=false makes them visible. Ref: bitcoin/bitcoin#26813
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
Recovery key descriptors are imported with
internal: None, which defaults totrue. Bitcoin Core hides internal descriptors fromlistunspent, making stuck commit UTXOs invisible.Fix
Set
internal: Some(false)so the descriptor is treated as a receive address and appears inlistunspent.Testing
Tested on Bitcoin Core 28.0 regtest - recovery UTXOs now appear in
listunspent.Reference
bitcoin/bitcoin#26813