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

[Epic] 2.2: Sharded capability discovery for light protocols #63

Closed
2 tasks done
jm-clius opened this issue Sep 1, 2023 · 5 comments
Closed
2 tasks done

[Epic] 2.2: Sharded capability discovery for light protocols #63

jm-clius opened this issue Sep 1, 2023 · 5 comments
Assignees
Labels
E:2.2: Sharded cap discovery for light protocols See https://github.com/waku-org/pm/issues/63 for details Epic Tracks a sub-team Epic.

Comments

@jm-clius
Copy link

jm-clius commented Sep 1, 2023

Epic label: E:2.2: Sharded cap discovery for light protocols

Summary

Ability to discover peers providing filter, lightpush and peer-exchange services within the decentralised network. To the application this should present as a peer selection mechanism that translates content topics to underlying shard.

Acceptance Criteria

Tasks

@jm-clius jm-clius added the Epic Tracks a sub-team Epic. label Sep 1, 2023
@fryorcraken fryorcraken added this to Waku Sep 1, 2023
@fryorcraken fryorcraken added this to the Waku Network Gen 0 milestone Sep 5, 2023
@fryorcraken fryorcraken added the E:2.2: Sharded cap discovery for light protocols See https://github.com/waku-org/pm/issues/63 for details label Sep 8, 2023
@fryorcraken
Copy link
Contributor

Only work tracked with this epic so far is js-waku work: https://github.com/orgs/waku-org/projects/2/views/2?filterQuery=is%3Aopen+label%3A%22E%3A2.2%3A+Sharded+cap+discovery+for+light+protocols%22&sortedBy%5Bdirection%5D=asc&sortedBy%5BcolumnId%5D=Status

From waku-org/research#3 (comment)

Task: Service peer selection on specific shards

Currently a service peer (e.g. a store node) is either provided by the application or it expects the peer manager to suggest a suitable service peer (selectPeer()). This task focuses on the latter: peer manager should provide ability to find service peers for a specific shard, based on the content topic that the application is interested in (e.g. an API call to selectPeer(Protocol, ContentTopic)), or kick off an ad-hoc discovery process until a suitable service peer is found. Client APIs (for filter, lightpush, peer-exchange) should automatically make use of this mechanism if the application does not explicitly set the desired service peer.

Owners:

Overall: @alrevuelta
Implementations:
    nwaku: @alrevuelta
    go-waku: @chaitanyaprem
    js-waku: ??

Priority: critical for launch

I do not see any issue tracking this work in nwaku/research.go-waku.

@alrevuelta, are you able to clarify the work needed here? cc @jm-clius

@alrevuelta
Copy link

#63 (comment)

@SionoiS Mind having a look? Maybe related to some of the peer management work you are doing?

@SionoiS
Copy link

SionoiS commented Oct 25, 2023

Duplicate of waku-org/nwaku#1941??? If not, can the difference be clarified?

@fryorcraken
Copy link
Contributor

Duplicate of waku-org/nwaku#1941??? If not, can the difference be clarified?

I suggest to sync with @jm-clius

@jm-clius
Copy link
Author

@SionoiS not a duplicate afaics, but the nwaku issue should be linked in this Epic description. The Epic tracks work across all clients.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E:2.2: Sharded cap discovery for light protocols See https://github.com/waku-org/pm/issues/63 for details Epic Tracks a sub-team Epic.
Projects
Status: Done
Development

No branches or pull requests

7 participants