-
Notifications
You must be signed in to change notification settings - Fork 21
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 new getcfilters message for utreexo nodes #192
base: main
Are you sure you want to change the base?
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.
I think maybe creating a new index is a better way of approaching this. With the new index you'd only store the filter header.
Could you make the commits atomic? Ideally all the changes to each of the packages should be committed together with each commit achieving one single thing. The change to Then all the changes to the package |
The index panics out on start |
Let me look into it |
This is meant to be just a draft PR
Add support for new getcfilters message called
UtreexoCFilter
When a new block is added, a new UtreexoCFilter filter is created and persisted on the node.
This filter is created by serializing the contents of the roots at that height.
When a node receives a getcfilters message, the logic doesn't change much, it handles it almost identical to how it deals with basic filters.