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
fuzz: add target for ScriptPubKeyMan
(legacy)
#28153
Conversation
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. 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. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
e951d31
to
c2e197a
Compare
CI failure seems unrelated. |
c2e197a
to
dbe54b1
Compare
Pushed to re-run CI. |
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.
ACK
I support the idea of having separate files for Legacy and Descriptor because I think the Wallet implementation would differ. Overall, the code looks great to me.
09aa5cf
to
f67d8ec
Compare
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.
lgtm
f67d8ec
to
eb4d8b3
Compare
Closing as there is little support for working on fixing non-critical issues in legacy wallets. |
Would be nice to have a descriptor wallet target? Alternatively, I think your plan was to speed up |
Yes, I'm working on speeding up wallet_notifications. |
This PR adds target for
{Legacy}ScriptPubKeyMan
. I'm working on a descriptor one and will do it in a separate file. I tried to focus here on functions that we use directly and we may have in some unit tests.