https://roadmap.logos.co/ Recent content in Nomos Technical Roadmap on Hugo -- gohugo.io en-us https://roadmap.logos.co/roadmap/virtual-machines/overview/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/virtual-machines/overview/ Motivation Logos seeks to use a privacy-first virtual machine for transaction execution. We believe this can only be acheived through zero-knowledge. https://roadmap.logos.co/roadmap/networking/carnot-waku-specification/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/networking/carnot-waku-specification/ Definition Reference $k$ - size of a given committee $n_C$ - number of committees in the overlay, or nodes in the tree $d$ - depth of the overlay tree $n_d$ - number of committees at a given depth of the tree Motivation In #Carnot, an overlay is created to facilitate message distribution and voting aggregation. https://roadmap.logos.co/roadmap/consensus/candidates/carnot/overview/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/consensus/candidates/carnot/overview/ Carnot (formerly LogosBFT) is a Byzantine Fault Tolerant (BFT) consensus candidate for the Nomos Network that utilizes Fountain Codes and a committees tree structure to optimize message propagation in the presence of a large number of nodes, while maintaining high througput and fast finality. https://roadmap.logos.co/roadmap/consensus/candidates/claro/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/consensus/candidates/claro/ Claro (formerly Glacier) is a consensus candidate for the Logos network that aims to be an improvement to the Avalanche family of consensus protocols. https://roadmap.logos.co/roadmap/consensus/development/prototypes/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/consensus/development/prototypes/ Consensus Prototypes is a collection of Rust implementations of the Consensus Candidates Tiny Node Required Roles Lead Developer (filled) https://roadmap.logos.co/roadmap/consensus/theory/overview/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/consensus/theory/overview/ This track of work is dedicated to creating theoretical models of distributed consensus in order to evaluate them from a mathematical standpoint. https://roadmap.logos.co/roadmap/consensus/overview/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/consensus/overview/ Consensus is the foundation of the network. It is how a group of peer-to-peer nodes understands how to agree on information in a distributed way, particuluarly in the presence of byzantine actors. https://roadmap.logos.co/roadmap/consensus/development/overview/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/consensus/development/overview/ https://roadmap.logos.co/roadmap/consensus/candidates/carnot/FAQ/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/consensus/candidates/carnot/FAQ/ Network Requirements and Assumptions What assumptions do we need Waku to fulfill? - Corey Moh: Waku needs to fill the following requirements, taken from the Carnot paper: https://roadmap.logos.co/requirements/overview/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/requirements/overview/ This document describes the requirements of the Logos Network. Network sovereignty is an extension of the collective sovereignty of the individuals within. https://roadmap.logos.co/roles/distributed-systems-researcher/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roles/distributed-systems-researcher/ About Status Status is building the tools and infrastructure for the advancement of a secure, private, and open web3. With the high level goals of preserving the right to privacy, mitigating the risk of censorship, and promoting economic trade in a transparent, open manner, Status is building a community where anyone is welcome to join and contribute. https://roadmap.logos.co/roadmap/networking/overview/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/networking/overview/ This page summarizes the work around the P2P networking layer of the Nomos project. Waku Waku is an privacy-preserving, ephemeral, peer-to-peer (P2P) messaging suite of protocols which is developed under Vac and maintained/productionized by the Logos Collective. https://roadmap.logos.co/roles/rust-developer/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roles/rust-developer/ Role: Rust Developer at Status Remote, Worldwide About Status Status is an organization building the tools and infrastructure for the advancement of a secure, private, and open web3. https://roadmap.logos.co/roadmap/networking/status-network-agents/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/networking/status-network-agents/ This page creates a model to describe the impact of the various clients within the Status ecosystem by describing their individual contribution to the messages within the Waku network they leverage. https://roadmap.logos.co/roadmap/networking/status-waku-kurtosis/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/networking/status-waku-kurtosis/ Status is the largest consumer of the Waku protocol, leveraging it for their entire networking stack. THeir upcoming release of Status Desktop and the associated Communities product will heavily push the limits of what Waku can do. https://roadmap.logos.co/roadmap/consensus/theory/snow-family/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roadmap/consensus/theory/snow-family/ In order to evaluate the properties of the Avalanche family of consensus protocols more rigorously than the original whitepapers, we work to create an analytical framework to explore and better understand the theoretical boundaries of the underlying protocols, and under what parameterization they will break vs a set of adversarial strategies https://roadmap.logos.co/roles/zero-knowledge-research-engineer/ Mon, 01 Jan 0001 00:00:00 +0000 https://roadmap.logos.co/roles/zero-knowledge-research-engineer/ at Status Remote, Worldwide About Status Status is building the tools and infrastructure for the advancement of a secure, private, and open web3.