mirror of https://github.com/logos-co/roadmap.git
62 lines
6.5 KiB
Markdown
62 lines
6.5 KiB
Markdown
|
---
|
||
|
|
title: 2024-01-29 Nomos weekly
|
||
|
|
tags:
|
||
|
|
- nomos-updates
|
||
|
|
date: 2024-01-29
|
||
|
|
lastmod: 2024-01-30
|
||
|
|
draft: false
|
||
|
|
description: Weekly update of Nomos
|
||
|
|
---
|
||
|
|
## `network privacy and mixnet`
|
||
|
|
|
||
|
|
### `research`
|
||
|
|
|
||
|
|
- The Mixnet specification is ready for review and can be frozen with the current version for v1 (until we find additional requirements during the implementation).
|
||
|
|
- Defined the [mixnet topology update mechanism](https://www.notion.so/Mixnet-Specification-807b624444a54a4b88afa1cc80e100c2?pvs=4#af141ade3e8147ec900cf3599953f4da) as a result of internal team discussions - conclusion: we should abstract a robustness layer that will handle mixnet configuration.
|
||
|
|
- Redefined [mix destination](https://www.notion.so/Mixnet-Specification-807b624444a54a4b88afa1cc80e100c2?pvs=4#ebb923fa6a7443a0a36737906104343c): Instead of having an extra hop to the mix destination after `L` layers, we're going to use the last mix layer as the mix destination (for message reconstruction).
|
||
|
|
- Also, the problem of the common view of candidate nodes for mixnet participation was raised - how to ensure that the whole network will know which mixnodes are selected. As previously discussed, we confirmed that we need to have a dedicated staking action for registering candidate mixnet nodes on-chain - the sampling will be performed only from the list created by that staking action.
|
||
|
|
- The PRs that entail the changes and piece them all together in the executable mixnet specification can be found [here](https://github.com/logos-co/nomos-specs/pull/56) and [here](https://github.com/logos-co/nomos-specs/pull/57).
|
||
|
|
|
||
|
|
### `development`
|
||
|
|
|
||
|
|
- Added a couple of PRs in preparation for the mixnet rust development - [crate structure](https://github.com/logos-co/nomos-node/pull/570), [remove mixnet legacies 1](https://github.com/logos-co/nomos-node/pull/572), and [remove mixnet legacies 2](https://github.com/logos-co/nomos-node/pull/573).
|
||
|
|
|
||
|
|
## `testnet`
|
||
|
|
|
||
|
|
### `development`
|
||
|
|
|
||
|
|
- Started the [document](https://www.notion.so/Block-Explorer-4d32e6f08c144a3a9166d25512e0e339) on the design of Block Explorer 2. Also, added a [PR](https://github.com/logos-co/nomos-node/pull/566) regarding naive blocks query implementation from the storage layer (the PR is still open with an ongoing discussion).
|
||
|
|
- Added a testnet basic bot to the chatapp non-interactive mode ([PR](https://github.com/logos-co/nomos-node/pull/567)). In more detail, we have previously added the ability to disseminate a file to the DA in the testnet, and we updated the chatapp with a similar functionality, which is used to have a bot that constantly pushes readable data to our DA in the testnet. This data (as opposed to file upload) will be readable by our testnet users and will be useful during the demos.
|
||
|
|
- Container for the basic bot [PR](https://github.com/logos-co/nomos-node/pull/568) - performed some required changes to our testnet infrastructure.
|
||
|
|
|
||
|
|
## `cryptarchia`
|
||
|
|
|
||
|
|
### `research`
|
||
|
|
|
||
|
|
- Updated the wealth concentration analysis [chapter](https://www.notion.so/Does-Crypsinous-Leader-Election-Function-lead-to-wealth-concentration-in-PoS-b81f07a791b745438443f51f00ac258f?pvs=4#1df422f6cc204cb8b362f41cda260b8b) about stake relativization algorithm.
|
||
|
|
- Started the [Nomos Tokenomics Design Canvas](https://www.notion.so/Nomos-Tokenomics-Design-Canvas-e62e78ee0f8c4a719d1f6ffb08574241) that will be filled in with additional details in the future.
|
||
|
|
- We have [discussed](https://www.notion.so/Cryptarchia-c4975863a81644e5af03cdc9233b910b?d=74886dad62124b4e9cebee953b3cdfd5&pvs=4#d7521fcde86945409d1b6950743cbe4c) an alternative path for the leader election function (stake relativization) in the. Refer to this [comment](https://www.notion.so/5921382536f842c2bd4d9b61eb4174d0) for more details. This helped answer a high-priority question: [Do we need to learn total stake?](https://www.notion.so/Cryptarchia-c4975863a81644e5af03cdc9233b910b?pvs=4#d7aebd5d87d2437f93b749805918b59c)
|
||
|
|
- The initial version of the Cryptarchia executable specification [PR](https://github.com/logos-co/nomos-specs/pull/54) has been merged.
|
||
|
|
- Added [fork choice rule](https://github.com/logos-co/nomos-specs/pull/58) to the Cryptarchia executable specification.
|
||
|
|
- Merged [implementation of slot leader election check](https://github.com/logos-co/nomos-specs/pull/55) to the Cryptarchia executable specification.
|
||
|
|
- Analysis of [Impacts of Approximate Total Stake](https://www.notion.so/Impacts-of-Approximate-Total-Stake-1b9a248b222449c68c70fb645a733b03) - having considered two alternative election histories of a node (one when using the true stake and the other when using the approximate stake), the population study shows higher staked nodes are more impacted by errors in estimating total stake. Also, impact on the finality study shows high sensitivity to overestimates of stake. This was done by deriving the analytic expression for the Hamming distance between the two aforementioned histories which allows quantifying differences - for the detailed analytic work, refer to the [Overleaf document](https://www.overleaf.com/project/656dfacf4929b4a3d6d2ffe5).
|
||
|
|
|
||
|
|
### `development`
|
||
|
|
|
||
|
|
- No updates, heavily in research.
|
||
|
|
|
||
|
|
## `data availability`
|
||
|
|
|
||
|
|
### `research`
|
||
|
|
|
||
|
|
- [DA Layer Comparison article](https://www.notion.so/DA-Layer-Comparison-Table-5848811f0af042e2b24c10d3cea9b0a8) has been updated according to the latest review. In addition to that, we also provided details about the Ethereum Danksharding Protocol and its comparison to the Nomos DA protocol (according to our research).
|
||
|
|
- [VID Certificate section](https://www.notion.so/DA-Api-Specification-83000d9c2f3f45b586cd55c5c195cce5#5a4839bf7309499e810830474a11b1f5) in the DA API Specification has been added. In it, we explained the steps required to create VID Certificate and their order, described what data is sent to different participants (Nomos Zone, DA Node, Block Producer). We have reviewed it internally and added some new questions and comments - refer to the discussion for more details.
|
||
|
|
- Based on the definitions from the VID certificate, revised the [Block DA Metadata structure](https://www.notion.so/Block-Format-Specification-10c4cfef8b8946b8a54344cf97b16938#af86fcfa7fef40e9aabfc10f9f65f49a) with some minor updates, more precisely with the data that should be written in the block for DA.
|
||
|
|
|
||
|
|
### `development`
|
||
|
|
|
||
|
|
- No development updates.
|
||
|
|
|
||
|
|
## `miscellaneous`
|
||
|
|
|
||
|
|
- Finalized v0.5 of the darkpaper: updates according to feedback and new insights and strategy: rewritten several sections and eliminated a bunch of sections that were not satisfactory. Some changes of the darkpaper are conceptual, not just cosmetic, improving the strategical focus.
|