roadmap/content/nomos/updates/2024-08-05.md

---
title: 2024-08-05 Nomos weekly
tags:
  - nomos-updates
date: 2024-08-05
lastmod: 2024-08-05
draft: false
description: Weekly update of Nomos
project tracking: https://www.notion.so/Project-Tracking-4fb69250b0114573a71c57882165eec3
---
## `P2P Privacy`

### `Research`

- Nomos Mix simulations: message dissemination time by queue type - [Session 1](https://www.notion.so/Dissemination-Time-Session-1-8bb47f13500a48a79df71c4ef8da2f10?pvs=4): Measured message dissemination time using 20~80 number of nodes, for each 5 queue types. Noisy Coin-flipping queue shows the lowest dissemination time when there are less number of real messages flown in the network, but shows the worst, if not. Random Sampling queue or Permuted Coin-flipping queue show around 2x longer dissemination time compared to the Non-mixing queue, but the performance degradation is relatively low, as the number of real messages increase. This is the initial interpretation of the result, which we can't make a conclusion based on.
- Nomos Mix simulations: message dissemination time by queue type - [WIP: Session 2](https://www.notion.so/Dissemination-Time-Session-2-401a8d054609483e8e0a0d9e9414395e?pvs=4): This experiment is still running. This runs more nodes (100~10000) than the session 1, to see how each queue performs in the larger network. Also preparing next experiments: measuring how long messages stay in the queue.
- Extended the methodology document with more parameters for message dissemination experiments. Found one paper that measures properties of the Monero network which also include the node connectivity levels, an extract of it can be found [here](https://www.notion.so/Practical-Peering-Degree-Distribution-03c27169f59847ae95adaa3dc32456b0).
- Designed another [type of experiment](https://www.notion.so/Nomos-Mix-Queueing-Mechanism-Experimentation-Methodology-d629af5a2d43473c9ec9ba191f6d904d?pvs=4#4d38e8790ecd492a812c733bf140b864), that is devoted to observing the quality of “temporal mixing” for a single node on a single path. The results of which will give us better understanding of the predictability of delaying of each of the queues and guide our decision during the selecting process.
- The results for the first session of simulations give some intuition about the impact of each of the parameters on the dissemination time. However, it’s too early to conclude as the quality of mixing is another part of the equation and it’s our main focus now.
- Started looking at the payment mechanism for the mixnet.
- [Analysis](https://www.notion.so/Analysis-of-the-Nomos-Mixnet-Anonymous-Communication-AC-System-c97d73a7b8894cf7830e8345f0cc37a4?pvs=4#73b50a8df0364dee8754979e81f3b9ed) of the queueing system in the Nomos Mixnet node: considered the FIFO (First In First Out) attack where two sender nodes send messages through k mix nodes to the receiver node. The latter is controlled by an adversary which is also capable of observing other nodes. For a mix node where a message is removed from its out-queue with probability q, derived an expression for the probability of success of the FIFO attack. This probability can be computed numerically by creating a large population of random variables (wrote a code for the latter). Using this framework, showed that the probability of success of the FIFO attack is a monotonic decreasing function of the number of mix nodes k and is bounded from below by ½. Also showed that having different q parameters for sender and mix nodes can reduce the probability of success of the FIFO attack. Finally, showed that heterogeneous latencies of connections can increase the probability of success of the FIFO attack. 

### `Development`

- Prepared the [engineering PoC](https://www.notion.so/Mixnet-Engineering-PoC-342e4f229d1a4031900d4cc620e24c1f?pvs=4) in Notion.

## `Data Availability`

### `Research`

- DA [technical specification](https://www.notion.so/DA-Technical-Specification-c6664294d630470ba20aefb21a218f8c?d=dc11993b05bd484da36a858ac83fdbd8#3529ba28472b40ce8ae14cfc8f7a6132) has been updated.

### `Development`

- [PR #686](https://github.com/logos-co/nomos-node/pull/686): DA BlobInfo instead of Certificate - Removed Certificate and Attestation definitions, introduced DispersedBlobInfo trait and implementations. Also updated the DA mempool, integration tests and other components to use BlobInfo.
- (WIP) DA Mock network service for CLI app: still in progress preparing various components for the updated CLI App.
- [PR #685](https://github.com/logos-co/nomos-node/pull/685) - finished implementing/fixing the DA network replication layer.
- ([WIP](https://github.com/logos-co/nomos-node/tree/da-network-dispersal)) Started implementing the DA network dissemination layer - finished the validator behaviour and started the executor behaviour.

## `PPoS/Consensus`

### `Research`

- Finalized the [Proof of Validator specifications](https://www.notion.so/Proof-of-Validator-Specification-5cd02f594d4d4a66be5e9f1ebf95d7d8).
- [PR #10](https://github.com/logos-co/nomos-pocs/pull/10) - 2nd Proof of Validator in Circom with Caulk.
- The implementation for the [Caulk usage scenario](https://github.com/logos-co/nomos-pocs/pull/10/commits/7f4ccde70f74344c6690234b2db41631e6a95efa) was prepared, and the results were added to the document.
- Started [analyzing](https://www.overleaf.com/7427853156xhwkfrqbrphd#ddda76) the usage of the PoL as a PoV.
- Finalizing reports 1 and 2 of the wealth concentration work: the [results](https://www.notion.so/Does-Crypsinous-Leader-Election-Function-lead-to-wealth-concentration-in-PoS-b81f07a791b745438443f51f00ac258f?pvs=4#1df422f6cc204cb8b362f41cda260b8b) are mostly in shape.

### `Development`

- No updates this week.

## `Coordination Layer`

### `Research`

- [PR #17](https://github.com/logos-co/nomos-pocs/pull/17): integrate the zone withdrawal logic with CL ptx/note structure.
- [PR #13](https://github.com/logos-co/nomos-pocs/pull/13): users could create as many zero-valued outputs as they'd like without affecting the balance of a partial tx, the implications of this was not clear so we decided to ban zero-valued outputs for now until we understand what is going on.
- [PR #14](https://github.com/logos-co/nomos-pocs/pull/14): boilerplate for the user atomic transfer ptx.

### `Development`

- No updates this week.

## `Testnet + Insights`

### `Development`

- No updates this week.

## `User Tools`

### `Research`

- No updates this week.

### `Development`

- No updates this week.

## `Miscellaneous`

- No updates this week.