mirror of https://github.com/logos-co/roadmap.git
53 lines
4.1 KiB
Markdown
53 lines
4.1 KiB
Markdown
|
---
|
|||
|
|
title: 2023-12-25 Nomos weekly
|
|||
|
|
tags:
|
|||
|
|
- nomos-updates
|
|||
|
|
date: 2023-12-25
|
|||
|
|
lastmod: 2023-12-27
|
|||
|
|
draft: false
|
|||
|
|
description: Weekly update of Nomos
|
|||
|
|
---
|
|||
|
|
## `network privacy and mixnet`
|
|||
|
|
|
|||
|
|
### `research`
|
|||
|
|
|
|||
|
|
- Used bounds and asymptotic analysis to create a new version of the table (see [this](https://docs.google.com/spreadsheets/d/1MaSBbfUGmJniILPvcQLxtyXqjBExUUEB6C2-YWNP6uI/edit?usp=sharing) for reference) which estimates the number of layers needed in the mixnet protecting the network layer. The latter assumes a very simple lottery function where the probability of winning is equal to the relative stake.
|
|||
|
|
### `development`
|
|||
|
|
|
|||
|
|
- No updates
|
|||
|
|
## `testnet`
|
|||
|
|
|
|||
|
|
### `development`
|
|||
|
|
|
|||
|
|
- We are experiencing an [issue](https://github.com/status-im/infra-misc/issues/220) with the file system on `metal-01.he-eu-hel1.nomos.misc` entering a read-only state. This is preventing any write operations on the system, impacting normal operations and services.
|
|||
|
|
- Nomos node stability investigation - found a main reason for tesnet failing after some time, consensus engine has some asserts that are not met during the run. I'm trying to replicate the same behaviour in integration tests.
|
|||
|
|
|
|||
|
|
## `private PoS`
|
|||
|
|
|
|||
|
|
### `research`
|
|||
|
|
|
|||
|
|
- A [consensus reference page](https://www.notion.so/The-Consensus-From-the-Past-till-Today-e057b669032d43f0a90393f5383e3d4d?pvs=4 "https://www.notion.so/The-Consensus-From-the-Past-till-Today-e057b669032d43f0a90393f5383e3d4d?pvs=4") has been written detailing the path and the history of decisions made as a context to the other documents we have provided. It is important to mention that this is a living document that might be updated further in the future.
|
|||
|
|
- Updated the [ongoing document](https://www.notion.so/DarkFi-s-little-audit-8cd6d5bb461f434a8372856d57eb5353") of DarkFi Crypsinous implementation with new details.
|
|||
|
|
- [Summarized](https://www.notion.so/Byzantine-Gossip-Consensus-a83513712031444f80eb5f6097773b72) the findings and ideas from different papers around byzantine gossip and consensus. There are some ideas that might be useful to us in the future.
|
|||
|
|
- For the Crypsinous lottery function analyzed the maximum likelihood (ML) statistical inference framework. The latter can be used by an adversary for inference of stakes of nodes to infer relative stake. Formally the ML framework suggests that observations of election statistics of all nodes are required in order to infer relative stake of a single node. However, for long time observations there is a possibility that statistics for a single node are sufficient to infer its relative stake. The [analysis](https://www.overleaf.com/read/fzbrxvkwwscq#f2907c) of this scenario, which uses a “naive” estimator of relative stake, is currently in progress.
|
|||
|
|
- Normalize stake for leader lottery: Summary with plots and equations can be found [here](https://www.notion.so/Lottery-Function-65f5ed5522b64c36b625652023318d88?pvs=4#98db4a6ff8644792b2ee65bafd6ecdf2).
|
|||
|
|
- We have a new analytical tool for analyzing the average of our process for learning stake, it lets us study how the process converges without the slow simulation runs and makes analytical work much simpler.
|
|||
|
|
- We found that our process for learning D will underestimate true total stake by up to 3% (depends on our choice of constants), we have some analytical bounds on the underestimate and confirmed them with simulation.
|
|||
|
|
|
|||
|
|
## `data availability`
|
|||
|
|
|
|||
|
|
### `research`
|
|||
|
|
|
|||
|
|
- Finished the comparison [article](https://www.notion.so/Comparison-of-DA-Structures-47350a408cbd4d8db545527b7a598ccf) of DA structures (Merkle Tree, RS+KZG and Merkle Tree+Snarks) and reach the conclusion that the structure we designed is flexible. We can easily switch to the Merkle tree + Plonky2 structure in the future.
|
|||
|
|
- Some additional research notes in terms of DA comparison can be found [here](https://www.notion.so/DA-Research-Papers-Notes-9d4f26c736f347a985d6615e1c7e8789).
|
|||
|
|
- Skimming through [NOTRY: Deniable messaging with retroactive avowal](https://eprint.iacr.org/2023/1926) to check if there is anything interesting to us
|
|||
|
|
|
|||
|
|
### `development`
|
|||
|
|
|
|||
|
|
- No updates
|
|||
|
|
|
|||
|
|
### `miscellaneous`
|
|||
|
|
|
|||
|
|
- Architecture whitepaper will be reviewed internally by the team in the following weeks.
|
|||
|
|
|