-
Notifications
You must be signed in to change notification settings - Fork 36.6k
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
wallet: No BDB creation, unless -deprecatedrpc=create_bdb #28597
Conversation
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. Code CoverageFor detailed information about the code coverage, see the test coverage report. 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. |
5f0af10
to
fa071ae
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.
Concept ACK.
Maybe add a small test creating a legacy wallet without the "create_bdb" flag? asserting the error is being properly thrown.
Yes, happy to push a commit or patch, if someone writes one. Otherwise, it should be possible to test locally:
|
Concept ACK |
Concept ACK. |
tACK fa071ae |
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.
utACK fa071ae
On a second thought, probably better to call it "create_legacy_wallet" instead of "create_bdb". Users might not be aware of the legacy wallet db engine name. |
I think BDB is mentioned in all compile docs, as well as the GUI. Maybe not in the RPC interface, but it is explained in this pull. Though, happy to change. |
ACK fa071ae |
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.
post-merge ACK fa071ae
This should have had release notes. |
A label was added after merge, but it looks like no one went through those. Currently there are 4 tagged: https://github.com/bitcoin/bitcoin/issues?q=label%3A%22Needs+release+note%22+is%3Aclosed |
Release note being added in #29023. |
fa88953 doc: Add link to needs-release-notes label (MarcoFalke) Pull request description: This makes it easier to spot and not forget. C.f. #28597 (comment) ACKs for top commit: kristapsk: ACK fa88953 TheCharlatan: ACK fa88953 Tree-SHA512: 28336cde36d62622d1b6627497291cbd4644bf1e4e6f17dc9cde39f254e7094dd02484da754e45558e59facb20941dd0c049ce7b33dcc62bfec6c26c16516cdf
With BDB being removed soon, it seems confusing and harmful to allow users to create fresh BDB wallets going forward, as it would load them with an additional burden of having to migrate them soon after.
Also, it would be good to allow for one release for test (and external) scripts to adapt.
Fix all issues by introducing the
-deprecatedrpc=create_bdb
setting.