Add new waku tasks (#343)

content/dst/waku/2025q4-waku-evaluation.md

@@ -97,3 +97,47 @@ Schedule note: Dates reflect quarter bounds; update when actual timing is known.
 #### Deliverables
 - Reports:
 - Related PRs if apply:
+
+
+
+### nWaku v0.37 bandwidth regression
+
+* fully qualified name: `vac:dst:waku:2025q4-waku-evaluation:nwaku-v0.37-bandwidth-regression`
+* owner: Farooq
+* status: not started
+* start-date: 2025/11/27
+* end-date: 2025/12/12
+
+#### Description
+Set a baseline 1K nodes 1msg/s 1KB scenario with only relay nodes, + 3 bootstrap nodes.
+Get per a complete per protocol metric plots with the image provided by Waku. The plots in 
+the v0.37 notion report have missing protocols.
+After the previous run, do another one with rendezvous set to False. This protocol metric 
+should appear in the previous point plots, if it is not there, check why. 
+Also, check if this flag affects bandwidth and latency performance.
+Depending on the results, we will iterate on further followups.
+
+#### Deliverables
+- Reports:
+- Related PRs if apply:
+
+
+### nWaku v0.37 store regression
+
+* fully qualified name: `vac:dst:waku:2025q4-waku-evaluation:nwaku-v0.37-store-regression`
+* owner: Farooq
+* status: not started
+* start-date: 2025/11/27
+* end-date: 2025/12/12
+
+#### Description
+Experiment with different sizes of an experiment setup to better test store protocol. 
+For example, 500 nWaku relay nodes and 5 store nodes (+2 bootstrap nodes) should be enough.
+Inject a bunch of messages, and then query. Scenario should be is fast and reproducible.
+Understand what is the behavior of get store messages. The intention is to query nodes that 
+are not store nodes, to see if they are able to retrieve the messages.
+Document different responses of the query. Analyze the behavior.
+
+#### Deliverables
+- Reports:
+- Related PRs if apply: