Section II
Architecture Overview
Multi-Core World Computer with Heterogeneous Validation
Computation runs in parallel atomicity zones, like cores of a CPU: each keeps its own state, and two validator classes (heavy producers that prove, light validators that only verify) make verification far cheaper than execution.
multi core
Multi-Core World Computer
Each atomicity zone is an independent core with its own state, so throughput grows by adding zones rather than demanding faster hardware from anyone.
validator classes
Two Validator Classes
Producers execute and prove on heavy hardware; validators verify the proof on commodity machines, the asymmetry that lets the network stay decentralized while scaling.
| Property | Block Producer | Block Validator |
|---|---|---|
| Role | Execute transactions + generate ZK proofs | Verify proofs + cast consensus votes |
| Hardware | High-performance: 128GB+ RAM, modern GPU | Commodity: 8GB+ RAM, any modern CPU |
| Operations | VM execution, ZK proof generation, state updates | Proof verification and consensus participation |
data flow
Six-Stage Data Flow
Every transaction moves through six stages, from gossip ingestion to consensus finality, each handled by a dedicated layer.
- Stage 1, Optimum: bandwidth-optimal data spread
- Stage 2, APEX: parallel, conflict-free execution
- Stage 3, Jolt Pro GR: a proof per transaction
- Stage 4, MLE-DB: hash-free state commitment
- Stage 5, HSS-CoFHE: no party sees plaintext
- Stage 6, Consensus: stake-weighted finality
dpos senators
Delegated Proof-of-Stake with Senators
Token holders delegate to stake-weighted senators who finalize each block by two-thirds supermajority, keeping the validator set lean while opening participation to everyone.
security targets
Security Targets
ring0 targets a 128-bit security level across the stack, with the core security claims machine-checked.
128-bit
Composed Soundness
128-bit
Hash Security
No Setup
Trusted Setup
Verified
Formal Proofs
design principles
Three Design Principles
Three principles hold the stack together: one shared algebraic core, verification far cheaper than proving, and a machine-checked proof behind every security claim.
- DP1 Algebraic coherence: one shared foundation across all layers
- DP2 Verification asymmetry: proving costs far more than verifying; validators never re-execute
- DP3 Formal provability: every core security claim is machine-checked