Skip to content

wallet, refactor: Remove Legacy wallet unused warnings and errors #32481

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

pablomartin4btc
Copy link
Member

Remove dead code due to legacy wallet support removal.

@DrahtBot
Copy link
Contributor

DrahtBot commented May 13, 2025

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Code Coverage & Benchmarks

For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/32481.

Reviews

See the guideline for information on the review process.
A summary of reviews will appear here.

Conflicts

Reviewers, this pull request conflicts with the following ones:

  • #bitcoin-core/gui/872 (Menu action to export a watchonly wallet by achow101)
  • #28333 (wallet: Construct ScriptPubKeyMans with all data rather than loaded progressively by achow101)

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.

@DrahtBot
Copy link
Contributor

🚧 At least one of the CI tasks failed.
Task lint: https://github.com/bitcoin/bitcoin/runs/42142854745
LLM reason (✨ experimental): The CI failure is due to trailing whitespace and spelling errors identified by the lint check.

Hints

Try to run the tests locally, according to the documentation. However, a CI failure may still
happen due to a number of reasons, for example:

  • Possibly due to a silent merge conflict (the changes in this pull request being
    incompatible with the current code in the target branch). If so, make sure to rebase on the latest
    commit of the target branch.

  • A sanitizer issue, which can only be found by compiling with the sanitizer and running the
    affected test.

  • An intermittent issue.

Leave a comment here, if you need help tracking down a confusing failure.

@pablomartin4btc pablomartin4btc force-pushed the wallet-remove-legacy-warnings-and-errors branch 2 times, most recently from a483558 to e66e9ee Compare May 13, 2025 14:59
@pablomartin4btc pablomartin4btc force-pushed the wallet-remove-legacy-warnings-and-errors branch 2 times, most recently from 1c0ab13 to 3909051 Compare May 13, 2025 19:43
@pablomartin4btc
Copy link
Member Author

Updates:

  • Addressed @achow101's feedback by adding an Assert() on CreateWallet() enforcing only descriptor wallets can be created.

Remove dead code due to legacy wallet removal.
SetupGeneration was supposed to be the function that all SPKMs used
to setup automatic generation, but it didn't work out that way and
ended up being legacy only. It should be deleted at this point.
@pablomartin4btc pablomartin4btc force-pushed the wallet-remove-legacy-warnings-and-errors branch from 3909051 to dbc8427 Compare May 16, 2025 18:21
@pablomartin4btc
Copy link
Member Author

Addressed feedback removing unnecessary descriptor wallet checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants