mirror of https://github.com/logos-co/roadmap.git
174 lines
9.4 KiB
XML
174 lines
9.4 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
|
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
|
<channel>
|
|
<title>Nomos Technical Roadmap on </title>
|
|
<link>https://roadmap.logos.co/</link>
|
|
<description>Recent content in Nomos Technical Roadmap on </description>
|
|
<generator>Hugo -- gohugo.io</generator>
|
|
<language>en-us</language><atom:link href="https://roadmap.logos.co/index.xml" rel="self" type="application/rss+xml" />
|
|
<item>
|
|
<title></title>
|
|
<link>https://roadmap.logos.co/roadmap/virtual-machines/overview/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/virtual-machines/overview/</guid>
|
|
<description>Motivation Logos seeks to use a privacy-first virtual machine for transaction execution. We beleive this can only be acheived through zero-knowledge.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>A Specification proposal for using Waku for Carnot Consensus</title>
|
|
<link>https://roadmap.logos.co/roadmap/networking/carnot-waku-specification/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/networking/carnot-waku-specification/</guid>
|
|
<description>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.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Carnot Overview</title>
|
|
<link>https://roadmap.logos.co/roadmap/consensus/candidates/carnot/overview/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/consensus/candidates/carnot/overview/</guid>
|
|
<description>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.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Claro: Consensus Candidate</title>
|
|
<link>https://roadmap.logos.co/roadmap/consensus/candidates/claro/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/consensus/candidates/claro/</guid>
|
|
<description>Claro (formerly Glacier) is a consensus candidate for the Logos network that aims to be an improvement to the Avalanche family of consensus protocols.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Consensus Prototypes</title>
|
|
<link>https://roadmap.logos.co/roadmap/consensus/development/prototypes/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/consensus/development/prototypes/</guid>
|
|
<description>Consensus Prototypes is a collection of Rust implementations of the Consensus Candidates
|
|
Tiny Node Required Roles Lead Developer (filled) </description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Consensus Theory Work</title>
|
|
<link>https://roadmap.logos.co/roadmap/consensus/theory/overview/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/consensus/theory/overview/</guid>
|
|
<description>This track of work is dedicated to creating theoretical models of distributed consensus in order to evaluate them from a mathematical standpoint.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Consensus Work</title>
|
|
<link>https://roadmap.logos.co/roadmap/consensus/overview/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/consensus/overview/</guid>
|
|
<description>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.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Development Work</title>
|
|
<link>https://roadmap.logos.co/roadmap/consensus/development/overview/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/consensus/development/overview/</guid>
|
|
<description></description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Frequently Asked Questions</title>
|
|
<link>https://roadmap.logos.co/roadmap/consensus/candidates/carnot/FAQ/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/consensus/candidates/carnot/FAQ/</guid>
|
|
<description>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:</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Logos Network Requirements Overview</title>
|
|
<link>https://roadmap.logos.co/requirements/overview/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/requirements/overview/</guid>
|
|
<description>This document describes the requirements of the Logos Network.
|
|
Network sovereignty is an extension of the collective sovereignty of the individuals within.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Open Role: Distributed Systems Researcher</title>
|
|
<link>https://roadmap.logos.co/roles/distributed-systems-researcher/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roles/distributed-systems-researcher/</guid>
|
|
<description>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.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>P2P Networking Overview</title>
|
|
<link>https://roadmap.logos.co/roadmap/networking/overview/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/networking/overview/</guid>
|
|
<description>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.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Rust Developer</title>
|
|
<link>https://roadmap.logos.co/roles/rust-developer/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roles/rust-developer/</guid>
|
|
<description>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.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Status Network Agents Breakdown</title>
|
|
<link>https://roadmap.logos.co/roadmap/networking/status-network-agents/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/networking/status-network-agents/</guid>
|
|
<description>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.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Status' use of Waku - A Scalability Study</title>
|
|
<link>https://roadmap.logos.co/roadmap/networking/status-waku-kurtosis/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/networking/status-waku-kurtosis/</guid>
|
|
<description>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.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Theoretical Analysis of the Snow Family of Consensus Protocols</title>
|
|
<link>https://roadmap.logos.co/roadmap/consensus/theory/snow-family/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roadmap/consensus/theory/snow-family/</guid>
|
|
<description>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</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Zero Knowledge Research Engineer</title>
|
|
<link>https://roadmap.logos.co/roles/zero-knowledge-research-engineer/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
<guid>https://roadmap.logos.co/roles/zero-knowledge-research-engineer/</guid>
|
|
<description>at Status
|
|
Remote, Worldwide
|
|
About Status
|
|
Status is building the tools and infrastructure for the advancement of a secure, private, and open web3.</description>
|
|
</item>
|
|
|
|
</channel>
|
|
</rss>
|