logos-co
/
roadmap
mirror of https://github.com/logos-co/roadmap.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

updated weeklies, monthlies

This commit is contained in:
Corey 2023-11-14 15:18:07 -05:00
parent 18b9031f6f
commit 6f1b8c6a37
8 changed files with 169 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
content/codex/updates/2023-11-03.md Normal file
View File

@ -0,0 +1,54 @@
---
title: 2023-11-03 Codex weekly
tags:
- codex-updates
date: 2023-11-03
lastmod: 2023-11-14
draft: false
description: Weekly update of Codex
---
# Codex Update Oct 24th - Nov 3rd
> The team is working towards deploying a beta testnet by the end of the year, and most work is centered around finishing all the required functionality for that.
## Client
### Epic: Block Merkelization
- Merkelization concrete PR in review
- https://github.com/codex-storage/nim-codex/pull/566
- Unifying the flows
- Making treeCid to be the same as treeRoot
- Storing proofs in key/value storage
### Epic: Wiring the Proving System
- Work on storage proofs is ongoing in https://github.com/codex-storage/codex-storage-proofs-circuits
- Work on Poseidon2 is being done in - https://github.com/codex-storage/nim-poseidon2
### Epic: Improve Client Stability
- Explored using CI flow for cloud-based benchmark harness, settled on Packer for image scripts [Packer scripts](https://github.com/codex-storage/debugging-scratchpad/tree/main/packer) - private repo
- Simple logging filtering/merging tool: [logtools](https://github.com/codex-storage/logtools)
- Microbenchmark of Sql backend in two separate VMs
- Ran remaining benchmarks, summary at [Benchmark Summary](https://653b015bed9280493c6a98bb--glowing-froyo-1db5ae.netlify.app/notebooks/repostore.html)
- Exploring behavior of nim-datastore and sqlite
- Continued working on a "quick-and-dirty" test setup, managed to get it working
- Quick PoC for a codex net deployed with Terraform on VMs: [Terraform main.tf](https://github.com/codex-storage/debugging-scratchpad/blob/main/terraform/main.tf)
- [Async Profiling](https://github.com/codex-storage/nim-codex/pull/600)
## Marketplace
### Epic: End-to-end Testing
- Further work on multinode integration testing
- [prevent stuck transactions by async locking nonce sequencing (+ estimate gas)](https://github.com/codex-storage/nim-ethers/pull/55)
- [On transaction failure, fetch revert reason with replayed transaction ](https://github.com/codex-storage/nim-ethers/pull/57)
- [Support logging to file](https://github.com/codex-storage/nim-codex/pull/558)
- [[fix] Ensure AsyncLock is released in case of exception ](https://github.com/codex-storage/nim-ethers/pull/58/files)
- [feat: ensure block expiry](https://github.com/codex-storage/nim-codex/pull/597)
## Infra
- Created Testnet Kubernetes cluster [56](https://github.com/codex-storage/infra-codex/issues/56)
- Deployed Testnet cluster basic components [57](https://github.com/codex-storage/infra-codex/issues/57)
- Configured DNS name for Testnet cluster [76](https://github.com/codex-storage/infra-codex/issues/76)
- Created Service Accounts in Testnet cluster [77](https://github.com/codex-storage/infra-codex/issues/77)
- Checked CORS issue on Codex Demo [79](https://github.com/codex-storage/infra-codex/issues/79)
- Configured TCP/UDP port forwarding for Testnet deployment [80](https://github.com/codex-storage/infra-codex/issues/80)

56
content/codex/updates/2023-11-10.md Normal file
View File

@ -0,0 +1,56 @@
---
title: 2023-11-10 Codex weekly
tags:
- codex-updates
date: 2023-11-14
lastmod: 2023-11-14
draft: false
description: Weekly update of Codex
---
# Codex Update Nov 6th - Nov 10th
> The team is working towards deploying a beta testnet by the end of the year, and most work is centered around finishing all the required functionality for that.
## Client
### Epic: Block Merkelization
- Merkelization concrete PR in review - mostly ready for merging
- https://github.com/codex-storage/nim-codex/pull/566
- Working on nim-datasotre to support atomic updates
- https://github.com/codex-storage/nim-datastore/pull/58
### Epic: Wiring the Proving System
- Merged conversion from field elements into bytes in nim-poseidon2
- https://github.com/codex-storage/nim-poseidon2/pull/6
- Added streaming API for Balazs's sponge in nim-poseidon2
- https://github.com/codex-storage/nim-poseidon2/pull/9
- Fixed merkle root construction for odd number of elements in nim-poseidon2
- https://github.com/codex-storage/nim-poseidon2/pull/8
- 2D erasure coding WIP
- https://github.com/codex-storage/nim-codex/pull/608
### Epic: Improve Client Stability
- Async profiling (it might actualy work)
- https://github.com/codex-storage/nim-codex/pull/600
- Prometheus metrics collector completed with tests
## Marketplace
### Epic: End-to-end Testing
- Addressed access issues within the marketplacesuite template, pinpointing a problem with a provider declared in ethertest and overcoming the challenge through deep template layer analysis.
- Discussions about improving the repostore maintenance module, specifically the method for returning bytes to Availabilities.
- Optimizing multinode integration tests, streamlining the process to enhance efficiency and performance.
- Integration test for the proving loop in the sales state module that was previously causing hang-ups, ensuring smoother operation.
- Progressed towards a cleaner integration test structure with the creation of a draft PR, setting the stage for more structured testing and deployment.
## Infra
- Configure TCP/UDP port forwarding for Testnet deployment [80](https://github.com/codex-storage/infra-codex/issues/80)
- Organize Grafana Dashboards [82](https://github.com/codex-storage/infra-codex/issues/82)
- Configure Continuous Tests automation [69](https://github.com/codex-storage/infra-codex/issues/69)
- Run Continuous Tests and check metrics
- Organize Grafana Dashboards
- Configure Continuous Tests automation enhancement
- Update Vector config
- Configure TCP/UDP port forwarding for Testnet deployment

BIN
content/images/Pasted image 20231114145512.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 308 KiB

9
content/insight/index.md
View File

@ -1,14 +1,15 @@
---
title: Insight Team Overview
---
## `insight:`
---
### Description
## Description
The insight team acts as a glue within the Logos Collective. They serve development projects by helping to track development activity and aiding in resource allocation. They serve the broader service units within the organization by helping them understand who's doing what, how much effort is going into each chunk of work, how much it costs, and future projections of milestone delivery.
This page tracks the various work that they engage in throughout the org. As this is a service unit and not a project, it does not strictly work off a milestone based approach and has consistent service work to the various groups within the Logos Collective.
### Current work
## Monthly Reports
- [[insight/monthly-reports/2023-oct|2023 October]]
## Current work
#### `dao:` [[insight/dao/index|details]]
#### `project-reporting:` [[insight/project-reporting/index|details]]

13
content/insight/monthly-reports/2023-oct.md
View File

@ -1,6 +1,6 @@
---
title: 2023 October Insights Monthly Report
draft: true
draft: false
lastmod: 2023-10-31
description: Monthly Report of Insights
---
@ -42,10 +42,8 @@ A technical roadmap has begun to be developed which outlines the process of "DAO
#### Contract Extension Negotiations with Sartography
- Summarizations provided by Eric in legal:
- Just to summarise where we’re at with Sartography as of the latest agreement, Sartography has indicated that they will develop additional SpiffWorkflow components called “SpiffWorkflow Extensions”. The negotiations with Sartography revolve around the issue ownership and licensing of the IP for these SpiffWorkflow Extensions as developed for Status. The points are as follows:
(i) Commercial license instead of an open source license: Originally all Spiffworkflow software would either be open source or be delivered to Status for its ownership. Sartography are insisting on deviating from this approach for the Extensions and intend to apply a commercial license to it. This is an unacceptable position. If they develop IP with Status’ money, then it must align with the original approach.
(ii) Waiver of fee for commercial license: Sartography have indicated that they are willing to “waive” the fee for any commercial license for the Extensions (referring this as a “gift” to Status). The terms of the commercial license will still need to be negotiated and are unknown to us right now. The waiver of a fee for a commercial license which we don’t have any view on may not be worth much if it turns out to be very restrictive.
- (i) Commercial license instead of an open source license: Originally all Spiffworkflow software would either be open source or be delivered to Status for its ownership. Sartography are insisting on deviating from this approach for the Extensions and intend to apply a commercial license to it. This is an unacceptable position. If they develop IP with Status’ money, then it must align with the original approach.
- (ii) Waiver of fee for commercial license: Sartography have indicated that they are willing to “waive” the fee for any commercial license for the Extensions (referring this as a “gift” to Status). The terms of the commercial license will still need to be negotiated and are unknown to us right now. The waiver of a fee for a commercial license which we don’t have any view on may not be worth much if it turns out to be very restrictive.
**An image of what Sartography aims to do, important to note this is not funded by Status:**
@ -54,13 +52,14 @@ A technical roadmap has begun to be developed which outlines the process of "DAO
For the avoidance of doubt, all “original” Spiffworkflow Software still aligns with our original agreed approach i.e. Sartography is obliged to keep it open source and any thing it delivers to Status will belong to Status who is obliged to make it open source.
**Path Forward** - Still needs to be finalized by legal; however, Sartography is building an ability to commercialize features that they are developing outside of development with Status. They will extend a commercial license to us and waive all fees associated _**if**_ Status uses any of those features. All feature they've expressed they are building are note features Status would leverage. For example, datastores for personal data and data stores for financial data.
**Path Forward** - Still needs to be finalized by legal; however, Sartography is building an ability to commercialize features that they are developing outside of development with Status. They will extend a commercial license to us and waive all fees associated _**if**_ Status uses any of those features. All feature they've expressed they are building are not features Status would leverage. For example, datastores for personal data and data stores for financial data.
#### Real Options Analysis
Frederico lead the way on developing a framework (and explainer) for performing Real Options Analysis on Keycard. Keycard was chosen based on its smaller project size and traditional evaluation methodology as a project (the easiest one to start with) with the goal in mind of generalizing the framework for all projects within Logos and Status. The current analysis and framework can be found [in Notion](https://www.notion.so/native/Keycard-s-Real-Option-Analyses-with-the-BSM-Model-526655fafd8f4af697a1d28211f325ba?deepLinkOpenNewTab=true) for now. Once finalized and reviewed, it may be released for public consumption.
This framework is expected to allow us to identify performance and evaluation trends for projects within their respective ecosystems, thus adding valuable insight to the decisions we as an org can make to steer them in the direction of success. More info on this can be seen in [Jarrad's previous townhall]() [LINK NEEDED] where he discussed it.
This framework is expected to allow us to identify performance and evaluation trends for projects within their respective ecosystems, thus adding valuable insight to the decisions we as an org can make to steer them in the direction of success. More info on this can be seen in [Jarrad's previous townhall](https://docs.google.com/presentation/d/1-G6Fbxsx3DlPv8Us9zkyWMBPQ3uYbGwd6a5Lm0ExTRU/edit?usp=sharing) (Org internal link - sorry - picture below for public) where he discussed it.
![[images/Pasted image 20231114145512.png]]
#### Revamping Accounting with Finance
Work continues with the Finance team to revamp the budgeting process for projects and services. The dashboard (mentioned below) being developed has helped track and monitor how money is being spent and allocated across the org.

26
content/nomos/index.md
View File

@ -7,47 +7,45 @@ tags:
lastmod: 2023-10-12
description: The Nomos project is an attempt to make a scalable, modular, and private L1. To learn more about the project, please visit https://nomos.tech. Nomos is currently in its initial phase as a project within Logos, namely the research and architecture design phase.
---
## `nomos:`
---
### Nomos Overview
## Nomos Overview
The Nomos project is an attempt to make a scalable, modular, and private L1. To learn more about the project, please visit [the website](https://nomos.tech)
Nomos is currently in its initial phase as a project within Logos, namely the research and architecture design phase.
#### Latest Monthly Report
- [[nomos/monthly-reports/2023-sept|2023-sept]]
### Latest Monthly Reports
- [[nomos/monthly-reports/2023-oct|2023 October]]
- [[nomos/monthly-reports/2023-sept|2023 September]]
### Current Key Milestones
## Current Key Milestones
#### `base-layer-spec:` [[nomos/base-layer-spec/index|details]]
### `base-layer-spec:` [[nomos/base-layer-spec/index|details]]
- due: 2024 Q1
- status: in progress
- description: Full specification of the Nomos Base Layer along with accompanying research and justification.
#### `base-layer-testnet:` [[nomos/base-layer-testnet/index|details]]
### `base-layer-testnet:` [[nomos/base-layer-testnet/index|details]]
- due: 2024 Q3
- status: in progress
- description:
#### `coord-layer-spec:`
### `coord-layer-spec:`
- due: 2024 Q4
- status: pending
- description:
#### `coord-layer-testnet:`
### `coord-layer-testnet:`
- due: 2025 Q1
- status: pending
- description:
---
### Delivered Milestones
#### `consensus-def:` [[nomos/consensus-def/index|details]]
## Delivered Milestones
### `consensus-def:` [[nomos/consensus-def/index|details]]
- due: 2023 Q3
- status: complete
- description: Research and specification of an underlying consensus algorithm to be used as foundation for Nomos.
---
### Useful Links
## Useful Links
- [Milestones Overview Notion Page](https://www.notion.so/ec57b205d4b443aeb43ee74ecc91c701?v=e782d519939f449c974e53fa3ab6978c): where the team updates their milestones before being transferred here.

46
content/nomos/updates/2023-11-06.md
View File

@ -1,5 +1,5 @@
---
title: 2023-10-30 Nomos weekly
title: 2023-11-06 Nomos weekly
tags:
- nomos-updates
date: 2023-11-06
@ -14,29 +14,39 @@ description: Weekly update of Nomos
### `development`
- Enriched cover traffic specs:- https://www.notion.so/Mixnet-Specification-807b624444a54a4b88afa1cc80e100c2?pvs=4#4fa4a0ba72ed44c28d5d5dd45422843c 
- Added a fallback for the case where mixnet fails: https://www.notion.so/Mixnet-Specification-807b624444a54a4b88afa1cc80e100c2?pvs=4#b9188f37004449d5b524fcd18ffceb0f 
- Enriched cover traffic specs: [Notion link](https://www.notion.so/Mixnet-Specification-807b624444a54a4b88afa1cc80e100c2?pvs=4#4fa4a0ba72ed44c28d5d5dd45422843c) 
- Added a fallback for the case where mixnet fails: [Notion link](https://www.notion.so/Mixnet-Specification-807b624444a54a4b88afa1cc80e100c2?pvs=4#b9188f37004449d5b524fcd18ffceb0f) 
- Nomos integration test stabilization
- Tune timeouts (by heavy debugging): https://github.com/logos-co/nomos-node/pull/492 https://github.com/logos-co/nomos-node/pull/494 
- Tune timeouts (by heavy debugging):
- https://github.com/logos-co/nomos-node/pull/492
- https://github.com/logos-co/nomos-node/pull/494 
- Prevent Duplicate error from libp2p gossipsub broadcasting: https://github.com/logos-co/nomos-node/pull/498 
- Fix port conflict: https://github.com/logos-co/nomos-node/pull/504 
- Store CI artifacts: https://github.com/logos-co/nomos-node/pull/508  https://github.com/logos-co/nomos-node/pull/510 
- Store CI artifacts:
- https://github.com/logos-co/nomos-node/pull/508 
- https://github.com/logos-co/nomos-node/pull/510 
- Mixnet implementation improvement
- Mixclient reconnect: https://github.com/logos-co/nomos-node/pull/501 
## `testnet`
### `development`
- Services APIs: https://github.com/logos-co/nomos-node/pull/476  https://github.com/logos-co/nomos-node/pull/487  https://github.com/logos-co/nomos-node/pull/488  https://github.com/logos-co/nomos-node/pull/489 
- Services APIs:
- https://github.com/logos-co/nomos-node/pull/476 
- https://github.com/logos-co/nomos-node/pull/487 
- https://github.com/logos-co/nomos-node/pull/488 
- https://github.com/logos-co/nomos-node/pull/489 
- Mempool aware of included blocks: https://github.com/logos-co/nomos-node/pull/485
- Voter attestation: https://github.com/logos-co/nomos-node/pull/498 
- Community PRs - typos: https://github.com/logos-co/nomos-node/pull/503  https://github.com/logos-co/nomos-node/pull/481 
- Community PRs - typos:
- https://github.com/logos-co/nomos-node/pull/503 
- https://github.com/logos-co/nomos-node/pull/481 
- Http API integration (Made the CI all green for the integrating PRs): https://github.com/logos-co/nomos-node/pull/490 
- Chat demo: https://github.com/logos-co/nomos-node/pull/495 
- Nomos node types (extract common types from nomos-node crate): https://github.com/logos-co/nomos-node/pull/496 
- Nomos update for demo call: https://www.notion.so/Nomos-update-November-2023-3b9a90935fce4e9083e6111210d0f101 
- Nomos update for demo call: [Notion link](https://www.notion.so/Nomos-update-November-2023-3b9a90935fce4e9083e6111210d0f101) 
- Static testnet configuration: https://github.com/logos-co/nomos-node/pull/499 
- In order to reliably expose all services when deployed, static configuration was added.
- Public deployment of temporal nomos testnet: ⁠general⁠
@ -55,27 +65,27 @@ description: Weekly update of Nomos
### `research`
- Multi-staking - prepared a discussion doc drafting a couple of ideas such as: how we can hide stake/voting power using homomorphic encryption and the consequences of that approach. The bottom line is that with Carnot and its tree structure we cannot follow the generic Proof of Stake approach and hide the voting power at the same time. We need to modify the Proof of Stake to follow the number of votes rather than the voting power during the vote aggregation phase. This modification bears consequences that need to be studied carefully, as the probability of a failure or liveness issues might be higher: https://www.notion.so/Discussing-Privacy-of-the-Multi-Staking-PoS-for-Carnot-BFT-with-homomorphisms-ab33e034c04d4a08be688cdb86eaa741 
- Rich Nodes Attack on Weighted Carnot worked out an attack that any private weighted-Carnot protocol will need to overcome: https://www.notion.so/Finding-Rich-Nodes-in-Weighted-Carnot-4a6e5964317a4765a05c46e600b69ac8 
- Private Weighted Voting w/ Ring Signatures a solution to the above attack that relies on ring signatures to break the connection between a vote and voter: https://www.notion.so/Private-Weighted-Voting-w-Linkable-Ring-Signatures-6efcf400716f401b86d42e59941d4849 
- From discussions on the above docs, started accumulating a summary of which behaviors to reward or penalize: List of Rewarded and Penalized Actions: https://www.notion.so/List-of-Rewarded-or-Penalized-Actions-3f0991ad8b4f494a9ba1d1edfb704f03 
- Multi-staking - prepared a discussion doc drafting a couple of ideas such as: how we can hide stake/voting power using homomorphic encryption and the consequences of that approach. The bottom line is that with Carnot and its tree structure we cannot follow the generic Proof of Stake approach and hide the voting power at the same time. We need to modify the Proof of Stake to follow the number of votes rather than the voting power during the vote aggregation phase. This modification bears consequences that need to be studied carefully, as the probability of a failure or liveness issues might be higher: [Notion link](https://www.notion.so/Discussing-Privacy-of-the-Multi-Staking-PoS-for-Carnot-BFT-with-homomorphisms-ab33e034c04d4a08be688cdb86eaa741) 
- Rich Nodes Attack on Weighted Carnot worked out an attack that any private weighted-Carnot protocol will need to overcome: [Notion link](https://www.notion.so/Finding-Rich-Nodes-in-Weighted-Carnot-4a6e5964317a4765a05c46e600b69ac8) 
- Private Weighted Voting w/ Ring Signatures a solution to the above attack that relies on ring signatures to break the connection between a vote and voter: [Notion link](https://www.notion.so/Private-Weighted-Voting-w-Linkable-Ring-Signatures-6efcf400716f401b86d42e59941d4849) 
- From discussions on the above docs, started accumulating a summary of which behaviors to reward or penalize: List of Rewarded and Penalized Actions: [Notion link](https://www.notion.so/List-of-Rewarded-or-Penalized-Actions-3f0991ad8b4f494a9ba1d1edfb704f03) 
- Derived a probability distribution for the weights of committees for a scenario  when weights of nodes, modeled as random variables, are sampled in every voting round.
- A derivation of a probability distribution for a scenario when weights of nodes are only sampled once (currently in progress).
- Wrote a simulation code which would  allow us  to compare failure probabilities in the above  two scenarios with the (unweighted) original Carnot version.
- Details for probability distribution for the weights of committees for a scenario when weights of nodes, modeled as random variables, are sampled in every voting round, are provided in https://www.overleaf.com/read/kkmsngmcgbkj#c4de95 
- Rewards for validators/delegators: the live document https://www.notion.so/Delegation-and-Validation-Rewards-d4af3f87a0b240739ff99b15af11cb3f?pvs=4 
- Research notes on rewards for validators/delegators: https://www.notion.so/Frederico-s-Research-Notes-b426cd773e214f35a5966f18d7db7588 
- List of Rewarded or Penalized Actions: https://www.notion.so/List-of-Rewarded-or-Penalized-Actions-3f0991ad8b4f494a9ba1d1edfb704f03 
- Rewards for validators/delegators: the live document [Notion link](https://www.notion.so/Delegation-and-Validation-Rewards-d4af3f87a0b240739ff99b15af11cb3f?pvs=4) 
- Research notes on rewards for validators/delegators: [Notion link](https://www.notion.so/Frederico-s-Research-Notes-b426cd773e214f35a5966f18d7db7588) 
- List of Rewarded or Penalized Actions: [Notion link](https://www.notion.so/List-of-Rewarded-or-Penalized-Actions-3f0991ad8b4f494a9ba1d1edfb704f03) 
## `data availability`
### `research`
- Finished the survey on the polynomial commitment schemes: https://www.notion.so/PCS-Survey-f06926a32c2d418897ff66fef1039a6e  
- Finished the survey on the polynomial commitment schemes: [Notion link](https://www.notion.so/PCS-Survey-f06926a32c2d418897ff66fef1039a6e)  
- PCS related libraries were examined. The structures and benchmarks used were reviewed. Resources related to this were added to the research notes above. 
- This work in particular is a nice compilation:https://xn--2-umb.com/23/pc-bench/ 
- Studied on EC+Commitment data structures. 1D or 1.5D structure may be more suitable for data availability within the scope of the Nomos project: https://www.notion.so/Erasure-Codes-Commitment-ea7c868255ad4f1a9ff9308d7f1df1c0 
- Studied on EC+Commitment data structures. 1D or 1.5D structure may be more suitable for data availability within the scope of the Nomos project: [Notion link](https://www.notion.so/Erasure-Codes-Commitment-ea7c868255ad4f1a9ff9308d7f1df1c0) 
### `development`

8
content/vac/monthly-reports/2023-oct.md Normal file
View File

@ -0,0 +1,8 @@
---
title: 2023 October Vac Monthly Report
date: 2023-10-30
lastmod: 2023-11-14
tags:
- monthly-report
draft: true
---