backport: bitcoin#25122, #25504, #25647, #25768, #25924, #25990, #26021, #26037, #26091, #26203, #26205 - #7550
Merged
Merged
Conversation
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.
Issue being fixed or feature implemented
Multiple wallet-relevant backports
PR is slightly over-sized because some of them depends on each other ; other are conflicting if goes to own branch.
What was done?
Backports from bitcoin core v24, v25 with wallet-related code.
How Has This Been Tested?
Run unit & functional tests
Breaking Changes
See relevant release notes changes:
Wallet
getreceivedbylabelnow returns an error, "Label not foundin wallet" (-4), if the label is not in the address book. (rpc: getreceivedbylabel, return early if no addresses were found in the address book bitcoin/bitcoin#25122)
Checklist:
Go over all the following points, and put an
xin all the boxes that apply.