mirror of https://github.com/logos-co/roadmap.git
weekly updates
This commit is contained in:
parent
bc32f912c2
commit
2d50872555
|
|
@ -7,9 +7,6 @@ lastmod: 2023-10-10
|
|||
draft: false
|
||||
description: Weekly update of Comms
|
||||
---
|
||||
## `acid`
|
||||
---
|
||||
|
||||
### Overview/Priorities
|
||||
- Comments from the BUs about blockers and miscommunications - Reevaluation of our comms strategy: BUs are responsible for DevRel, BD, and technical content. We’re responsible for QC of outgoing content (wordsmiths, video editing, and packaging) and non-technical content. This will be communicated with them and consolidated along with the strategy asap.
|
||||
- New Mantra: Brand awareness and Learning Communities, which are both measurable by proxy. This means we focus more on performance and growth KPIs and reporting these clearly to C/J.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,74 @@
|
|||
---
|
||||
title: 2023-10-25 Comms weekly
|
||||
tags:
|
||||
- acid-updates
|
||||
date: 2023-10-17
|
||||
lastmod: 2023-10-25
|
||||
draft: false
|
||||
description: Weekly update of <project>
|
||||
---
|
||||
|
||||
**ACID ROUND UP - OCT. 17**
|
||||
|
||||
**Overview/Priorities**
|
||||
|
||||
- Workflows / Champions model: Reporting structure necessary.
|
||||
- Reporting to C+J: ClickUp dashboards.
|
||||
- Brand Guidelines: In process of improvements.
|
||||
- Istanbul NSF event cancelled. Will find more opportunities in first half of 2024.
|
||||
|
||||
**Tech & Design**
|
||||
|
||||
- LSD finetuning.
|
||||
- Nomos team requested executable code inside documentation website.
|
||||
- Documentation for Docusaurus site. Every BU can deploy their own documentation
|
||||
- Integrating the Logos job listings on IFT website - working with JB and Flo.
|
||||
- No integrated requirement checklist for what the roadmap should be for all the org. It is not clear if this is one project or several. Different reporting structures per BU makes this complex. Focus on task / “bounty” list
|
||||
- Finish up guidelines pages
|
||||
|
||||
**Digital Content Studio**
|
||||
|
||||
- Ana (new visual designer) joined last week. Helping on branding designs.
|
||||
- Podcast templates for cutout animations are good to go. Match options for outputs.
|
||||
- Twitter Spaces has an overlap with podcast pipeline. Jarrad also wants a easy going convo type setup for his own thinking and this is a bit. Needs to sync with MF.
|
||||
- Matt and Nick sign off on LPE Article Headers/Social images
|
||||
|
||||
**Podcast**
|
||||
|
||||
- Quality control got version of Jordi Baylina episode with new graph. Will be ready soon.
|
||||
- Snowden episode needs a change in the graph at the beginning and needs date change when we know it will launch
|
||||
|
||||
**Copy**
|
||||
|
||||
- Doc sites are all live except for Waku - pending some small changes.
|
||||
- Nimbus websites might be getting close to launch.
|
||||
- Carl asked for a beginner series for the network state concept, including a call to action that makes it easy for them to get to the beginner friendly content.
|
||||
- IFT copy is in Carl’s hands and we are waiting for review.
|
||||
- 3 tech one pagers for Matt and the fundraising team are done.
|
||||
|
||||
**Movement Building**
|
||||
|
||||
- Twitter Spaces idea for each BU is being discussed internally. Ideas to use https://docs.google.com/document/d/1yOPPsZqKzf6__zuCsFYRsDDkk-lYX--vjRoz6e7OYK4/edit
|
||||
- Working on events stuff and postponing Network State Forum event for next year
|
||||
- We are running and testing ads on promoting our Twitter Spaces and have pivoted to growing our brand following online to lead into a big event. Potentially hackathon around the all hands meeting etc.
|
||||
- PR company: onboarding is happening, they are asking good questions there
|
||||
- Status: Launch the community campaign. John wants to launch Nov 1.
|
||||
- Paid Twitter Ads: Carl asked to run test ad. 2k for Logos space tweet. so far, 800k impressions. 125 followers gained so far. We will use this for benchmarking.
|
||||
- NSP: held up as Jarrad is reviewing content and Carl is pending.
|
||||
- Waku: feedback from Rome, mentioned that people come to them what is Waku/Status/Logos and how does everything fit. They don’t have a clear answer. We are fixing this.
|
||||
- Talking to Lou re: events, we can approach Waku marketing as short term campaigns initially November-December. Will propose an awareness campaign to see what can be done with existing resources.
|
||||
|
||||
**Events**
|
||||
|
||||
- Different scenarios for Istanbul. Looking at whether we co-sponsor EthGlobal Istanbul.
|
||||
- Waku will be doing EthGlobal India. EthGlobal Istanbul too expensive (40k) for Waku alone so we might co-sponsor.
|
||||
- Speaking to EthDenver for next year + an Africa strategy for Waku.
|
||||
- Set up and manage events and KPIs and reporting in Click Up via forms that external people to the comms team can fill in.
|
||||
- We need a proper lead time for activation campaigns to maximise participation, social awareness etc. This is in planning.
|
||||
- Video footage from EthCC Paris event still unedited. If there are requests, we can edit it for that purpose.
|
||||
- Writing a brief for event managers
|
||||
|
||||
**Project Management**
|
||||
|
||||
- Workflows reviews and optimizations based on strategy, goals and champions model
|
||||
- PM and reporting set-up in ClickUp
|
||||
|
|
@ -0,0 +1,61 @@
|
|||
---
|
||||
title: 2023-10-25 Comms weekly
|
||||
tags:
|
||||
- acid-updates
|
||||
date: 2023-10-24
|
||||
lastmod: 2023-10-25
|
||||
draft: false
|
||||
description: Weekly update of Comms
|
||||
---
|
||||
|
||||
**Overview/Priorities**
|
||||
|
||||
- We are on the right track re: reporting, champions model and outputs. Full update here: https://doc.clickup.com/9009185920/p/h/8cfuh40-13894/965f96f62ea5053
|
||||
|
||||
**Tech & Design**
|
||||
|
||||
- IFT website desktop version almost ready
|
||||
- Logos Brand Guidelines are being updated
|
||||
- Docusauraus updates - workshop for BUs to enable them to do content updates
|
||||
- Jobs will be added to every BU website and IFT
|
||||
|
||||
**Digital Content Studio**
|
||||
|
||||
- Content guidelines in the works, summarising everything and putting it all together to make it functional.
|
||||
- Swag and presentations are coming in according to plan - nothing of note.
|
||||
- Jonny working on proposal for NPS UX/structure in Figma based on conversation with nick and Amir yesterday
|
||||
|
||||
**Podcast**
|
||||
|
||||
- Pulling together detailed rollout doc with assets and exact copy for Al to send to Snowden and Assange for approvals and coordination.
|
||||
- Get Stella out - audio quality is much better than Snowden’s so it’s good to go.
|
||||
|
||||
**Copy**
|
||||
|
||||
- IFT is ready and getting published by EOW.
|
||||
- No news for copy re: NSP. Soft launch projected for this week for NSP.
|
||||
- Beginner friendly piece by Rick for NSP is in production.
|
||||
- Event promotion for Logos EthGlobal Pragma presence.
|
||||
- Social buffer for Logos is set and ready. In depth threads re: philosophy and connection with each part of the tech stack.
|
||||
|
||||
**Movement Building**
|
||||
|
||||
- Logos Discord structure: https://docs.google.com/document/d/1N0vgj7GIHllJ9YI912WdMetSEELMBzuWbRKl8NXjXCA/edit#heading=h.ebfdikfy2j9v
|
||||
- Logos Forum gets traffic due to paid ads, please pay attention and move discussions there as much as is natural.
|
||||
- Feedback from Jarrad: we need to focus on creating shareable cultural artifacts. For example, transcribing Twitter spaces into forums. Lazar suggested using the radical _anarchy salon content too.
|
||||
- Soft launch of NSP will happen this end of week. Next week we go with main launch.
|
||||
- Twitter paid ads were running on space. Report is complete and ready to be shared.
|
||||
- Growth strategy with Logos paid ads and Network state paid ads will be completed soon and shared with all.
|
||||
- Legal: long story short is they will ask to have the least possible changes to the privacy policy but changes we asked for should be ready to be implemented.
|
||||
|
||||
**Events**
|
||||
|
||||
- Waku will be the main brand at ETHGlobal Istanbul to avoid confusion and to optimise
|
||||
- Logos will be present at Pragma - we maximise brand awareness and want to test
|
||||
- Wider event marketing campaign needs to be clear. Distinct posts, tracking impact.
|
||||
- Dashboard on ClickUp for KPIs is in the works. Focus on optimising event attendance vs cost and resources.
|
||||
- 2024 is in the works. Africa events outline for Waku, ETH Denver already contacted.
|
||||
|
||||
**Project Management**
|
||||
|
||||
- Setting up workspace, PM and reporting in click up with teams and get audit with Clickup experts. Onboarding next week.
|
||||
|
|
@ -0,0 +1,56 @@
|
|||
---
|
||||
title: 2023-10-25 Codex weekly
|
||||
tags:
|
||||
- codex-updates
|
||||
date: 2023-10-23
|
||||
lastmod: 2023-10-25
|
||||
draft: false
|
||||
description: Weekly update of Codex
|
||||
---
|
||||
|
||||
# Codex Update Oct 2 - 23
|
||||
|
||||
> We had a teamwide offsite in Crete from October 6th to the 12th, during which we were able to discuss and come up with concrete solutions around several important pieces of the project aspects such as the proving system and the contract start interactions, as well as plan out outstanding work for our upcoming testnet launch at the end of the year. The meeting was very productive and it helped align the team around the current and future outstanding work in order to hit our big end of year milestone.
|
||||
|
||||
## Client
|
||||
|
||||
### Milestone: Block Merkelization
|
||||
- Merkelization concrete PR in review
|
||||
- https://github.com/codex-storage/nim-codex/pull/566
|
||||
|
||||
### Milestone: Block Exchange protocol refinements and simulations
|
||||
- Some results were presented during the offsite
|
||||
- https://rpubs.com/giuliano_mega/codex-swarms
|
||||
|
||||
### Milestone: Async Disc Access & Threading support
|
||||
- Work on IO threads support (not much progress due to offsite, will be picked up asap)
|
||||
- All related PRs are here https://github.com/codex-storage/nim-datastore/pulls
|
||||
- We now how a clear idea of how to implement and integrated it - https://github.com/codex-storage/nim-codex/pull/552
|
||||
|
||||
### Milestone: Sampling and Storage Proofs
|
||||
- Work on storage proofs is ongoing under https://github.com/codex-storage/zk-research-artifacts/tree/master/storage_proofs
|
||||
- A circom implementation is being worked on in https://github.com/codex-storage/zk-research-artifacts/tree/master/storage_proofs/MVP/circuit
|
||||
- Reference/testing implementation to consume the circuits is done here https://github.com/codex-storage/zk-research-artifacts/tree/master/storage_proofs/MVP/reference
|
||||
- Analysis of the sampling strategies are available here https://github.com/codex-storage/zk-research-artifacts/tree/master/sampling
|
||||
|
||||
### Milestone: Client stability and debugging
|
||||
- Major effort to stabilize the Codex client through continuous automated testing
|
||||
- Work on better log analysis is being done here https://github.com/gmega/logtools
|
||||
- Running several load tests with ˜100 nodes using the dist testing framework https://github.com/codex-storage/cs-codex-dist-tests
|
||||
|
||||
## Infra
|
||||
- Investigating and fixing issues related to Elasticsearch logshipping
|
||||
- [Install Loki in Dist-Tests cluster](https://github.com/codex-storage/infra-codex/issues/55)
|
||||
- [Fix Vector errors related to the Kubernetes logs shipping](https://github.com/codex-storage/infra-codex/issues/66)
|
||||
- [Configure Vector to ship Dist/Continuous-Tests logs to Loki](https://github.com/codex-storage/infra-codex/issues/69)
|
||||
|
||||
## Research
|
||||
|
||||
### Milestone: Publications
|
||||
- White paper ongoing - https://docs.google.com/document/d/1LCy23m90IHf32aUVhRT4r4772w1BfVcSLaJ0z9VTw9A/edit#heading=h.qs3bayckj5u4
|
||||
|
||||
## DAS
|
||||
|
||||
### Milestone DAS
|
||||
- Our current engagement with the EF is coming to an end a summary of the work done has been collected here
|
||||
- https://hackmd.io/TYqF-wj2SIWwpS2F_PhWzg
|
||||
|
|
@ -0,0 +1,30 @@
|
|||
---
|
||||
title: 2023 October Nomos Monthly Report
|
||||
draft: true
|
||||
lastmod: 2023-10-25
|
||||
description: "October 2023 Monthly Report of Nomos"
|
||||
---
|
||||
|
||||
## Executive Summary
|
||||
|
||||
## Key Updates
|
||||
|
||||
### Personnel
|
||||
-
|
||||
|
||||
### Milestones
|
||||
|
||||
## Perceived Changes in Project Risk
|
||||
|
||||
## Future Plans
|
||||
|
||||
### Insight
|
||||
|
||||
### Project
|
||||
|
||||
## Sources and Useful Links
|
||||
|
||||
Weekly Reports
|
||||
- [[nomos/updates/2023-10-09|2023-10-09]]
|
||||
- [[nomos/updates/2023-10-17|2023-10-17]]
|
||||
- [[nomos/updates/2023-10-23|2023-10-23]]
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
---
|
||||
title: Nomos Monthly Reports
|
||||
---
|
||||
Here are the monthly reports that are generated.
|
||||
Here are the monthly reports that are generated for Nomos.
|
||||
|
|
@ -7,8 +7,6 @@ lastmod: 2023-10-10
|
|||
draft: false
|
||||
description: Weekly update of <project>
|
||||
---
|
||||
## `nomos:`
|
||||
---
|
||||
### network privacy and mixnet:
|
||||
|
||||
#### :research
|
||||
|
|
|
|||
|
|
@ -0,0 +1,49 @@
|
|||
---
|
||||
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).
|
||||
|
|
@ -0,0 +1,60 @@
|
|||
---
|
||||
title: 2023-10-25 Nomos weekly
|
||||
tags:
|
||||
- nomos-updates
|
||||
date: 2023-10-23
|
||||
lastmod: 2023-10-25
|
||||
draft: false
|
||||
description: 2023-10-23 Weekly update of Nomos
|
||||
---
|
||||
## `network privacy and mixnet:`
|
||||
|
||||
### `research:`
|
||||
|
||||
- Set up a calculation for the probability of anonymity (communication) failure in the mix network of a large size, sampled from a large population of nodes, such that mix network size is comparable with the node population size. The latter is the most challenging regime to analyse but potentially can give us much more accurate estimates of probabilities. Previously we have analysed regimes when mix network size is much smaller than network size and when all nodes in the network are also used in the mix network.
|
||||
- Notes on “Anonymity Trilemma: Strong Anonymity, Low Bandwidth Overhead, Low Latency - Choose Two” paper provided in the overleaf document. https://www.overleaf.com/read/rybwvjftfrrg ; The latter derives necessary conditions for anonymous communication in terms of latency, amount of noise messages and some measure of anonymity.
|
||||
|
||||
### `development:`
|
||||
|
||||
- Mixnet development specifications: went through the Loopix paper again - writing the draft specs: https://www.notion.so/WIP-Mixnet-Development-Specifications-807b624444a54a4b88afa1cc80e100c2 (covering the current Loopix-based implementation + Future work: cover traffic, multicasting (TBD), incentivization (TBD))
|
||||
|
||||
## `testnet:`
|
||||
|
||||
### `development:`
|
||||
|
||||
- Save block contents to storage - https://github.com/logos-co/nomos-node/pull/464
|
||||
- Refactoring for future content - https://github.com/logos-co/nomos-node/pull/461
|
||||
- Services state watchers - added a first version so overwatch can await for other services signal that they are ready to work. First version using relay did not work (among other things, too complicated). Second version uses an aditional handle per service, it is morestraight forward. It may add more intricated relationship among services, and they cannot be handled/caught on runtime. Testing only for now.
|
||||
- Failing services status PR: https://github.com/logos-co/Overwatch/pull/29
|
||||
- Working services status PR: https://github.com/logos-co/Overwatch/pull/30
|
||||
- Update lifecycle handling: https://github.com/logos-co/nomos-node/pull/457
|
||||
- Generics metrics API: https://github.com/logos-co/nomos-node/pull/466
|
||||
- Human readable ser/deser for array based types: https://github.com/logos-co/nomos-node/pull/468
|
||||
- Update libp2p breaking changes: https://github.com/logos-co/nomos-node/pull/470
|
||||
- Finished mixnodes in docker testnet: https://github.com/logos-co/nomos-node/pull/467 - The testnet in docker compose is now merged and has a README. There are still room for improvement, like spawning some nodes sequentially (like in https://github.com/logos-co/nomos-node/pull/425), but this will be solved in added in a new PRs or solved by other node improvements.
|
||||
- Improvements for node config: https://github.com/logos-co/nomos-node/pull/460, https://github.com/logos-co/nomos-node/pull/471 - These changes were required for spawning nodes in testnet, will be useful for our endusers too
|
||||
|
||||
## `private PoS:`
|
||||
|
||||
### ::research
|
||||
|
||||
- Single-staking - reviewed and updated the design up to the construction section.
|
||||
- Multi-staking - all comments have been addressed, but new are coming.
|
||||
- Right now we are investigating a scenario where we are limiting the amount of validators in the Single-Staking case by diverging from the requirement of having multiples of validators by removing the economical incentives. In other words, we are considering to allow registering validators that have at least a threshold of stake (that is or is not capped) and a single (unitary) voting power. This way we are limiting the economical need for having multiple validators hosted by a single node, and at the same time limiting the network overhead of the single-staking design.
|
||||
- The "Delegation and Validation Rewards" document (WIP): https://www.notion.so/Delegation-and-Validation-Rewards-d4af3f87a0b240739ff99b15af11cb3f?pvs=4
|
||||
- Incorporating notes in the architecture whitepapers. These readings are not as deeply technical as papers, but more about understanding the directions currently explored at the edge of blockchain architectures (namely rollups, modular architectures and intent-centric architectures).
|
||||
- Working on the problem of PPoS, one of the most critical points of focus right now, to have at least an understanding of the available options
|
||||
|
||||
## nomos::data availability
|
||||
|
||||
### ::research
|
||||
|
||||
- Hyrax, Dory and Dark schemes were studied, comparisons here: https://www.notion.so/Polynomial-Commitment-Schemes-59bf8f6fe39840babe819c5c0a9628fc ; It was concluded that schemes with verifier time above logarithmic are not a good option for data availability.
|
||||
- FRI is a structure that should be used not for now, (at this stage especially, due to large proof size - higher than KZG), but can be used for quantum resistance in the future. Here are some sources that say this can be used in later stages (the reasons are the same as ours). - https://scroll.io/blog/kzg#user-content-fn-6 and https://notes.ethereum.org/@vbuterin/proto_danksharding_faq#Why-use-the-hash-of-the-KZG-instead-of-the-KZG-directly
|
||||
|
||||
### ::development
|
||||
|
||||
|
||||
## nomos::miscellaneous
|
||||
|
||||
- David Rusu has joined - warm welcome to him!
|
||||
|
|
@ -1,3 +1,4 @@
|
|||
---
|
||||
title: "Vac updates"
|
||||
---
|
||||
Here are all files that are tagged with `#vac-updates`
|
||||
|
|
@ -9,7 +9,7 @@ description: "Monthly Report of <project>"
|
|||
|
||||
## Key Updates
|
||||
|
||||
### Personel
|
||||
### Personnel
|
||||
-
|
||||
|
||||
### Milestones
|
||||
|
|
|
|||
Loading…
Reference in New Issue