Jump to content
Toggle sidebar
Logos
Search
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information
Editing
Nomos/Requirements
(section)
Page
Discussion
English
Read
Edit
View history
More
Read
Edit
View history
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== 4.1 Base Layer === <span id="private-proof-of-stake"></span> ==== 4.1.1 Private Proof of Stake ==== Description: The Base Layer MUST implement a Private Proof of Stake consensus mechanism that preserves validator privacy and prevents targeted attacks. Functional Requirements: PPOS-001: Validator Privacy * The system MUST implement basic privacy: ** Hide validator stakes through Blend Network ** Preserve block proposer anonymity ** Prevent stake deanonymization attacks ** Maintain validator metadata privacy * The system SHOULD support enhanced privacy: ** Advanced timing analysis protection ** Enhanced anonymity set generation ** Improved network attack resistance PPOS-002: Consensus Security * The system MUST provide basic security: ** Prevent stake grinding attacks ** Ensure fair block production ** Maintain consensus finality ** Handle network partitions * The system SHOULD implement advanced security: ** Quantum attack resistance ** Eclipse attack prevention ** Advanced fork choice rules ** Complex partition handling PPOS-003: Network Resilience * The system MUST ensure basic resilience: ** Support commodity hardware validators ** Handle intermittent connectivity ** Recover from network failures ** Maintain liveness under attack * The system SHOULD provide enhanced resilience: ** Advanced recovery mechanisms ** Dynamic attack mitigation ** Adaptive network topology ** Self-healing capabilities <span id="data-availability"></span> ==== 4.1.2 Data Availability ==== Description: The Base Layer MUST provide scalable data availability with light client verification capabilities. Functional Requirements: DAS-001: Data Sampling and Verification * The system MUST implement basic sampling: ** Efficient data availability sampling ** Light client verification support ** Sample size optimization ** Verification latency targets * The system SHOULD support advanced sampling: ** Adaptive sample sizes ** Enhanced verification methods ** Optimized proof generation ** Advanced fraud proofs DAS-002: Data Organization * The system MUST implement basic sharding: ** Data segmentation and distribution ** Cross-shard verification ** Shard synchronization ** Data redundancy management * The system SHOULD support advanced sharding: ** Dynamic shard allocation ** Cross-shard optimization ** Adaptive redundancy ** Load balancing DAS-003: Data Integrity and Recovery * The system MUST ensure basic integrity: ** Data reconstruction capabilities ** Integrity verification ** Error detection and correction ** Bandwidth optimization * The system SHOULD implement advanced features: ** Advanced reconstruction methods ** Enhanced error correction ** Optimized bandwidth usage ** Proactive integrity checks <span id="network-and-consensus-privacy"></span> ==== 4.1.3 Network and Consensus Privacy ==== Description: The Base Layer MUST implement two complementary privacy systems: * Required for MVP: ** Nomos Blend Network: A specialized privacy system for Private Proof of Stake with three modules: *** PTM (Persistent Transmission Module): Manages validator connections and drop messages *** MBM (Message Blending Module): Processes consensus messages through mixing and timing obfuscation *** CTM (Cover Traffic Module): Generates anonymity sets through cover messages ** libp2p-mix: A P2P networking module for general network privacy * Future Enhancements: ** Advanced timing analysis protection ** Enhanced anonymity set generation ** Improved network attack resistance Functional Requirements: BNP-001: Persistent Transmission Module * The system MUST maintain persistent validator connections with basic privacy: ** Establish and maintain secure validator connections ** Handle drop messages for connection privacy ** Monitor connection quality and health ** Manage connection lifecycles securely * The system SHOULD implement advanced connection features: ** Dynamic connection management based on network conditions ** Enhanced privacy through adaptive drop message rates ** Advanced connection health monitoring and recovery ** Optimized connection resource management BNP-002: Message Blending Module * The system MUST process and blend consensus messages: ** Process consensus messages through mixing ** Implement basic timing analysis protection ** Integrate fully with Cryptarchia protocol ** Maintain message timing obfuscation * The system SHOULD enhance message privacy: ** Advanced timing analysis protection mechanisms ** Enhanced message mixing algorithms ** Complex timing pattern obfuscation ** Optimized message processing and blending BNP-003: Cover Traffic Module * The system MUST generate minimum required cover traffic: ** Generate and maintain cover message streams ** Create sufficient anonymity sets ** Optimize resource usage for cover traffic ** Balance privacy and bandwidth usage * The system SHOULD implement advanced cover traffic: ** Dynamic cover traffic generation based on network activity ** Enhanced anonymity set management ** Advanced traffic pattern obfuscation ** Efficient resource utilization strategies BNP-004: Network Privacy Integration * The system MUST provide network-level privacy: ** Network-level privacy for non-consensus messages ** Basic private P2P communication capabilities ** Private data dissemination mechanisms ** Basic traffic analysis protection * The system SHOULD enhance network privacy: ** Advanced traffic analysis protection ** Optimized cover traffic generation ** Larger anonymity set maintenance ** Improved network attack resistance <span id="coordination-layer"></span>
Summary:
Please note that all contributions to Logos may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Logos:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)