mirror of https://github.com/logos-co/roadmap.git
monthly updates (WIP)
This commit is contained in:
parent
c5e62848b5
commit
8cf79780a4
|
|
@ -0,0 +1,54 @@
|
||||||
|
---
|
||||||
|
title: 2023 October Codex Monthly Report
|
||||||
|
date: 2023-10-30
|
||||||
|
lastmod: 2023-10-30
|
||||||
|
draft: false
|
||||||
|
tags:
|
||||||
|
- monthly-report
|
||||||
|
- codex
|
||||||
|
---
|
||||||
|
## Executive Summary
|
||||||
|
In the first half of the month, the team had an Offsite which focused on concretizing solutions around the MVP and planning out the required work to deliver the MVP by the end of the year.
|
||||||
|
|
||||||
|
All work after the offsite this month has been focused on the tasked out work that was planned during the offsite.
|
||||||
|
|
||||||
|
The Ethereum Foundation collaboration on Data Availability Sampling is coming to an end, all of the work associated with it was summed up [here](https://hackmd.io/TYqF-wj2SIWwpS2F_PhWzg).
|
||||||
|
|
||||||
|
## Key Updates
|
||||||
|
|
||||||
|
### Personnel
|
||||||
|
A new job role was put up for a [Technical Business Development Lead for Codex](https://jobs.status.im/?gh_jid=5329400). This work will be dedicated to establishing and maintaining relationships with business partners interacting with the Codex Network. As the MVP and testnet get closer to launch, it is expected that these core relationships will need to be forged and cultivated.
|
||||||
|
|
||||||
|
- lots of upskilling and training new CCs (all people on client < 4 months old).
|
||||||
|
### Milestones
|
||||||
|
There was only one weekly update this month so it can be referenced for milestone updates, the link is down below.
|
||||||
|
|
||||||
|
The Ethereum Foundation collaboration on Data Availability Sampling is coming to an end, all of the work associated with it was summed up [here](https://hackmd.io/TYqF-wj2SIWwpS2F_PhWzg). A subsequent report will be created that looks at the pros and cons of the engagement to inform both other Logos projects and future similar Codex engagements.
|
||||||
|
|
||||||
|
- fat trimmed that wasn't required for MVP (maybe get a list of these things).
|
||||||
|
## Perceived Changes in Project Risk
|
||||||
|
The project maintains its track to deliver the Codex MVP by the end of the year. The offsite that took place mapped out the specific work to be done, and who is tasked to do it within the team.
|
||||||
|
|
||||||
|
more confident that it will be delivered on time based on scope of work and current team makeup and planning from off-site
|
||||||
|
|
||||||
|
there is no expected delay to delivering the MVP and testnet by the end of the year. and debugging infra for monitoring failures with testnet.
|
||||||
|
|
||||||
|
## Future Plans
|
||||||
|
|
||||||
|
### Insight
|
||||||
|
The Codex roadmap has yet to be ported over to this website, but now that the offsite is complete and the roadmap is more concrete, that transition should happen quickly within the next month.
|
||||||
|
|
||||||
|
This should allow us to ramp up the automated monitoring and create development activity dashboards. It is hoped that we have a development dashboard established by next month and a section within the monthly report that describes quantitative measurements of project development.
|
||||||
|
### Project
|
||||||
|
all focus is on current MVP and associated testnet
|
||||||
|
|
||||||
|
current MVP is minimum marketplace integrated with client and proving scheme. Proving scheme needs coding out and plugged into client. Need client itself to reflect recent changes in merkelization and block transfer.
|
||||||
|
|
||||||
|
get testnet up and running, internal (logos/status) dogfooding for this year's MVP, then to build monitoring and participation metrics over next year to prep for mainnet launch.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Sources and Useful Links
|
||||||
|
|
||||||
|
Weekly Reports
|
||||||
|
- [[codex/updates/2023-10-23|2023-10-23]]
|
||||||
|
|
@ -0,0 +1,26 @@
|
||||||
|
---
|
||||||
|
title: 2023 October Insights Monthly Report
|
||||||
|
draft: true
|
||||||
|
lastmod: 2023-10-31
|
||||||
|
description: Monthly Report of Insights
|
||||||
|
---
|
||||||
|
|
||||||
|
## Executive Summary
|
||||||
|
|
||||||
|
## Key Updates
|
||||||
|
|
||||||
|
### Personnel
|
||||||
|
- A senior and junior software engineer have been brought on to support the ongoing development of SpiffWorkflow.
|
||||||
|
|
||||||
|
### Milestones
|
||||||
|
|
||||||
|
## Perceived Changes in Project Risk
|
||||||
|
|
||||||
|
## Future Plans
|
||||||
|
|
||||||
|
### Insight
|
||||||
|
|
||||||
|
## Sources and Useful Links
|
||||||
|
|
||||||
|
Weekly Reports
|
||||||
|
-
|
||||||
|
|
@ -4,8 +4,10 @@ draft: true
|
||||||
lastmod: 2023-10-25
|
lastmod: 2023-10-25
|
||||||
description: "October 2023 Monthly Report of Nomos"
|
description: "October 2023 Monthly Report of Nomos"
|
||||||
---
|
---
|
||||||
|
|
||||||
## Executive Summary
|
## Executive Summary
|
||||||
|
October was marked with a continued push to finalized the architecture whitepaper, development of the Base Layer specification and the infrastructure required to create a testnet from the Base Layer MVP node implementation.
|
||||||
|
|
||||||
|
The whitepaper content is under review alongside some graphic design for a few of the more complicated figures.
|
||||||
|
|
||||||
## Key Updates
|
## Key Updates
|
||||||
|
|
||||||
|
|
@ -27,4 +29,5 @@ description: "October 2023 Monthly Report of Nomos"
|
||||||
Weekly Reports
|
Weekly Reports
|
||||||
- [[nomos/updates/2023-10-09|2023-10-09]]
|
- [[nomos/updates/2023-10-09|2023-10-09]]
|
||||||
- [[nomos/updates/2023-10-17|2023-10-17]]
|
- [[nomos/updates/2023-10-17|2023-10-17]]
|
||||||
- [[nomos/updates/2023-10-23|2023-10-23]]
|
- [[nomos/updates/2023-10-23|2023-10-23]]
|
||||||
|
- [[nomos/updates/2023-10-30|2023-10-30]]
|
||||||
|
|
@ -7,14 +7,14 @@ lastmod: 2023-10-10
|
||||||
draft: false
|
draft: false
|
||||||
description: Weekly update of <project>
|
description: Weekly update of <project>
|
||||||
---
|
---
|
||||||
### network privacy and mixnet:
|
## `network privacy and mixnet:`
|
||||||
|
|
||||||
#### :research
|
### `research:`
|
||||||
|
|
||||||
- Derived asymptotic expressions for anonymity and communication failure probabilities, when taking into account certain values for population size and network size. Used simulations and analytic framework to study failure probabilities in mixnets of different sizes. Assuming delays between sending and receiving messages are independent random variables from the exponential distribution, derived probability distribution of latency. Main result: one cannot have both low probability of communication and low probability of anonymity failures. The probability of anonymity failure is decreasing with the number of layers but at the expense of increasing the latency.
|
- Derived asymptotic expressions for anonymity and communication failure probabilities, when taking into account certain values for population size and network size. Used simulations and analytic framework to study failure probabilities in mixnets of different sizes. Assuming delays between sending and receiving messages are independent random variables from the exponential distribution, derived probability distribution of latency. Main result: one cannot have both low probability of communication and low probability of anonymity failures. The probability of anonymity failure is decreasing with the number of layers but at the expense of increasing the latency.
|
||||||
- Finalize research of network-level privacy solutions. Learned important information on: Framework for formalizing privacy, Nym and tokenomics of a Mixnet, Sphinx, and Loopix. Notes found at: https://www.notion.so/Network-Privacy-2dabf0aa878744e299b2ebb97120876f (summaries still WIP).
|
- Finalize research of network-level privacy solutions. Learned important information on: Framework for formalizing privacy, Nym and tokenomics of a Mixnet, Sphinx, and Loopix. Notes found at: https://www.notion.so/Network-Privacy-2dabf0aa878744e299b2ebb97120876f (summaries still WIP).
|
||||||
|
|
||||||
#### :development
|
### `development:`
|
||||||
|
|
||||||
- Lock Overwatch to a specific revision in nomos: https://github.com/logos-co/nomos-node/pull/455.
|
- Lock Overwatch to a specific revision in nomos: https://github.com/logos-co/nomos-node/pull/455.
|
||||||
- Implement and pipe services lifecycle handling in Overwatch: https://github.com/logos-co/Overwatch/pull/27.
|
- Implement and pipe services lifecycle handling in Overwatch: https://github.com/logos-co/Overwatch/pull/27.
|
||||||
|
|
@ -23,9 +23,9 @@ description: Weekly update of <project>
|
||||||
- Make libp2p gossipsub settings configurable: https://github.com/logos-co/nomos-node/pull/454.
|
- Make libp2p gossipsub settings configurable: https://github.com/logos-co/nomos-node/pull/454.
|
||||||
- Avoid temporary gossipsub errors when bootstrapping tests: https://github.com/logos-co/nomos-node/pull/442.
|
- Avoid temporary gossipsub errors when bootstrapping tests: https://github.com/logos-co/nomos-node/pull/442.
|
||||||
|
|
||||||
### testnet:
|
## `testnet:`
|
||||||
|
|
||||||
#### development:
|
### `development:`
|
||||||
|
|
||||||
- Skeleton for nomos API service - https://github.com/logos-co/nomos-node/pull/451.
|
- Skeleton for nomos API service - https://github.com/logos-co/nomos-node/pull/451.
|
||||||
- Support generics for overwatch derive - https://github.com/logos-co/Overwatch/pull/26.
|
- Support generics for overwatch derive - https://github.com/logos-co/Overwatch/pull/26.
|
||||||
|
|
@ -36,17 +36,17 @@ description: Weekly update of <project>
|
||||||
- Add canonical ID to attestations and certificates: https://github.com/logos-co/nomos-node/pull/448.
|
- Add canonical ID to attestations and certificates: https://github.com/logos-co/nomos-node/pull/448.
|
||||||
- Add functionalities to nomos-cli: https://github.com/logos-co/nomos-node/pull/450.
|
- Add functionalities to nomos-cli: https://github.com/logos-co/nomos-node/pull/450.
|
||||||
|
|
||||||
### private PoS:
|
## `private PoS:`
|
||||||
|
|
||||||
#### research:
|
### `research:`
|
||||||
|
|
||||||
- Exploring multi-staking PPoS design for Carnot.
|
- Exploring multi-staking PPoS design for Carnot.
|
||||||
- Idea: a slightly modified version of PoS, unknown how much funds a single validator has and validators are grouped by the amount of stake they have. This property gives validators group-based k-anonymity, where they are indistinguishable (on the stake level). This also enables us to assign the same voting power per each group of validators, which then can be reflected on the overlay structure.
|
- Idea: a slightly modified version of PoS, unknown how much funds a single validator has and validators are grouped by the amount of stake they have. This property gives validators group-based k-anonymity, where they are indistinguishable (on the stake level). This also enables us to assign the same voting power per each group of validators, which then can be reflected on the overlay structure.
|
||||||
- Considering a couple of additional stake hiding/obfuscating techniques without making the initial design too complex. We incentivize/penalize validators based not on the voting power they represent but on the stake. We can have a system that diverges from an equality between voting power and stake, to a system that approximates the voting power based on the stake but the rewarding/penalization directly follows the stake.
|
- Considering a couple of additional stake hiding/obfuscating techniques without making the initial design too complex. We incentivize/penalize validators based not on the voting power they represent but on the stake. We can have a system that diverges from an equality between voting power and stake, to a system that approximates the voting power based on the stake but the rewarding/penalization directly follows the stake.
|
||||||
|
|
||||||
### data availability:
|
## `data availability:`
|
||||||
|
|
||||||
#### development:
|
### `development:`
|
||||||
|
|
||||||
- DA nomos API based on the new skeleton: https://github.com/logos-co/nomos-node/pull/456.
|
- DA nomos API based on the new skeleton: https://github.com/logos-co/nomos-node/pull/456.
|
||||||
- Add API to return DA blobs: https://github.com/logos-co/nomos-node/pull/453.
|
- Add API to return DA blobs: https://github.com/logos-co/nomos-node/pull/453.
|
||||||
|
|
@ -0,0 +1,55 @@
|
||||||
|
---
|
||||||
|
title: 2023-10-30 Nomos weekly
|
||||||
|
tags:
|
||||||
|
- nomos-updates
|
||||||
|
date: 2023-10-30
|
||||||
|
lastmod: 2023-10-31
|
||||||
|
draft: false
|
||||||
|
description: Weekly update of Nomos
|
||||||
|
---
|
||||||
|
## `network privacy and mixnet:`
|
||||||
|
|
||||||
|
### `research:`
|
||||||
|
|
||||||
|
- Analysis of failure probability in random partitions of networks constructed from nodes with prescribed voting “weights” - derived equations for the probability of anonymity (communication) failure in the mix network of a large size, n, sampled from a large population of nodes of the size, N, such that n is comparable with N (https://www.overleaf.com/read/rybwvjftfrrg). Analysis of these equations is currently in progress.
|
||||||
|
- Set up a model of random partitions of networks where each node has a weight (https://www.overleaf.com/read/kkmsngmcgbkj#c4de95). Derivation of probability distributions for this model is currently in progress.
|
||||||
|
- We have agreed to put more effort into designing a fully weighted multi-staking privacy PoS design. The goal is to map the space of possible solutions (at least the subset of solutions that have been worked on and thought about lately) and their impact on the privacy, security and efficiency of the network.
|
||||||
|
|
||||||
|
### `development:`
|
||||||
|
|
||||||
|
- Mixnet specifications: Goals + Basic specs (implemented already) + Cover traffic - https://www.notion.so/WIP-Mixnet-Development-Specifications-807b624444a54a4b88afa1cc80e100c2
|
||||||
|
- Making Nomos & Mixnode stable for Testnet - Investigated/resolved CI failures: https://github.com/logos-co/nomos-node/pull/49
|
||||||
|
|
||||||
|
## `testnet:`
|
||||||
|
|
||||||
|
### `development:`
|
||||||
|
|
||||||
|
- Test nomos demo this week!
|
||||||
|
- Simulation overlay topology info: https://github.com/logos-co/nomos-node/pull/478 and https://github.com/logos-co/nomos-node/pull/479 - to understand better how the network topology looks inside a simulation with a large number of nodes, a way to visualise the network was added
|
||||||
|
- Simulation optional network capacity: https://github.com/logos-co/nomos-node/pull/483 - after discussing potential issues for getting baseline simulation results for networks with large number of nodes, the option to disable network capacity simulation was added. Advised the DST team to drastically increase the timeout number, so that the baseline will have all the nodes participating (happy path)
|
||||||
|
- Testnet consensus layer setup: https://github.com/logos-co/nomos-node/pull/482
|
||||||
|
- CI summary for long running integration tests: https://github.com/logos-co/nomos-node/pull/484
|
||||||
|
- Discussion about metrics service and prometheus - current http metrics service is fine, but its design is more fitting for the UIs rather than metrics collectors like prometheus. Explored this idea with libp2p (https://github.com/logos-co/nomos-node/pull/431), it seems like a good idea to have a node-wide service like node-http-api for prometheus metrics.
|
||||||
|
- Fix overwatch lifecycle refactor issue: https://github.com/logos-co/Overwatch/pull/31
|
||||||
|
- Sighandler service: https://github.com/logos-co/nomos-node/pull/480
|
||||||
|
- Implement da-blob API: https://github.com/logos-co/nomos-node/pull/487
|
||||||
|
- Implement storage API: https://github.com/logos-co/nomos-node/pull/488
|
||||||
|
- Implement add cert and add tx APIs: https://github.com/logos-co/nomos-node/pull/489
|
||||||
|
- Integrate the new HTTP backend to nomos-node: https://github.com/logos-co/nomos-node/pull/490
|
||||||
|
- Add http API to revive block contents from storage: https://github.com/logos-co/nomos-node/pull/473
|
||||||
|
- Add API to revive DA blobs: https://github.com/logos-co/nomos-node/pull/477
|
||||||
|
- Allow deprecated type in Swarm: https://github.com/logos-co/nomos-node/pull/486
|
||||||
|
|
||||||
|
## `private PoS:`
|
||||||
|
|
||||||
|
### `research:`
|
||||||
|
|
||||||
|
- Rewards for validators/delegators - the live document "Delegation and Validation Rewards": https://www.notion.so/Delegation-and-Validation-Rewards-d4af3f87a0b240739ff99b15af11cb3f?pvs=4
|
||||||
|
- Read up on Zarcanum (PPoS chain), not much to get inspired from them - https://www.notion.so/Private-Proof-of-Stake-182722d1bdef4894af1d56fece334eae#b8cc6b67f7334b41930bd091458dff2b
|
||||||
|
- Weighted-BRB - https://www.notion.so/Weighted-Byzantine-Reliable-Broadcast-in-front-of-PoS-consensus-d160a930522942ac98ebf42dc7c515bd
|
||||||
|
|
||||||
|
## `data availability:`
|
||||||
|
|
||||||
|
### `research:`
|
||||||
|
|
||||||
|
- Survey of polynomial commitment schemes - https://www.notion.so/Mehmet-5e698a9bba5d489aa058d3a695cda12f - work in progress, but-RS+KZG seems to be the more reasonable option for data availability at the first stage.
|
||||||
Loading…
Reference in New Issue