[Epic] 1.1 Network requirements and task breakdown

[jm-clius]

Epic label: E:1.1 Network requirements and task breakdown

Summary

This tracks the work necessary to determine the specifications for a public Waku Network, a rough design to achieve this and a breakdown of tasks necessary to get there.

The deliverable of this milestone is twofold:

A) Firstly answer questions such as:

1. How many shards to we want to support initially? Do we know how to increase this in future?
2. What is the reasonable bandwidth expectation per shard?
3. What is a reasonable message rate expectation per shard?
4. What is a reasonable number of publishers per shard?
5. What is a reasonable max message size for the shard?
6. What membership mechanisms and limits should we set and should this be done on a per-shard basis?

B) Breakdown the list of tasks necessary to achieve the design determined in (A) and do initial task assignment to core contributors

Acceptance Criteria

Tasks

• feat(64/WAKU2-NETWORK): Introduce raw Waku Network RFC vacp2p/rfc#616

[jm-clius]

Weekly Update

• achieved: Setup project management tools; determined number of shards to 8; some conversations on RLN memberships
• next: Breakdown and assign tasks under each milestone for the 1 million users/public Waku Network epic.

[jm-clius]

Weekly Update

• achieved: Breakdown and assign tasks under each milestone for the 1 million users/public Waku Network epic.
• next: Refine/discuss task breakdown. Start working on Waku Network RFC.

[jm-clius]

Weekly Update

• achieved: Further task refinement and assigning ownership. Visibility and traceability via GH issues.
• next: Start working on Waku Network RFC.

[jm-clius]

Weekly Update

• achieved: Started working on Waku Network RFC. Visibility and traceability in GH improvements.
• next: Continue working on Waku Network RFC.

[jm-clius]

Weekly Update

• achieved: Opened first raw version of Waku Network RFC for review.
• next: Address any feedback on the Waku Network RFC and complete underdefined sections.

[fryorcraken]

@jm-clius what is realistic revised date pleaes?

[jm-clius]

This can be closed once vacp2p/rfc#616 is merged. Realistically ~22 Sept.

[jm-clius]

Weekly Update

• achieved: Further specifications added for RLN. Merged and published first version of RFC
• next: Define first launchable (sub)network for Devconnect.

[jm-clius]

This issue is closed by the merging of vacp2p/rfc#616