-
Notifications
You must be signed in to change notification settings - Fork 47
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: Service Peer Management for Sharding #769
Labels
enhancement
New feature or request
Comments
4 tasks
Shard based peer selection is already implemented in #783 Managing service peer connections based on shard configuration is not a priority for Gen-0 milestone. Hence removing the label from the epic. |
Descoping this for go-waku as managing service peer connections would come under purview of SDK. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Service Peer Management for Static Shards includes service Peer selection based on pubSubTopic/shard and managing service peer connections based on shard configuration.
Refer to waku-org/js-waku#1464 for some thoughts
Acceptance criteria
The text was updated successfully, but these errors were encountered: