logos-messaging/pm
1
0
Fork 0
mirror of https://github.com/logos-messaging/pm.git synced 2026-01-07 16:43:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix format

Browse Source
This commit is contained in:
fryorcraken.eth 2024-01-25 22:04:18 +11:00
parent 07ab3318c9
commit 7ac5dcba1f
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
1 changed files with 76 additions and 77 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

151
ROADMAP.md
View File

@ -9,10 +9,10 @@ MW means _man-week_: Effort time for an individual to complete the project.
### The Waku Whitepaper ### The Waku Whitepaper
**Goal:** On completion, Waku will have an academically rigorous whitepaper explaining the what, why and how of Waku protocols - **Goal:** On completion, Waku will have an academically rigorous whitepaper explaining the what, why and how of Waku protocols
**Research tracks:** All - **Research tracks:** All
**Estimated date of completion:** 2024Q4 - **Estimated date of completion:** 2024Q4
**Estimated effort:** - **Estimated effort:**
- research: 4 MW - research: 4 MW
As set out in [https://github.com/waku-org/research/issues/7](https://github.com/waku-org/research/issues/7). As set out in [https://github.com/waku-org/research/issues/7](https://github.com/waku-org/research/issues/7).
@ -21,12 +21,12 @@ Total length should be around 15 pages.
### Waku RFC Review ### Waku RFC Review
**Goal:** On completion, the set of RFCs for Waku will be simplified, reasonably up to date and accessible. - **Goal:** On completion, the set of RFCs for Waku will be simplified, reasonably up to date and accessible.
**Research tracks:** All - **Research tracks:** All
**Estimated date of completion:** 2024Q1 - **Estimated date of completion:** 2024Q1
**Estimated effort:** - **Estimated effort:**
- research: 3 MW - research: 3 MW
- docs/eco-dev: 1 MW - docs/eco-dev: 1 MW
Review our Waku RFC strategy, review the content of the most important RFCs, improve RFC indexing and ensure that Review our Waku RFC strategy, review the content of the most important RFCs, improve RFC indexing and ensure that
important RFCs are easily identified and accessible. important RFCs are easily identified and accessible.
@ -67,14 +67,14 @@ Review the most important Waku RFCs:
### Store v3-beta - message hashes ### Store v3-beta - message hashes
**Goal:** After this upgrade, the network will provide distributed and synchronised store services. - **Goal:** After this upgrade, the network will provide distributed and synchronised store services.
**Research tracks:** Message Reliability - **Research tracks:** Message Reliability
**Estimated date of completion:** 2024Q2 - **Estimated date of completion:** 2024Q2
**Estimated effort:** - **Estimated effort:**
- research: 5 MW - research: 5 MW
- nwaku - nwaku
- js-waku - js-waku
- docs/eco-dev: - docs/eco-dev:
An improved version of the Store protocol, marking a crucial increment towards a synchronisation protocol: An improved version of the Store protocol, marking a crucial increment towards a synchronisation protocol:
@ -89,16 +89,16 @@ hashes as index/cursor, can be used as a starting point.
### Store v3 - store synchronisation ### Store v3 - store synchronisation
**Goal:** Upgrade the Store service capability in the network from a collection of local, unsynchronised, - **Goal:** Upgrade the Store service capability in the network from a collection of local, unsynchronised,
semi-centralised (trusted) service nodes to a decentralised service capability in the network with inter-node synchronisation. semi-centralised (trusted) service nodes to a decentralised service capability in the network with inter-node synchronisation.
**Research tracks:** Message Reliability - **Research tracks:** Message Reliability
**Estimated date of completion:** 2024Q2 - **Estimated date of completion:** 2024Q2
**Estimated effort:** - **Estimated effort:**
- research: 9 MW - research: 9 MW
- nwaku: - nwaku:
- js-waku: - js-waku:
- go-waku: - go-waku:
- docs/eco-dev - docs/eco-dev
Building on Store v3-beta, this version of Store includes basic synchronisation between nodes. Building on Store v3-beta, this version of Store includes basic synchronisation between nodes.
This will probably include: This will probably include:
@ -117,14 +117,14 @@ IMO (iii) should be pursued as the preferred option, as far as possible.
### Store Incentivisation (first iteration/POC) ### Store Incentivisation (first iteration/POC)
**Goal:** The network will provide proof of concept for incentivised store protocol - **Goal:** The network will provide proof of concept for incentivised store protocol
**Research tracks:** Secure Scaling, Restricted Run, Protocol Incentivization - **Research tracks:** Secure Scaling, Restricted Run, Protocol Incentivization
**Estimated date of completion:** 2024Q2 - **Estimated date of completion:** 2024Q2
**Estimated effort:** - **Estimated effort:**
- research: 5 weeks - research: 5 weeks
- nwaku - nwaku
- js-waku - js-waku
- docs/eco-dev: - docs/eco-dev:
A POC incentivisation mechanism that incorporates POC versions of the three Waku service incentivisation elements: A POC incentivisation mechanism that incorporates POC versions of the three Waku service incentivisation elements:
@ -138,14 +138,14 @@ A POC incentivisation mechanism that incorporates POC versions of the three Waku
### General Service Protocol Incentivisation (first iteration/POC) ### General Service Protocol Incentivisation (first iteration/POC)
**Goal:** The network will provide proof of concept for incentivised service protocols - **Goal:** The network will provide proof of concept for incentivised service protocols
**Research tracks:** Secure Scaling, Restricted Run, Protocol Incentivization - **Research tracks:** Secure Scaling, Restricted Run, Protocol Incentivization
**Estimated date of completion:** 2024Q2 - **Estimated date of completion:** 2024Q2
**Estimated effort:** - **Estimated effort:**
- research: 5 weeks - research: 5 weeks
- nwaku - nwaku
- js-waku - js-waku
- docs/eco-dev: - docs/eco-dev:
This expands store incentivisation to other protocols: This expands store incentivisation to other protocols:
@ -154,11 +154,11 @@ This expands store incentivisation to other protocols:
### Roadmap Towards Incentivisation on Mainnet ### Roadmap Towards Incentivisation on Mainnet
**Goal:** Publish a breakdown clarifying the roadmap to push incentivization to mainnet. - **Goal:** Publish a breakdown clarifying the roadmap to push incentivization to mainnet.
**Research tracks:** Secure Scaling, Restricted Run, Protocol Incentivization - **Research tracks:** Secure Scaling, Restricted Run, Protocol Incentivization
**Estimated date of completion:** 2024Q3 - **Estimated date of completion:** 2024Q3
**Estimated effort:** - **Estimated effort:**
- research: 3 weeks - research: 3 weeks
The research and design necessary to come up with a roadmap to productionised incentivisation, including: The research and design necessary to come up with a roadmap to productionised incentivisation, including:
@ -168,12 +168,12 @@ The research and design necessary to come up with a roadmap to productionised in
### Capability Service Discovery ### Capability Service Discovery
**Goal:** After this upgrade, the network will support decentralised service (e.g. store, filter) discovery on shards. - **Goal:** After this upgrade, the network will support decentralised service (e.g. store, filter) discovery on shards.
**Research tracks**: Secure Scaling, Restricted Run - **Research tracks**: Secure Scaling, Restricted Run
**Estimated date of completion:** 2024Q2 - **Estimated date of completion:** 2024Q2
**Estimated effort:** - **Estimated effort:**
- research: 6 MW - research: 6 MW
- ... - ...
Implement a strategy for Waku nodes to discover and maintain a healthy connectivity to the set of service peers Implement a strategy for Waku nodes to discover and maintain a healthy connectivity to the set of service peers
necessary for their configured applications. In the Waku Network nodes can opt to provide a range of services necessary for their configured applications. In the Waku Network nodes can opt to provide a range of services
@ -185,12 +185,11 @@ See https://github.com/waku-org/research/issues/74.
### Content Service Discovery ### Content Service Discovery
**Goal:** After this upgrade, the network will support service discovery on content topics - **Goal:** After this upgrade, the network will support service discovery on content topics
**Research tracks**: Secure Scaling, Restricted Run - **Research tracks**: Secure Scaling, Restricted Run
**Estimated date of completion:** 2024Q4 - **Estimated date of completion:** 2024Q4
- **Estimated effort:**
**Estimated effort:** - research 6 MW
- research 6 MW
Implement a strategy for Waku nodes to discover service peers necessary for their configured applications based on the Implement a strategy for Waku nodes to discover service peers necessary for their configured applications based on the
content topics configured on those service nodes. In the Waku Network nodes can opt to provide a range of services content topics configured on those service nodes. In the Waku Network nodes can opt to provide a range of services
@ -209,12 +208,12 @@ bandwidth capping, resource-restricted options and a clear evaluation of what is
### RLN in resource-restricted clients ### RLN in resource-restricted clients
**Goal:** Using RLN in resource-restricted provide fair user experience in terms of initial setup and performance. - **Goal:** Using RLN in resource-restricted provide fair user experience in terms of initial setup and performance.
**Research tracks:** Secure Scaling, Restricted Run, Rate Limiting - **Research tracks:** Secure Scaling, Restricted Run, Rate Limiting
**Estimated date of completion:** 2024Q3 - **Estimated date of completion:** 2024Q3
**Estimated effort:** - **Estimated effort:**
- research: 8 weeks - research: 8 weeks
- js-waku... - js-waku...
Enabling RLN proof generation and verification within light clients. Enabling RLN proof generation and verification within light clients.
Different options are set out in [https://github.com/waku-org/research/issues/45](https://github.com/waku-org/research/issues/45). Different options are set out in [https://github.com/waku-org/research/issues/45](https://github.com/waku-org/research/issues/45).
@ -223,11 +222,11 @@ became the key focus of this effort.
### RLNv2 ### RLNv2
**Goal:** Improved flexibility of the rate limit (from 1 msg/epoch to N msg/epoch), providing better dimensioning for bandwidth capping. - **Goal:** Improved flexibility of the rate limit (from 1 msg/epoch to N msg/epoch), providing better dimensioning for bandwidth capping.
**Research tracks:** Secure Scaling, Restricted Run, Rate Limiting - **Research tracks:** Secure Scaling, Restricted Run, Rate Limiting
**Estimated date of completion:** 2024Q3 - **Estimated date of completion:** 2024Q3
**Estimated effort:** - **Estimated effort:**
- research: 4 weeks - research: 4 weeks
Moving from RLNv1 to RLNv2 to allow better bandwidth dimensioning in the network. This will allow a message allocation Moving from RLNv1 to RLNv2 to allow better bandwidth dimensioning in the network. This will allow a message allocation
per day per registered publisher, providing better statistical guarantees for network bandwidth usage. per day per registered publisher, providing better statistical guarantees for network bandwidth usage.
@ -236,11 +235,11 @@ See: [https://github.com/waku-org/research/issues/22](https://github.com/waku-or
### Maturing RLN variables/parameters revision (staking, contract/chain, token) ### Maturing RLN variables/parameters revision (staking, contract/chain, token)
**Goal:** A review of RLN security parameters and functionality in preparation for mainnet deployment. - **Goal:** A review of RLN security parameters and functionality in preparation for mainnet deployment.
**Research tracks:** Secure Scaling, Restricted Run, Rate Limiting - **Research tracks:** Secure Scaling, Restricted Run, Rate Limiting
**Estimated date of completion:** 2024Q3 - **Estimated date of completion:** 2024Q3
**Estimated effort:** - **Estimated effort:**
- research: 3 weeks - research: 3 weeks
Analyse RLN deployment in TWN Gen 0 and evaluate its DoS protection performance. Analyse RLN deployment in TWN Gen 0 and evaluate its DoS protection performance.