-
Notifications
You must be signed in to change notification settings - Fork 37.7k
fuzz: wallet: add target for MigrateToDescriptor
#32624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. Code Coverage & BenchmarksFor details see: https://corecheck.dev/bitcoin/bitcoin/pulls/32624. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. |
08b574d
to
5f2fb4d
Compare
08b574d..5f2fb4d: Address #32624 (comment) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approach ACK
5f2fb4d
to
73439a7
Compare
73439a7
to
6d29c9a
Compare
lgtm ACK 6d29c9a |
This PR adds fuzz coverage for the scriptpubkeyman migration (
MigrateToDescriptor
). Note that it's a test for the migration of the scriptpubkey manager, not for the whole migration process as tried in #29694, because:This target loads keys, HDChain (even inactive ones), watch only and might add tons of different scripts, then calls
MigrateToDescriptor
. It does not play with encrypted stuff because it would make the target super slow. Also, after the migration there are some assertions that would work as a regression test for #31452, for example.