DST Updates - 2025-09-29 (#299)

AlbertoSoutullo · kaiserd · web-flow · commit 34e3165138ad · 2025-10-07T14:52:58.000+02:00
Co-authored-by: kaiserd &lt;1684595+kaiserd@users.noreply.github.com&gt;
diff --git a/content/dst/ift/2025q3-dst-tooling.md b/content/dst/ift/2025q3-dst-tooling.md
@@ -221,7 +221,7 @@ Keep track of values and logs of previous experiments in an automatized and cros
 
 * fully qualified name: `vac:dst:ift:2025q3-dst-tooling:nim-libp2p-cron-removal`
 * owner: Farooq
-* status: 90%
+* status: 100%
 * start-date: 2025/09/02
 * end-date: 2025/09/19
 
@@ -241,7 +241,7 @@ to vary the message rate and size in the middle of an experiment if needed.
 
 * fully qualified name: `vac:dst:ift:2025q3-dst-tooling:nim-libp2p-dst-node-refactor`
 * owner: Farooq
-* status: 80%
+* status: 90%
 * start-date: 2025/09/02
 * end-date: 2025/09/19
 
@@ -254,13 +254,14 @@ Apart from this, the node should be able to be executed from the same docker ima
 
 #### Deliverables
 - PRs
+  - [Github PR: Topology #4](https://github.com/vacp2p/dst-libp2p-test-node/pull/4)
 - Related Documents
 
 ### Deployment refactor
 
 * fully qualified name: `vac:dst:ift:2025q3-dst-tooling:deployment-refactor`
 * owner: Pearson
-* status: 30%
+* status: 100%
 * start-date: 2025/09/15
 * end-date: 2025/09/30
 
@@ -272,5 +273,5 @@ feasible, and improve with more feedback from the members of the team.
 
 #### Deliverables
 - PRs:
-  - [Github Draft PR: Build basic Waku nodes with python dict #143]https://github.com/vacp2p/10ksim/pull/143
+  - [Github PR: Build basic Waku nodes with python dict #143]https://github.com/vacp2p/10ksim/pull/143
 - Related Documents:
diff --git a/content/dst/ift/2025q4-dst-tooling.md b/content/dst/ift/2025q4-dst-tooling.md
@@ -132,3 +132,22 @@ Ideally it is done with Docker Desktop, or any other light Kubernetes solution.
 - PRs:
 - Related Documents:
 
+### Complete deployment refactor
+
+* fully qualified name: `vac:dst:ift:2025q4-dst-tooling:complete-deployment-refactor`
+* owner: Pearson
+* status: 0%
+* start-date: 2025/10/06
+* end-date: 2025/10/24
+
+#### Description
+After refactor feasibility was done in `vac:dst:ift:2025q3-dst-tooling:deployment-refactor`, continue
+this line of work to complete the refactor. 
+Keep following the discussions on the [deployment document](https://www.notion.so/Deployment-Workflow-25d8f96fb65c80f7801ce9a06dede8a4).
+To not keep extending new functionalities with new projects, Waku will be added as baseline 
+for the refactor functionalities to be tested. Other projects will be  added in other tasks.
+
+#### Deliverables
+- PRs:
+- Related Documents:
+
diff --git a/content/dst/nomos/2025q3-nomos-scaling.md b/content/dst/nomos/2025q3-nomos-scaling.md
@@ -59,7 +59,7 @@ This will also help spur on outside adoption and contributions.
 
 * fully qualified name: `vac:dst:nomos:2025q3-nomos-scaling:nomos-deployment-test`
 * owner: Alberto
-* status: 80%
+* status: 100%
 * start-date: 2025-09-19
 * end-date: 2025-09-30
 
@@ -73,7 +73,9 @@ and is well-prepared to support advanced experiments like Blendnet.
 
 #### Deliverables
 * PRs:
+  * [Github PR: Files for nomos testnet #145](https://github.com/vacp2p/10ksim/pull/145)
 * Report published with all relevant details
+  * [Notion: Nomos compose to K8s issues](https://www.notion.so/Nomos-compose-to-K8s-27d8f96fb65c8077b5cefa236a0dddda)
 
 
 ### Blend benchmarking
diff --git a/content/dst/nomos/2025q4-nomos-scaling.md b/content/dst/nomos/2025q4-nomos-scaling.md
@@ -71,3 +71,36 @@ Measure the speed and reliability of Nomos's blendnet.
 * Benchmarks done
 * Report published with all relevant details
 
+
+### DA benchmarking
+
+* fully qualified name: `vac:dst:nomos:2025q4-nomos-scaling:nomos-da-benchmarking`
+* owner: Alberto
+* status: 0%
+* start-date:
+* end-date:
+
+#### Description
+
+Measure Nomos bandwidth usage in DA per node and entire network.
+
+#### Deliverables
+* PRS:
+* Documents:
+
+
+### Nomos consumption
+
+* fully qualified name: `vac:dst:nomos:2025q4-nomos-scaling:nomos-consumption`
+* owner: Alberto
+* status: 0%
+* start-date:
+* end-date:
+
+#### Description
+
+Measure Nomos resource consumption (CPU/RAM) usage in different scenarios.
+
+#### Deliverables
+* PRS:
+* Documents:
diff --git a/content/dst/status/2025q3-status-go-chat-protocol-benchmarks.md b/content/dst/status/2025q3-status-go-chat-protocol-benchmarks.md
@@ -445,7 +445,7 @@ Same as @Send one-to-one message - Network outage for private group
 
 * fully qualified name: `vac:dst:status:2025q3-status-go-chat-protocol-benchmarks:cleanup-resources`
 * owner: Alberto
-* status: 80%
+* status: 100%
 * start-date: 2025/09/15
 * end-date: 2025/09/30
 
@@ -466,6 +466,7 @@ Close up draft PRs from previous procol benchmarks. Extract utilities and/or add
 - [Contact request #23](https://github.com/vacp2p/status-benchmarks/pull/23) 
 - [Send one-to-one #24](https://github.com/vacp2p/status-benchmarks/pull/24) 
 - [Create private group #25](https://github.com/vacp2p/status-benchmarks/pull/25)
+- [Send group messages #26](https://github.com/vacp2p/status-benchmarks/pull/26)
 
 ### Delay and store
 
@@ -489,7 +490,7 @@ Check how this behaves, and if it solves scalability.
 
 * fully qualified name: `vac:dst:status:2025q3-status-go-chat-protocol-benchmarks:relay-node-benchmark-2`
 * owner: Alberto
-* status: 50%
+* status: 100%
 * start-date: 2025/09/15
 * end-date: 2025/09/30
 
@@ -500,3 +501,6 @@ Using the fix in the discovery process for the
 to repeat the benchmarks for only scenarios that use relay nodes, as discovery in light nodes is not working at the moment.
 
 #### Deliverables
+- [Github PR: Async utils](https://github.com/vacp2p/status-benchmarks/pull/33)
+- [Github PR: Second benchmark additions](https://github.com/vacp2p/status-benchmarks/pull/32)
+- [Notion: Status discovery gathering information](https://www.notion.so/Status-benchmark-discovery-issues-27a8f96fb65c80e9bc09e356371556a0)
diff --git a/content/dst/status/2025q4-status-evaluation.md b/content/dst/status/2025q4-status-evaluation.md
@@ -93,18 +93,18 @@ Same as @Send one-to-one message - Network outage for private group
 #### Deliverables
 
 
-### Light node benchmark 2
+### Chat protocol benchmarks followup
 
-* fully qualified name: `vac:dst:status:2025q4-status-evaluation:light-node-benchmark-2`
+* fully qualified name: `vac:dst:status:2025q4-status-evaluation:chat-protocol-benchmarks-followup`
 * owner: Alberto
 * status: 0%
-* start-date:
-* end-date:
+* start-date: 2025/10/06
+* end-date: 2025/10/24
 
 #### Description
 
 Using the fix in the discovery process for the 
 [relay nodes](https://www.notion.so/Chat-Protocol-Benchmarks-1938f96fb65c80d8b22fdf641c5ff003?source=copy_link#1998f96fb65c8014bf0af42ce2645fa9)
-to repeat the benchmarks for only scenarios that use light nodes.
+to repeat the benchmarks adding light nodes in the same chat protocol benchmarks scenarios.
 
 #### Deliverables
diff --git a/content/dst/vac/2025q4-libp2p-evaluation.md b/content/dst/vac/2025q4-libp2p-evaluation.md
@@ -128,6 +128,40 @@ Perform a comparison between nim-libp2p using quic and waku using mplex and yamu
 - Related PRs if apply:
 
 
+### Mix in nim-libp2p node
+
+* fully qualified name: `vac:dst:ift:2025q4-libp2p-evaluation:mix-in-nim-libp2p-node`
+* owner: Farooq
+* status: 0%
+* start-date: 2025/10/06
+* end-date: 2025/10/17
+
+#### Description
+After refactor was done in `vac:dst:ift:2025q3-dst-tooling:nim-libp2p-dst-node-refactor`,
+include mix to the configuration options of the node.
+
+#### Deliverables
+- PRs:
+- Related Documents:
+
+### Go-libp2p node
+
+* fully qualified name: `vac:dst:ift:2025q4-libp2p-evaluation:go-libp2p-node`
+* owner: Farooq
+* status: 0%
+* start-date: 2025/10/06
+* end-date: 2025/10/24
+
+#### Description
+Include go-libp2p node to the [dst node repository](https://github.com/vacp2p/dst-libp2p-test-node).
+It should behave the same than the nim-libp2p node.
+Create a small deployment with both implementations using the same publisher.
+Report results of a single scenario (fixed parameters) using K8s and shadow.
+
+#### Deliverables
+- PRs:
+- Related Documents:
+
 ### Webtransport ?
 
 ### KAD-DHT ?
diff --git a/content/dst/waku/2025q3-waku-evaluation.md b/content/dst/waku/2025q3-waku-evaluation.md
@@ -189,4 +189,5 @@ and report js waku team any missing functionalities/issues.
 
 #### Deliverables
 - PRs:
+ - [Github PR: Add js-waku files #146](https://github.com/vacp2p/10ksim/pull/146)
 - Related Documents:
diff --git a/content/dst/waku/2025q3-waku-theoretical-analysis.md b/content/dst/waku/2025q3-waku-theoretical-analysis.md
@@ -52,7 +52,7 @@ ensuring that projects are built on well-reasoned analysis.
 
 * fully qualified name: `vac:dst:waku:2025q3-waku-theoretical-analysis:bandwidth`
 * owner: Farooq
-* status: 80%
+* status: 100%
 * start-date: 2025-09-17
 * end-date: 2025-09-30
 
@@ -74,7 +74,7 @@ in Kubernetes with the theoretical values.
 
 * fully qualified name: `vac:dst:waku:2025q3-waku-theoretical-analysis:message-dissemination`
 * owner: Farooq
-* status: 80%
+* status: 100%
 * start-date: 2025-09-17
 * end-date: 2025-09-30
 
diff --git a/content/dst/waku/2025q4-waku-scaling.md b/content/dst/waku/2025q4-waku-scaling.md
@@ -64,18 +64,16 @@ To have: Vac-DST: status-backend benchmarks
 
 
 ### Optimise Browser Bootstrapping
-> *Note*: This needs more input from project
 
 [Link to Waku FURPS](https://github.com/waku-org/pm/blob/master/draft-roadmap/improve_devex_api_twn_metrics_docs.md#optimise-browser-bootstrapping)
 
-* fully qualified name: `-`
-* owner: -
-* status: -
-* start-date: -
-* end-date: -
+* fully qualified name: `vac:dst:waku:2025q4-waku-scaling:optimise-browser-bootstrapping`
+* owner: Pearson
+* status: 0%
+* start-date: 2025-10-15
+* end-date: 2025-10-31
 
 #### Description
-Waku estimated date of completion: 31 Aug
 
 Using js-waku, prove that:
 - From an operating state, a node can 
@@ -167,4 +165,25 @@ Prove that:
 
 #### Deliverables
 - Code:
-- Report:
+- Report:
+
+
+### TWN supports RLN onchain tree and deposits, existing memberships only
+> *Note*: Moved from previous quarter
+
+[Link to Waku FURPS](https://github.com/waku-org/pm/blob/master/draft-roadmap/deploy_rln_onchain_tree_on_l2_testnet.md#twn-supports-rln-onchain-tree-and-deposits-existing-memberships-only)
+[Link to Waku FURPS](https://github.com/waku-org/pm/blob/master/draft-roadmap/rln_mainnet.md#twn-supports-rln-onchain-tree-and-deposits-existing-memberships-only)
+
+* fully qualified name: `vac:dst:waku:2025q4-waku-scaling:TWN-supports-RLN-tree`
+* owner: Alberto
+* status: 0%
+* start-date: 2025/10/06
+* end-date: 2025/10/24
+
+#### Description
+Prove that a new node setup with an RLN membership can be ready
+to verify RLN proof within 5s, no matter the size of the tree.
+
+#### Deliverables
+- Code: 
+- Report:
