-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add Bloom Filters #68
Conversation
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.
Looks good to me, definitely make sure to test that migration
Also you should add a warning about this being discouraged for everything except bisq |
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.
This change, on its own/in its current form, will break bitcoind. You need to write a migration for the config spec since you changed the structure of how the config.yaml is organized. Otherwise this looks good
Added the parameter to the lt_22_0_0 script with the other filters - will test migration |
@ProofOfKeags I think the only change that needs to be made here is that 22_0_0 needs to be renamed 22_0_2 and referenced under that version in the manifest. But hopefully any issues will be uncovered when @kn0wmad tests the migration |
This is insufficient as it is currently written it is trying to mutate |
I see... maybe it would make more sense to keep the name "Block Filters" - I wasn't sure if it was an accurate description or not to include bloom filters there, but it can also be in it's own category |
@ProofOfKeags it's actually adding new keys with the new names, and defaulting them to false. But you're right that it needs to move the old keys to the new names rather than simply creating the new keys and defaulting them to false. @kn0wmad there are probably other things you need to check as well, like whether the stuff left over from 22.0.0 can be removed, or whether it needs to be separated into its own migration. This is the first time we're going to have two migrations in a package. You need to test the hell out of this. |
Deprecating this PR in favor of #69, inshallah |
Successfully tested a connection with Bisq
Closes #67