Rules of engagement (will be added to https://github.com/waku-org/pm/blob/master/PROCESS.md)

• For every P (Performance) there must be a Grafana panel (pointed to fleet), and a Vac-DST simulation to sign-off the P (search for “Vac-DST”).
• For every R (Reliablity) there should be a test suite by Vac-QA that sign-off the R in unreliable network environment (search for “Vac-QA”); and potentially a Grafana panel (pointed to fleet), and a Vac-DST simulation (if relevant).
• Deliverables deliver a number of FURPS: deliverable name: FURPS they deliver
• Deliverables are owned by one or several teams, specified in parenthesis after deliverable

*Description/Resources Required/Deliverables/Tracking Metrics/Risks can be found in the google doc https://docs.google.com/document/d/1L8HvXtAYk-JqQL6w3RgCskXwegcTa0J5nyH9YL4LrQE/edit?tab=t.0.*

Milestones started in 2024

Store Service Upgrade

Waku Roadmap Entry

GitHub Milestone

Deliverables

1. ✅ Store v3-beta - Message Hashes: F1, U2
2. ❌ Store v3 - store synchronisation F2, R3, P1
3. 🏗️ DoS protection for req-res protocols and metrics F3, R2. P4 (nwaku)
4. 🏗️ PostgreSQL Maintenance: F4, U1. R1, P2, P3 (nwaku)
5. ✅ Metric: Count store messages F5

Functionality

1. ✅ Messages can be retrieved from store nodes using their hashes

2. ❌ Store nodes can synchronise their latest messages with each other

   Used an off-the-shelf protocol and library but the performance and API for Waku use case was inadequate (eg, removing messaging from sync window). Decided to design new protocol, more optimized (different fingerprint and storage strategies) and future proof. eg, will be possible to use content topics as sync criteria. Will be defined in new FURPS/Milestone.