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

updates

This commit is contained in:
Corey 2022-06-10 08:31:58 -04:00
parent 798361e138
commit eec9327993
3 changed files with 50 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
technology/blockchain.md
View File

@ -1,8 +1,8 @@
---
title: The Logos Blockchain
title: The Logos Blockchain Network
---
# The Logos Blockchain
The Logos Blockchain is a heterogeneous blockchain network, specifically designed to enable communities to have digital infrastructure that is not only appropriate for them, but also owned by them.
# The Logos Blockchain Network
The Logos Blockchain Network is a heterogeneous blockchain network, specifically designed to enable communities to have digital infrastructure that is not only appropriate for them, but also owned by them.
This endeavor is currently under a heavy research phase as we explore the current best practices and possibilities that are under development or available across the industry.
@ -12,7 +12,7 @@ We find it useful to define a list of use cases that the technology should fulfi
### Use cases
The main use case of the blockchain infrastructure is to provide support for bootstrapping and maintaining **Common Interest Communities (CIC)**. CICs have the following key characteristics:
The main use case of the blockchain network infrastructure is to provide support for bootstrapping and maintaining **Common Interest Communities (CIC)**. CICs have the following key characteristics:
- We expect the range of network sizes to be wide. We can expect some CICs to be in the scale ~10 nodes, while others could (potentially) scale up to current blockchain limits.
- CICs will have varying degrees of inter-communication. Some will be existing in relative isolation (ie. no communication), while others could be very interdependent.
@ -45,4 +45,4 @@ In order to fulfill these use cases, we now define a set of requirements the blo
As we harden our confidence around the various protocols that will come together to meet these requirements, we will update this site. Please check back regularly to learn more about how this network will be built.
Our intention is to be as rigorous and open as possible. You can read about [our development methodology](./overview) to learn how we plan to make good on those intentions.
Our intention is to be as rigorous and open as possible. You can read about [our development methodology](./process) to learn how we plan to make good on those intentions.

42
technology/overview.md
View File

@ -6,43 +6,6 @@ This requires a re-imagining of the public internet infrastructure upon which we
Individually, they are designed to be easily incorporated into other established systems. Together, they form the foundational public infrastructure required for the next generation of social institutions to emerge.
### Our Process
We build public good protocols for everyone, then implement them the way that works for us
Public goods are for the people, and thus should be owned and controlled by them. How they are built influences this outcome. To this end, we have come up with a process that helps to ensure that the products of our effort are not solely controlled by us and our potentially limited self-interests and opinions.
In a nutshell, Logos projects will work hand-in-hand with our sister research organization, Vac, to create agnostic protocols for everyone to share and contribute to. You can read more about Vac and their mission [here](https://vac.dev).
The general flow of how a given project within Logos collaborates with Vac is summarized in the following diagram.
```mermaid
flowchart
O1[Unopinionated Protocols]
subgraph A Logos Project
L1[Engineering]-->|Delivers|L2[Opinionated Products]
L3[Research]-->|Delivers|L4[PoC Implementation]
end
subgraph Vac Research
V1[Principles]-->|Aligns|V2[Agnostic Specifications]
V3[Protocol Development Process]-->|Structures|V2
click V3 "https://rfc.vac.dev" "Specifications"
click V1 "https://status.im/about/" "Principles"
end
L3-->|Delivers|V2
V2-->|Informs|L1
V2-->|Allow for|O1
```
A Logos project will perform research on a problem. Their initial deliverables will be a Proof of Concept (PoC) and a set of specifications that detail explicitely how that solution is built. Vac will provide resources to the Logos project by facilitating in the process writing and hardening the specifications being developed.
In addition to helping in the process of spec writing, they also serve as an embodiment of the foundational principles that maintain the ethical development of public good infrastructure. This means that specifications written, developed, and housed with Vac are not tied to any given chain, biased ideology, and the subsequent control that comes from it. These specifications can then be used by the general public in any way they see fit, free and open source.
The Logos project will then pull back an opinionated view of these specifications to implement their vision of how the product should be built for their particular use case.
This process is our commitment to build in the open and work to maintain an ethos of building for the public good while also allowing ourselves to create opinionated products that suit our specific needs.
**Waku** - *The ephemeral communication layer.*
Waku is a peer-to-peer communication layer.
@ -73,12 +36,15 @@ Codex has a working PoC, as is expected to be in production by 2023.
Logos Blockchain is a heterogeneous blockchain network.
The third component of the Logos’ stack is a blockchain network that aims to provide fast, scalable and secure smart contracts, with near-instant transaction finality. We’re developing a leaderless consensus algorithm, which is currently under active research. Our current repos and tests are set to private until the research begins to mature slightly, but are available on request.
The third component of the Logos’ stack is a blockchain network that aims to provide fast, scalable and secure smart contracts, with near-instant transaction finality.
This network is built on top of what we call an "agreements layer" that is powered by a distributed, leaderless consensus algorithm which is currently under active research. Our current repos and tests are set to private until the research begins to mature slightly, but are available on request.
The first two client implementations will be written in Nim and Rust. The same team developing [Nimbus](https://nimbus.team/) one of the leading Ethereum Consensus Clients, will expand its resources to take on the Nim implementation once the first specification has been published.
[Read more]("/technology/blockchain")
---
Logos is not yet in production across every protocol in its stack. A number of research and engineering problems remain. We have no disillusions to the magnitude of the undertaking, and the work still ahead of us. We invite anyone who is serious about contributing research or to its code-base to join the community and get involved.

41
technology/process.md Normal file
View File

@ -0,0 +1,41 @@
# Our Process
We build public good protocols for everyone, then implement them the way that works for us
Public goods are for the people, and thus should be owned and controlled by them. How they are built influences this outcome. To this end, we have come up with a process that helps to ensure that the products of our effort are not solely controlled by us and our potentially limited self-interests and opinions.
In a nutshell, Logos projects will work hand-in-hand with our sister research organization, Vac, to create agnostic protocols for everyone to share and contribute to. You can read more about Vac and their mission [here](https://vac.dev).
The general flow of how a given project within Logos collaborates with Vac is summarized in the following diagram.
```mermaid
flowchart
O1[Unopinionated Protocols]
O2[Users]
subgraph Project
L1[Engineering]-->|Delivers|L2[Opinionated Products]
L3[Research]-->|Delivers|L4[PoC Implementation]
end
subgraph Vac
V1[Principles]-->|Aligns|V2[Agnostic Specifications]
V3[Protocol Development Process]-->|Structures|V2
click V3 "https://rfc.vac.dev" "Specifications"
click V1 "https://status.im/about/" "Principles"
end
L3-->|Delivers|V2
V2-->|Informs|L1
V2-->|Allow for|O1
L2-->|Serves|O2
O2-->|Provides user feedback to|L1
L1-->|Updates|V2
```
A Logos project will perform research on a problem. Their initial deliverables will be a Proof of Concept (PoC) and a set of specifications that detail explicitely how that solution is built. Vac will provide resources to the Logos project by facilitating in the process writing and hardening the specifications being developed.
In addition to helping in the process of spec writing, they also serve as an embodiment of the foundational principles that maintain the ethical development of public good infrastructure. This means that specifications written, developed, and housed with Vac are not tied to any given chain, biased ideology, and the subsequent control that comes from it. These specifications can then be used by the general public in any way they see fit, free and open source.
The Logos project will then pull back an opinionated view of these specifications to implement their vision of how the product should be built for their particular use case.
This process is our commitment to build in the open and work to maintain an ethos of building for the public good while also allowing ourselves to create opinionated products that suit our specific needs.