-
Notifications
You must be signed in to change notification settings - Fork 8
removed bloom module #280
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: v0.41-dev
Are you sure you want to change the base?
removed bloom module #280
Conversation
WalkthroughThe entire bloom filter module is removed from the dash-spv crate, including the builder, manager, statistics tracking, utility functions, and all associated tests. No bloom filter functionality remains publicly exported. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20–30 minutes
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (7)
💤 Files with no reviewable changes (7)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (19)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This PR removed the bloom module since it is not being used in the codebase. The only reference to BloomFitlers in the crate is the following:
That is being use here:
It sais that the network is handling the filtering. Couldn't find the Network really handling this, maybe is the dashcore crate.
Would like confirmation if this can be removed or if we need to implement it. If we can remove it I would like to add to this PR a commit removing the
should_fetch_transactionmethod and theMempoolStrategyif it is not being used anywhere elseSummary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.