update content
This commit is contained in:
parent
2709430cf5
commit
c8aab03b7d
|
@ -3,7 +3,7 @@ title: Description and architecture
|
|||
sidebar_position: 2
|
||||
---
|
||||
|
||||
Nomos was designed to serve as the infrastructure for emerging network states. We believe that such a network must maintain the following properties:
|
||||
Nomos was designed to serve as the infrastructure for emerging network states, providing a key piece of infrastructure to the Logos tech stack. We believe that such a network must maintain the following properties:
|
||||
|
||||
- **Maximum decentralization:** Nomos is designed to place minimum resource demands on validators, ensuring that those without access to powerful hardware can participate. With the network maximally accessible, greater numbers of users can join as full peers, strengthening Nomos from a security perspective.
|
||||
|
||||
|
@ -13,6 +13,8 @@ Nomos was designed to serve as the infrastructure for emerging network states. W
|
|||
|
||||
- **Privacy-centric:** We believe privacy to be essential for the self-determination and sovereignty of aspiring network states. Consequently, Nomos has been designed to protect user privacy at the network level and in such a way as to enable the integration of new privacy techniques as they become available.
|
||||
|
||||
### Design space
|
||||
|
||||
To achieve the above, Nomos develops an underexplored area in the design space between Ethereum, Cosmos, Polkadot and newer systems like Celestia and Anoma.
|
||||
|
||||
Ethereum pioneered the concept of a blockchain network capable of smart contract execution ushering in an ongoing era of monetary and organizational experimentation. Yet, it is vulnerable to various centralizing forces. Furthermore, while its rollup-centric approach to scaling has the potential for decentralization, most rollups today rely on centralized sequencers and inter-rollup communication presents its own complications. Inspirational to Nomos in many ways, these shortcomings make Ethereum ill-suited for our vision of a network of network states.
|
||||
|
@ -37,7 +39,7 @@ The Carnot consensus protocol is crucial to ensuring high performance as the net
|
|||
|
||||
Alongside ensuring maximum decentralization, the Base Layer also strives to make data availability scalable. It achieves this by:
|
||||
|
||||
- Reducing the amount of computation validators need to do by minimizing or eliminating block execution or verification on the Base Layer.
|
||||
- Reducing the amount of computation validators need to do by minimizing or eliminating block execution or verification from the Base Layer.
|
||||
|
||||
- Reducing the amount of data light clients need to download through Data Availability Sampling.
|
||||
|
||||
|
@ -59,8 +61,6 @@ The Coordination Layer provides the following functions only:
|
|||
|
||||
- **Censorship resistance:** Censorship resistance is an emergent property of the above features, enabling any user to "exit" an execution zone by submitting transactions to the Coordination Layer directly. This is particularly powerful in the event that an Execution Zone attempts to censor a user's actions.
|
||||
|
||||
Coordination Layer directly. This is particularly powerful in the event that an Execution Zone attempts to censor a user's actions.
|
||||
|
||||
<br />
|
||||
|
||||
**Execution Zones**
|
||||
|
@ -85,8 +85,8 @@ This architecture makes Execution Zones more powerful than traditional sidechain
|
|||
|
||||
- Share liquidity across the network.
|
||||
|
||||
- Enable improved security via staking.
|
||||
- Enable improved security via restaking.
|
||||
|
||||
Execution Zones exist to satisfy a wide range of application requirements that may demand far greater performance characteristics than what a highly decentralized, monolithic blockchain can achieve before hitting scaling limits. Such applications are often willing to make compromises in terms of security or decentralization to achieve such performance. By combining the elastic consensus algorithm Carnot with a staking mechanism and flexible execution models, Nomos grants a high degree of Execution Zone adaptability.
|
||||
Execution Zones exist to satisfy a wide range of application requirements that may demand far greater performance characteristics than what a highly decentralized, monolithic blockchain can achieve before hitting scaling limits. Such applications are often willing to make compromises in terms of security or decentralization to achieve higher performance. By combining the elastic consensus algorithm Carnot with a restaking mechanism and flexible execution models, Nomos grants a high degree of Execution Zone adaptability.
|
||||
|
||||
![architect.png](/subpages/architect.png)
|
||||
|
|
|
@ -5,11 +5,13 @@ sidebar_position: 1
|
|||
|
||||
Nomos is an innovative blockchain platform designed to address the critical requirements of the network state. It aims to provide developers with secure, flexible and scalable infrastructure for building a wide range of applications while respecting the privacy and sovereignty of its users.
|
||||
|
||||
We believe that blockchain technology has the potential to lay the foundations of a fairer, less corruptible and, ultimately, freer world. However, its most successful implementations to date fall way short of achieving this.
|
||||
Nomos serves as the computational branch of the [Logos](https://logos.co/) tech stack. Alongside the communications branch, [Waku](https://waku.org/), and the storage branch, [Codex](https://codex.storage/), it is one of the Logos Collective's foundational projects.
|
||||
|
||||
We believe that blockchain technology has the potential to lay the foundations of a fairer, less corruptible and, ultimately, freer society. However, its most successful implementations to date fall way short of achieving this.
|
||||
|
||||
<br/>
|
||||
|
||||
### Network-level privacy, network-level sovereignty
|
||||
## Network-level privacy, network-level sovereignty
|
||||
|
||||
Bitcoin and Ethereum emerged from the cypherpunk tradition. As Eric Hughes wrote in his seminal 1993 essay, "A Cypherpunk's Manifesto":
|
||||
|
||||
|
@ -19,15 +21,18 @@ Yet, neither network protects the right to privacy by default. Without network-l
|
|||
|
||||
We believe that such absolute transparency massively limits the scope of the technology's adoption and, therefore, its revolutionary potential. We cannot expect individuals to voluntarily exit the current system into one in which their every interaction with all financial and social institutions is forever available for the entire world to see. When we buy a coffee, for example, there is no absolutely no need for the seller to see our salary, other purchase history or political leanings.
|
||||
|
||||
### Consent of the governed
|
||||
|
||||
Furthermore, we believe consent to be a critical element of any governance system. We find the nation-state's claims of governance via implied consent to be extremely contrived and believe blockchain-based systems represent an improvement because every on-chain action is voluntary and requires an individual to digitally sign, therefore, providing explicit consent.
|
||||
|
||||
While this is certainly a step in the right direction, it does not go far enough. If an individual no longer aligns with the on-chain institutions of which they were once apart, today's blockchains offer a means of exiting the system to recreate something new. However, the cost to do so successfully can be prohibitively expensive.
|
||||
|
||||
There have been numerous occasions in history where an on-chain community has been divided on some issue, resulting in a hard fork that creates two independent chains. In such situations, both networks suffer in terms of their overall security, making them more vulnerable to external attacks.
|
||||
Nomos leverages a novel architecture to avoid this situation. We believe that a simple disagreement over a community's path forward should not threaten the existence of either party. The Nomos network enables the creation of numerous semi-autonomous execution zones that share the main network's security while retaining the freedom to create their own rulesets and, eventually, become fully independent if they so choose.
|
||||
|
||||
Nomos leverages a novel architecture to avoid this situation. We believe that a simple disagreement over a community's path forward should not threaten the existence of either party. The Nomos network enables the creation of numerous semi-autonomous execution zones that share the main network's security while retaining the freedom to follow their own rulesets and, eventually, become fully independent if they so choose.
|
||||
|
||||
<br/>
|
||||
|
||||
### History
|
||||
|
||||
Work on Nomos began among a small subgroup of Status core contributors in 2022. The network takes its name from the ancient Greek concept of law
|
||||
Work on Nomos began among a small subgroup of Status core contributors in 2022. The network takes its name from the ancient Greek concept of law and follows the naming convention established by Logos. Nomos was first announced as a core Logos project in June 2023.
|
|
@ -6,3 +6,4 @@ sidebar_position: 4
|
|||
At this early stage of Nomos' development, the team is primarily focused on implementing the network's consensus protocol, Carnot. As the consensus protocol is so foundational to the rest of the project, it must precede other development areas. Alongside Carnot, Nomos' contributors are working on defining the network architecture, which will also influence future roadmap items.
|
||||
|
||||
After defining the network architecture and implementing the consensus protocol, we can establish further milestones both above and below the consensus protocol. Above the consensus layer will be the network's data model and execution environments, which will enable advanced functionality. Below will be P2P networking and peer discovery, which must be built or integrated while maintaining privacy and performance.
|
||||
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Team structure
|
||||
title: Core contributors
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
|
|
|
@ -114,7 +114,7 @@ const config = {
|
|||
},
|
||||
{
|
||||
href: '/',
|
||||
label: 'Temrs & conditions',
|
||||
label: 'Terms & conditions',
|
||||
},
|
||||
],
|
||||
},
|
||||
|
|
Binary file not shown.
Before Width: | Height: | Size: 70 KiB After Width: | Height: | Size: 65 KiB |
Loading…
Reference in New Issue