-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Filtering DNS seed by features #54
Filtering DNS seed by features #54
Conversation
7496441
to
0a17fab
Compare
NODE_WITNESS, | ||
/// xd (aka x13), all included in x9 and x5 | ||
FULL_NODE, | ||
} |
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.
How about struct SeedServices { flags: bitcoin::ServiceFlags }
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, much better, thank to point me to this feature of rust-bitcoin
} | ||
seeds_addr | ||
} | ||
} |
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.
For PRs I tend to prefer as minimal a diff as possible, as it makes it easier for me to review. Eg. I don't want to have to re-review my own code. So I'd suggest not moving existing code around.
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.
Thanks for clarifying this @cloudhead, in other words, do you want that I put the check of sub-seed in the nakamoto_comm::network
?
I usually maintain the code struct of the repository, and I'm sorry if I move your code out of your class, but I did that because I think have a DNS seed module makes easy future change.
BTW, if you want I can revert the change
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.
Thanks for clarifying this @cloudhead, in other words, do you want that I put the check of sub-seed in the
nakamoto_comm::network
?
Yes, whatever results in the smallest diff.
I usually maintain the code struct of the repository, and I'm sorry if I move your code out of your class, but I did that because I think have a DNS seed module makes easy future change.
BTW, if you want I can revert the change
Yeah, that would be better for now. It makes my job easier to review code when less of it changes :)
It's okay if doing that means that some code is not in the optimal place. This is something that can be changed later on.
Generally, I try to not mix code refactors with change in functionality, as you have to then review two things at once.
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.
Generally, I try to not mix code refactors with change in functionality, as you have to then review two things at once.
I agree with your point of view, thanks. I will change this PR, or close it and open a new one with the change in the nakamoto_comm::network
, thanks
Signed-off-by: Vincenzo Palazzo <[email protected]>
Signed-off-by: Vincenzo Palazzo <[email protected]>
…feature Signed-off-by: Vincenzo Palazzo <[email protected]>
0a17fab
to
48f2845
Compare
This include a rework of the PR cloudhead#54, but not include the refactoring in other module. Signed-off-by: Vincenzo Palazzo <[email protected]>
Closing in favor of #59 |
This include a rework of the PR cloudhead#54, but not include the refactoring in other module. Signed-off-by: Vincenzo Palazzo <[email protected]>
This include a rework of the PR cloudhead#54, but not include the refactoring in other module. Signed-off-by: Vincenzo Palazzo <[email protected]>
This include a rework of the PR cloudhead#54, but not include the refactoring in other module. Signed-off-by: Vincenzo Palazzo <[email protected]>
This include a rework of the PR cloudhead#54, but not include the refactoring in other module. Signed-off-by: Vincenzo Palazzo <[email protected]>
This include a rework of the PR cloudhead#54, but not include the refactoring in other module. Signed-off-by: Vincenzo Palazzo <[email protected]>
This include a rework of the PR cloudhead#54, but not include the refactoring in other module. Signed-off-by: Vincenzo Palazzo <[email protected]>
This include a rework of the PR cloudhead#54, but not include the refactoring in other module. Signed-off-by: Vincenzo Palazzo <[email protected]>
This include a rework of the PR cloudhead#54, but not include the refactoring in other module. Signed-off-by: Vincenzo Palazzo <[email protected]>
This include a rework of the PR cloudhead#54, but not include the refactoring in other module. Signed-off-by: Vincenzo Palazzo <[email protected]>
This include a rework of the PR cloudhead#54, but not include the refactoring in other module. Signed-off-by: Vincenzo Palazzo <[email protected]>
Fixes #50
Working in progress