-
Notifications
You must be signed in to change notification settings - Fork 57
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
chore: upgrade peer exchange mounting #2953
Conversation
You can find the image built from this PR at
Built from 46e61d0 |
Not sure I understand the change. Before this change there were 2 cases:
Not sure what's wrong with that logic, maybe I'm missing something? But I see that with the changes now, we are eliminating the possibility of configuring the node as a peer exchange client |
This change is based on the chat in this Discord thread. Previously, nodes (server-side) would only add the node address if it provided the peer exchange service. Now, that's not necessary; any client can ask any node that provides the peer exchange service. The old method was somewhat permission-based, where only the node could decide who received the peer exchange service. The new way is more permissionless. Any suggestions or corrections are appreciated, @gabrielmer. |
But we currently don't need a
The condition to require a Again, I might be missing something 😶 |
I just updated the PR. Can you please look into it and try isolating both things so nothing hurts 😊? |
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 reasonable to me. :)
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.
LGTM! Thanks so much!
This PR upgrades the mounting scheme for peer_exchange. With this update, a specific node address is no longer required when mounting peer_exchange from the node side.