Vac: update DST milestones

content/vac/dst/deployment-and-analysis/vac/libp2p-version-testing.md

@@ -0,0 +1,43 @@
+---
+title: "Ongoing testing of specific monthly libp2p releases"
+description: "On a monthly cadence, test specific releases of libp2p and provide feedback."
+---
+## `vac:dst:deployment-and-analysis:vac:libp2p-version-testing`
+---
+
+```mermaid
+%%{ 
+  init: { 
+    'theme': 'base', 
+    'themeVariables': { 
+      'primaryColor': '#BB2528', 
+      'primaryTextColor': '#fff', 
+      'primaryBorderColor': '#7C0000', 
+      'lineColor': '#F8B229', 
+      'secondaryColor': '#006100', 
+      'tertiaryColor': '#fff' 
+    } 
+  } 
+}%%
+gantt
+  tickInterval 1month
+  dateFormat YYYY-MM-DD 
+  section Status
+    LibP2P: 2024-05-15, 2024-12-31
+```
+
+- status: Ongoing
+- CC: Wings
+
+### Description
+
+The Vac P2P team is transitioning nim-libp2p to a monthly release cycle.
+Our approach involves selecting a commit hash to designate as the monthly version a week prior to release. 
+DST will conduct stability tests on this version (with additional testing in Nomos and Waku test fleets outside of the DST scope). 
+Our aim is to increasingly automate this process. 
+The next round of testing is scheduled for the end of May, targeting the beginning of June.
+
+### Justification
+
+### Deliverables
+- Monthly report of libp2p testing outcomes

content/vac/dst/deployment-and-analysis/waku/midscale.md

@@ -33,14 +33,18 @@ gantt
 
 Run deployments of between 1000 and 5000 Waku nodes actively passing messages in one network.
 
-- Measure relay bandwidth
-- Measure reliability of Waku message relaying
-- Measure usage of the DiscV5 protocol
-- Test Store protocol at scale
-- Test Waku relay+store reliability with nodes going offline/online
-    - If nodes go online/offline, we should be able to retrieve missing messages from the store. This will also test Waku message relaying in a different way.
-- Filter and lightpush tests
-- Test heterogenous clusters involving different node implementations such as nwaku and go-waku.
+Testing is to be done in this order of priority:
+1. Measure relay bandwidth
+2. Measure reliability of Waku message relaying
+3. Measure usage of the DiscV5 protocol in the same scenario as (1).
+4. Test Store protocol at scale
+5. Test Waku relay+store reliability with nodes going offline/online
+  - If nodes go online/offline, we should be able to retrieve missing messages from the store. This will also test Waku message relaying in a different way.
+6. Filter and lightpush tests
+7. Measure (1) and (3) in heterogenous clusters involving different node implementations such as nwaku and go-waku
+8. Measure (3) with Waku peer exchange protocol used for discovery by a subset of nodes.
+9. Measure (1) with a mix of nodes using Resource-restricted device reliability protocol and peer exchange, meaning a small number of nwaku nodes serve store, light push and filter protocols and a high number of clients consume them. For example, 6-10 service nodes, 200 relay nodes and 1000 light nodes.
+This should include connection and node churn impact on reliability for both relay and light clients.
 
 ### Justification
 

content/vac/dst/index.md

@@ -10,15 +10,16 @@ lastmod: 2023-09-08
 ## `vac:dst:`
 ---
 
-### `tooling:vac`
+### `tooling`
 * [[vac/dst/tooling/vac/deployer-tool|deployer-tool ]]
 * [[vac/dst/tooling/vac/visualiser-tool|visualiser-tool ]]
 
-## `deployment-and-analysis:waku`
+## `deployment-and-analysis`
 * [[vac/dst/deployment-and-analysis/waku/10k|10k ]]
 * [[vac/dst/deployment-and-analysis/waku/midscale|midscale ]]
 * [[vac/dst/deployment-and-analysis/nomos/mixnet|mixnet ]]
 * [[vac/dst/deployment-and-analyis/codex/testnet|testnet ]]
+* [[vac:dst:deployment-and-analysis/vac/libp2p-version-testing|libp2p-version-testing ]]
 
 ### `wakurtosis:waku:`