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

feat: Peer discovery with dynamic shards as dimension #678

Closed
chair28980 opened this issue Aug 24, 2023 · 5 comments
Closed

feat: Peer discovery with dynamic shards as dimension #678

chair28980 opened this issue Aug 24, 2023 · 5 comments
Assignees
Labels
E:1.4: Sharded peer management and discovery See https://github.com/waku-org/pm/issues/67 for details

Comments

@chair28980
Copy link
Contributor

Tracks work necessary to ensure that nodes can filter discovered peers according to the shards the node is currently subscribed to and for the node to update its own discoverable ENR every time its subscription set changes.

Priority: Critical for launch.

@richard-ramos
Copy link
Member

I think part of this has been implemented already for WakuRelay since #595 , because anytime Relay().Subscribe is called or a pubsub subscription is closed, the ENR is updated with the new shards.
See https://github.com/waku-org/go-waku/blob/master/waku/v2/node/localnode.go#L288-L347

@richard-ramos
Copy link
Member

In waku-org/research#3 the following is described:

Task: Peer discovery with dynamic shards as dimension
Tracks work necessary to ensure that nodes can filter discovered peers according to the shards the node is currently subscribed to and for the node to update its own discoverable ENR every time its subscription set changes.

This does not mention specific protocols, so I have the following question: should a lightnode doing a filter subscription have its ENR affected as well?
cc: @SionoiS

@SionoiS
Copy link

SionoiS commented Sep 1, 2023

@richard-ramos

What I did in Nwaku was to update the ENR (and filter) that discv5 use which is different from the waku_node one but that's impl. details.

This does not mention specific protocols, so I have the following question: should a lightnode doing a filter subscription have its ENR affected as well?

🤔 probably not since lightnode are not discoverable anyway.

@richard-ramos
Copy link
Member

I see, in that case I'd consider this task to be complete.

@chaitanyaprem
Copy link
Collaborator

Closing this as per above discussion as it is already addressed.
Any new scenarios identified would be taken up as maintenance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E:1.4: Sharded peer management and discovery See https://github.com/waku-org/pm/issues/67 for details
Projects
Archived in project
Development

No branches or pull requests

5 participants