mirror of https://github.com/logos-co/roadmap.git
57 lines
4.6 KiB
Markdown
57 lines
4.6 KiB
Markdown
|
---
|
|||
|
title: 2024-02-19 Nomos weekly
|
|||
|
tags:
|
|||
|
- nomos-updates
|
|||
|
date: 2024-02-19
|
|||
|
lastmod: 2024-02-20
|
|||
|
draft: false
|
|||
|
description: Weekly update of Nomos
|
|||
|
---
|
|||
|
## `network privacy and mixnet`
|
|||
|
|
|||
|
### `research`
|
|||
|
|
|||
|
- Based on previous investigation, started a [document](https://www.notion.so/Populating-Mixnet-in-Cryptarchia-adf0ad10bd6b4c56b9597f7719b12092) about integrating the population strategy from Nym into the Cryptarchia setting. In it, while following an explicit staking assumption, it is assumed that a node that wants to be a mix node must register and stake on-chain. WIP with a lot of potential changes.
|
|||
|
|
|||
|
### `development`
|
|||
|
|
|||
|
- Implementation WIP: defining structure for mixnode / mixclient.
|
|||
|
- Implementation: concluded that the [nymtech/sphinx](https://github.com/nymtech/sphinx) crate can be used for our use case. For reference, previously we used a [wrapper of sphinx](https://github.com/nymtech/nym/tree/develop/common/nymsphinx) developed in the [nymtech/nym](https://github.com/nymtech/nym) codebase - but now, we can use the `nymtech/sphinx` crate as it is.
|
|||
|
- Modified libp2p to use QUIC. Replaced TCP with QUIC in the `nomos-libp2p` crate, which will be used by the `mixnet` network backend: [PR](https://github.com/logos-co/nomos-node/pull/580).
|
|||
|
- Fixed integration tests for QUIC. With the QUIC updates, some DA integration tests were failing - now they are working properly: [PR](https://github.com/logos-co/nomos-node/pull/581).
|
|||
|
|
|||
|
## `testnet`
|
|||
|
|
|||
|
### `development`
|
|||
|
|
|||
|
- Created a [document](https://www.notion.so/Key-Value-Database-943f54941d0347aa89a0de87ad9cc43a) regarding embeddable databases with their analysis. In more detail, the document includes benchmark code, analysis of several rust-based DBs, a proposal for which DB we should use, and example code for our most important use cases.
|
|||
|
|
|||
|
## `cryptarchia`
|
|||
|
|
|||
|
### `research`
|
|||
|
|
|||
|
- Updated the "Does Crypsinous’ Leader Election Function lead to wealth concentration in PoS?" [document](https://www.notion.so/Does-Crypsinous-Leader-Election-Function-lead-to-wealth-concentration-in-PoS-b81f07a791b745438443f51f00ac258f#126d293cf5ae4e46bb112a1b03cf5bf9) with new details about stake relativization - more precisely new simulations in regards to validators of certain ranges.
|
|||
|
- Started building out a NIZK (Non-interactive Zero-Knowledge) [Glossary](https://www.notion.so/NIZK-Glossary-089171eaa5b74f7ea765d1bcfc687cf1) of terms that will be used for internal education as well as writing the specification.
|
|||
|
- WIP: writing a how-to [guide](https://www.notion.so/How-to-Read-Write-an-NIZK-Spec-4efbe30df2ca48d9aacbab5b3e4a63d8) for reading/writing NIZK specifications. This will help us in the future when writing certain Nomos specifications.
|
|||
|
- Analysis of de-anonymization of relative stake: for adversarial inference of relative stake in the leader election process, considered statistical properties of (naive) maximum likelihood (ML) estimator of relative stake - in the naive ML approach, the relative stake of node i is obtained from the frequency of observed 1’s, representing vins in elections, and properties of lottery function. Also, analyzed statistical properties of the naive ML estimator of relative stake. [The consequences of the aforementioned results](https://www.notion.so/De-anonymisation-of-relative-stake-5b48f86bba3845c98f9b16f952307998) for the mixnet are in progress and will be shared in the future. To see the math behind the analysis check the [Overleaf document](https://www.overleaf.com/project/656dfacf4929b4a3d6d2ffe5).
|
|||
|
|
|||
|
### `development`
|
|||
|
|
|||
|
- No tangible updates - but Cryptarchia rust implementation is in progress, more details in the coming weeks.
|
|||
|
|
|||
|
## `data availability`
|
|||
|
|
|||
|
### `research`
|
|||
|
|
|||
|
- Initial DA API specification structure PR: defined mock zone, DA node and block producer to wrap DA spec and use it for encoding, dissemination and verification. Once the DA spec is near finalization, we will continue the mock implementation in python.
|
|||
|
- [DA Specification](https://www.notion.so/Data-Availability-Specification-4dd57aa0a212490c82b09d22bd2b9c30) updated per reviews and comments. Likely more changes on the way (depending on review).
|
|||
|
- Started a [document](https://www.notion.so/VeriZEXE-vs-Taiga-3ef9b9def27b4140bd752b0d49cba391) on studying VeriZEXE and Taiga designs. WIP, currently includes initial notes, likely to change.
|
|||
|
|
|||
|
### `development`
|
|||
|
|
|||
|
- Started implementing KZG core functionality of DA - more details in the upcoming weeks.
|
|||
|
|
|||
|
## `miscellaneous`
|
|||
|
|
|||
|
- Finalizing v0.6. of the darkpaper for internal release.
|
|||
|
- Finalizing the first [blog post](https://docs.google.com/document/d/15G9t6lE7CdqA7o-x8dLwZIyRrnbV-D5E0jyRaFjgphk/edit#heading=h.89r8n54lhgro) for internal release.
|