<li><ahref="https://www.notion.so/Mixnet-v2-Proof-of-Concept-102d0563e75345a3a6f1c11791fbd746?pvs=4"class="external">Planning</a> the Mixnet v2 PoC simulation (WIP): To simulate the behavior of the new design, we need to cover some design options (such as the way of broadcasting, etc.). We’ll create a simulator with these options to find the optimal design.</li>
<li><ahref="https://www.notion.so/Mixnet-v2-Proof-of-Concept-102d0563e75345a3a6f1c11791fbd746?pvs=4#12f00f18441049a893687f011ee3c683"class="external">Researched</a> the existing Mixnet simulators: They provide Python simulators focusing only on global passive adversaries (GPA) by measuring the Shannon entropy as a metric for anonymity (the uncertainty of linking an output message with a certain input message). We can adopt this practice for GPA analysis. For active adversary analysis, we need to figure out how to simulate tagging attacks and n-1 attacks (if necessary). For tagging attacks, we can probably perform an indirect analysis by measuring how many nodes a block is disseminated in before it’s selected/proposed.</li>
<li><ahref="https://www.notion.so/Requirements-for-PPoS-Network-Privacy-946893155a17459eb8f3a3165e3611f5"class="external">Summarized</a> the requirements for the Mixing gadget.</li>
<li>Optimization of mixnets: For a scenario when n nodes, sampled from N nodes with at most M adversarial nodes, we designed an algorithm. Given the number of nodes per layer n_1, the fraction of compromised paths which can be tolerated αmax, and the probability that the fraction of compromised paths is greater than 𝛼𝑚𝑎𝑥αmax, δ, the algorithm outputs the number of layers L: <ahref="https://www.notion.so/Analysis-of-failures-in-the-mix-network-feeef349720842759c59785af71c7c59#762ea606be4540b4877e5bde74cb652e"class="external">Summary</a>. The algorithm is implemented in Python, but the code needs further refinement.</li>
<li>Analysis of anonymity and communication failures in the mix gadget: Assuming that k nodes are sampled from N nodes, where at most M nodes are adversarial, we derived the probability that all k nodes are adversarial and the probability that at least one node is adversarial. The latter is the probability of communication failure, and the former is the probability of anonymity failure. The probability of anonymity failure decreases with k, and the probability of communication failure increases with k. We derived upper bounds on these probabilities. For large N, the probability of anonymity failure is bounded above by 2(𝑀/𝑁)𝑘/𝜋2(M/N)k/π, and the probability of communication failure is bounded by 1−𝜋(1−𝑀/𝑁)𝑘/21−π(1−M/N)k/2. Note that M in the latter corresponds not only to adversarial but also to “slow” nodes or nodes with bad connections. The <ahref="https://www.notion.so/Analysis-of-failures-in-the-mix-network-feeef349720842759c59785af71c7c59?pvs=4#5354ec4b641743709a2429327ef00ed3"class="external">summary</a> of this work is in progress.</li>
<li>Work on analysis of the new mix gadget design is currently in progress.</li>
<li>Initial DA protocol benchmarking uncovered 2 performance issues that will be addressed as soon as possible: <ahref="https://github.com/logos-co/nomos-node/tree/da-v1-encoding-benchmarks"class="external">WIP</a>.</li>
<li>Add Cert verification to DA mempool: - Merged payload to item conversion in mempool <ahref="https://github.com/logos-co/nomos-node/pull/634"class="external">PR</a>. Added certificate verification in da mempool <ahref="https://github.com/logos-co/nomos-node/pull/641"class="external">PR merged</a>.</li>
<li>DA Indexer service definition: Service that is responsible for DA API functionality, is able to track new blocks and assign metadata to previously attested chunks <ahref="https://github.com/logos-co/nomos-node/pull/643"class="external">PR</a>. Note that the service is defined, but other services like storage are not yet integrated. These missing pieces will be the focus of upcoming weeks.</li>
<li>Wealth concentration <ahref="https://www.notion.so/Does-Crypsinous-Leader-Election-Function-lead-to-wealth-concentration-in-PoS-b81f07a791b745438443f51f00ac258f"class="external">document</a> is in the process of reorganization with new studies being according to 8 parameters (see table 1 in the doc - we’re able to use way more realistic numbers as well, because software evolved), 3 classes of stakers (lower, mid, higher - we still lack a precise definition of them); and 3 fork-choice rules (lowest, highest, stochastic).</li>
<li>The first study assumes the relative stake is known and compares the 3 classes of stakers when the protocol enforces each of the 3 fork-choice rules under different parametrizations (sensitivity analysis).</li>
<li>The second study relaxes the assumption that the relative stake is known. We use and evaluate the impact of David and Alexander’s algorithm.</li>
<li>The third study relaxes the assumption that the protocol enforces the fork-choice rule. Each staker is allowed to use the rule of its choice.</li>
<li>Investigated the current state of the <ahref="https://github.com/logos-co/nomos-node/issues/637"class="external">orphan proofs problem</a>. After internal discussions, it was understood that this is a low priority for now, and we need to evaluate the real impact of this problem and how often it can happen first.</li>
<li>Completed the <ahref="https://www.notion.so/Proof-Systems-Survey-ffc625a2ff82407db7a45fd193136258"class="external">Proof Systems Survey</a>: added updates on aggregation, folding schemes, and some protocols. Also, listed and grouped libraries with existing implementations. This week, there will be more detailed explanations about these libraries.</li>
<li>Celestia ZK-Research Group messages have been summarized in a <ahref="https://www.notion.so/Celestia-ZK-in-the-Base-Layer-2be0ad708cff47fb844d1f1fac68b622"class="external">document</a> with annotations and discussions around parts that might be important to us.</li>
<li>Extended the metrics and visualizations <ahref="https://www.notion.so/On-metrics-insights-and-instrumentation-d8c8357b4e304fa3806f1b7f0e6b172d#b12d861deede4f71a31e33253c8e726a"class="external">document</a> by adding a planning block to match with yearly planning and resources.</li>
<li>Latest discussions triggered the need for yearly planning modifications: Wrote a <ahref="https://www.notion.so/Nomos-Engineering-planning-3-4Q-2024-f90859a189294419b13ae94682e96bf7"class="external">document</a> explaining year expectations + resources planning.</li>
<li>Created an initial Vac QA collaboration <ahref="https://www.notion.so/Nomos-node-testing-QA-15ae2611a23f4fe391c600c1b889c0ca"class="external">document</a> with cross-team interactions plan.</li>
<li>Milestone Execution plan has been <ahref="https://www.notion.so/2024-Milestone-Execution-Plan-62004acdaa5e4c65bd8c5b10e935e78b"class="external">published</a>.</li>
<li>Logos - Nomos update added - this will be an introductory one with focus on progress of research and engineering in the future.</li>
<li>New Nomos blog to be published this week with another to be set to review.</li>
