diff --git a/content/nomos/updates/2024-09-30.md b/content/nomos/updates/2024-09-30.md
new file mode 100644
index 000000000..e3f1ffb75
--- /dev/null
+++ b/content/nomos/updates/2024-09-30.md
@@ -0,0 +1,72 @@
+---
+title: 2024-09-30 Nomos weekly
+tags:
+  - nomos-updates
+date: 2024-09-30
+lastmod: 2024-09-30
+draft: false
+description: Weekly update of Nomos
+project tracking: https://www.notion.so/Project-Tracking-4fb69250b0114573a71c57882165eec3
+---
+
+## `PPoS / Consensus / DA`
+
+### `Research`
+
+- Finished the [PoV integration specification](https://www.notion.so/Proof-of-Validator-Specification-5cd02f594d4d4a66be5e9f1ebf95d7d8?pvs=4#d07d5f29743b444395cba40f30239820).
+- [Studied](https://www.notion.so/Nomos-Tokenomics-Design-Canvas-e62e78ee0f8c4a719d1f6ffb08574241) a simple model for the tokenomics of a PoS utility token.
+- Updated the [Nomos Token Design Canvas](https://www.notion.so/Nomos-Tokenomics-Design-Canvas-e62e78ee0f8c4a719d1f6ffb08574241).
+- Added more context to the [DA dispersal specification](https://www.notion.so/NomosDA-Network-Specification-c6664294d630470ba20aefb21a218f8c?pvs=4#890a1860b2804e7ebd4c055688c3f9fe).
+- (WIP) Continued writing [NomosDA explainer series](https://www.notion.so/Encoding-1038f96fb65c8077a9f9f895327e5a05) first drafts.
+
+### `Development`
+
+- [PR #764](https://github.com/logos-co/nomos-node/pull/764) (Node): DA - Finished and merged replication changes.
+- Kickoff executor binary: We plan to add missing pieces of the architecture for the testnet. The first step is having a running executor. [PR #766](https://github.com/logos-co/nomos-node/pull/766) (Node) - created the binary crate. [PR #768](https://github.com/logos-co/nomos-node/pull/768) (Node) - implemented (composed) executor network behaviors and added Swarm. [PR #795](https://github.com/logos-co/nomos-node/pull/795) (Node) (WIP) - started network service implementation.
+
+## `Mixnet`
+
+### `Research`
+
+- In order to measure the latency and bandwidth of the Mix protocol, we prepared and ran a new experiment by introducing more realistic parameters simulating the behavior of the block leader (20s block time) and cover traffic, which is much lower than in previous experiments (performed to find the primary queuing mechanism) but still provides reasonable quality mixing. The report can be found [here](https://www.notion.so/Ordering-Experiments-Latency-Ordering-Coefficients-and-Bandwidth-1118f96fb65c80e29045c02a52fc4e07?pvs=4). Summary: We can meet the latency requirement (defined by the Nomos consensus protocol) if we limit the size of the Mix network to fewer than 100 nodes. However, the bandwidth consumption is under 80Kbps when the payload size is 320 bytes (i.e., block selection), but it exceeds 500Kbps when the payload size is 3200 bytes (= 100 tx refs * 32 bytes). This shows the difficulty of scaling to a large Mix network. We also need to clearly define the bandwidth requirement by specifying the payload size and related mechanisms.
+- Focused on improving documentation. Wrote the following documents, which went through a review (though some sections still require revision): [Introduction](https://www.notion.so/WIP-Nomos-Mix-Introduction-1058f96fb65c808abb1dcb33cc2ed417), [Tier 1](https://www.notion.so/WIP-Nomos-Mix-Tier-1-Persistent-Transmission-10b8f96fb65c807cb1e8f92a7f41a771), [Tier 2 (part 1)](https://www.notion.so/WIP-Nomos-Mix-Tier-2-Temporal-Mix-1058f96fb65c80f2b27bef71784a6da0), [Tier 2 (part 2)](https://www.notion.so/WIP-Nomos-Mix-Tier-2-Cryptographic-Mix-10b8f96fb65c80e8b8ebcf704b865d0b). These documents describe the design of the first iteration of the mixnet. The missing documents will add new features on top, such as (Tier 3) cover traffic and (Tier 4) incentivization mechanics.
+- Began estimating the minimal amount of bandwidth required.
+- Analysis of latency in the Nomos mix network: Considered the latency of broadcast in networks of size N with a topology of a random regular graph with connectivity ccc. For large N, a finite neighborhood of any node is a tree with branching factor c−1. Numerical analysis of broadcast latency in networks with topologies of random regular graphs and Cayley trees of various sizes suggests that the latter can be used to construct an upper bound for the former. We showed that broadcast latency on a tree can be computed recursively with numerical complexity O(N), which is better than O(Nlog⁡N) when Dijkstra's algorithm is used. The recursion on a tree was used to derive a recursive equation for the probability distribution of broadcast latency on trees with branching ratio c−1, i.e., the probability distribution of broadcast latency for a finite neighborhood of large regular graphs with connectivity c. This work is summarized [here](https://www.notion.so/Analysis-of-the-Nomos-Mixnet-Anonymous-Communication-AC-System-c97d73a7b8894cf7830e8345f0cc37a4?pvs=4#10a8f96fb65c8017a32eccbe8890bb5f).
+
+### `Development`
+
+- No updates this week.
+
+## `Coordination Layer`
+
+### `Research`
+
+- We’ve decided to postpone research on the Stwo wrapper for now, and we explained the reasons in [this document](https://www.notion.so/Preliminary-Research-Stwo-Wrapper-82f900dce90d4532be844c477b8cc618#10c8f96fb65c80f8ba8fd04bf8e8bec2). In summary: the optimizations in Stwo, which reduce proof size, complicate Merkle proof verification, requiring additional computations by the verifier, which conflicts with the goal of a simpler verification process. Additionally, significant rewriting of the prover is needed for compatibility, and emulating field operations from M31 to BLS could negatively affect performance. The time and effort required for implementation, parameter tuning, and handling Circle STARK verification are much greater than expected. Given these challenges, along with the fact that Risc0 already provides a working wrapper with fewer complications, the anticipated benefits of continuing this work no longer justify the effort.
+- Took notes on the ZkVM vs ZK Circuit discussion, shared [here](https://discord.com/channels/1111286067413405788/1111288089864843347/1288424246225408031) for future reference and added them to [this document](https://www.notion.so/ZKVM-s-vs-ZK-Circuits-1118f96fb65c80dc84c1d92acdc9611e).
+
+### `Development`
+
+- No updates this week.
+
+## `Zone and Apps`
+
+### `Research`
+
+- [Started research](https://www.notion.so/Initial-Zone-Research-10c8f96fb65c80c594c2fe2083469279) on zones, exploring key questions and drafting initial thoughts.
+
+### `Development`
+
+- No updates this week.
+
+## `Testnet and Tooling`
+
+### `Development`
+
+- [PR #797](https://github.com/logos-co/nomos-node/pull/797) (Node) - KZG-RS global params configuration for the testnet: updated configuration syncing between nodes and added Risc0 dependencies. After review, this can be deployed on testnet.nomos.tech.
+- [PR #767](https://github.com/logos-co/nomos-node/pull/767) and [PR #770](https://github.com/logos-co/nomos-node/pull/770) (Node) - CI: Jenkins nightly jobs update - Risc0 setup for Jenkins nightlies. Added dissemination test alongside consensus. Docker build job for GitHub PR check to track missing dependencies.
+
+## `Miscellaneous`
+
+- Created a blog content [plan](https://www.notion.so/Blog-Plan-Q4-2024-10c8f96fb65c802bb2c3dff5927dffb6) until the end of the year.
+
+