Skip to content
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

bug: wakuPeerExchangeDiscovery doesn't seem to take pubsubTopics into account #1858

Open
fbarbu15 opened this issue Feb 20, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@fbarbu15
Copy link
Collaborator

fbarbu15 commented Feb 20, 2024

This is a bug report

Problem

When using wakuPeerExchangeDiscovery with a wrong(non-existent or empty) pubsubtopicArray the peerExchange still works and node are discovered. Peer Exchange does not take the passed pubsub topics into consideration.

Solution

Instead of saving all peers to the peer store, discard the peers that are not on the configured shard.

@fbarbu15 fbarbu15 added the bug Something isn't working label Feb 20, 2024
@fryorcraken fryorcraken added this to Waku Feb 20, 2024
@chair28980 chair28980 moved this to Triage in Waku Feb 28, 2024
@chair28980
Copy link
Contributor

@danisharora099 to inspect the issue and update with findings.

@danisharora099
Copy link
Collaborator

Right!
Pubsub topic is required to satiate BaseProtocol and is not taken into consideration while finding/saving peers, as peer exchange finds all peers and then Connection Manager ignores peers according to the pubsub topic.

We can not save peers in the peer store if they are not relevant to the configured pubsub topics

Updated the issue description to reflect the same

@chair28980 chair28980 moved this from Triage to To Do in Waku Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: To Do
Development

No branches or pull requests

3 participants