mirror of https://github.com/logos-co/roadmap.git
49 lines
2.8 KiB
Markdown
49 lines
2.8 KiB
Markdown
|
---
|
||
|
|
title: 2023-10-17 Nomos weekly
|
||
|
|
tags:
|
||
|
|
- nomos-updates
|
||
|
|
date: 2023-10-17
|
||
|
|
lastmod: 2023-10-25
|
||
|
|
draft: false
|
||
|
|
description: 2023-10-17 Weekly update of Nomos
|
||
|
|
---
|
||
|
|
## `network privacy and mixnet:`
|
||
|
|
|
||
|
|
### `research:`
|
||
|
|
|
||
|
|
- Finalized the write up and summaries of the privacy network research - https://www.notion.so/Network-Privacy-2dabf0aa878744e299b2ebb97120876f (Pinned those notes that are the most important, to serve as a guidance for anyone who wants to have a quicker overview of the topic)
|
||
|
|
|
||
|
|
---
|
||
|
|
## `testnet:`
|
||
|
|
|
||
|
|
### `development:`
|
||
|
|
|
||
|
|
- Improved integration tests: https://github.com/logos-co/nomos-node/pull/458
|
||
|
|
- Preparing for demo
|
||
|
|
- Lifecycle handling: https://github.com/logos-co/nomos-node/pull/457
|
||
|
|
- A note on current testnet implementation. Realized that even with python code the configuration of mixnet and libp2p nodes are getting too complicated, nodes are still missing features and the glue code is not a solution in the long run. Will have more discussions.
|
||
|
|
|
||
|
|
---
|
||
|
|
## `private PoS:`
|
||
|
|
|
||
|
|
### `research:`
|
||
|
|
|
||
|
|
- Initial proposal for multi-staking PPoS design for Carnot: https://www.notion.so/Sketch-Approximated-PoS-with-k-anonymity-towards-multi-staking-for-Carnot-BFT-e066eb4f80114ddc862a8665aea952b6?pvs=4
|
||
|
|
|
||
|
|
---
|
||
|
|
## `data availability:`
|
||
|
|
|
||
|
|
### `research:`
|
||
|
|
|
||
|
|
- Sona polynomial commitment scheme was examined and found to be applicable to data availability. Comparisons and notes can be viewed here:https://www.notion.so/Polynomial-Commitment-Schemes-59bf8f6fe39840babe819c5c0a9628fc
|
||
|
|
- If we continue with KZG, the method to be followed for "trusted setup" was investigated. Some methods can be found here: https://www.notion.so/Trusted-Setup-19a29ee752f14e96895328a0bd7a9634
|
||
|
|
- Added notes on using prime field: https://www.notion.so/Notes-c4a680142a954953a2c0ea0e4b6fdcf1
|
||
|
|
|
||
|
|
|
||
|
|
---
|
||
|
|
## `Eurorust Event:`
|
||
|
|
Here are some notes by Daniel about the event the Engineering Team attended to last weekend:
|
||
|
|
- From the ecosystem speeches we can say they are constantly making efforts on making the language mature. impl Trait in traits are coming later this year, will impact our codebase (will need some refactors). It doesn't look like a big change but it kind of is. We use a lot of abstractions (futures + streams mostly) that force use to box everything (dynamic dispatch), that now will be statically dispatched.
|
||
|
|
- Overall keynotes and speeches were not really good. More exploratory than anything. Some of them showed tech that was mostly not relevant to us.
|
||
|
|
Gathering the team had some impact. We had some bonding on related topics that all of us enjoy. And we had some conversations that otherwise would not probably took place.
|
||
|
|
- IMO probably not worth to repeat this kind of events unless we participate in a more active way (preparing a speech ourselves and apply which I think we are totally capable of. We have a few things we could show up - Simulation app or Overwatch for example).
|