Overview
This document describes the high-level architecture of the ComputeNet network, including its layers, components, and communication patterns.
Architecture Layers
ComputeNet is organized into distinct layers:
Application Layer
SDKs, APIs, and client libraries that applications use to interact with the network.
Protocol Layer
Job submission, routing, verification, and consensus protocols that coordinate network operations.
Execution Layer
Validator nodes that execute compute jobs and generate proofs within isolated runtime environments.
Network Layer
Peer-to-peer networking, gossip protocols, and data transport between network participants.
Component Diagram
Key components and their relationships:
- Gateway Nodes — Entry points for client requests
- Coordinator Nodes — Manage job distribution and consensus
- Validator Nodes — Execute jobs and generate proofs
- Archive Nodes — Store historical receipts and state
- Relay Nodes — Facilitate cross-region communication
Draft Architecture
The architecture is still being refined. Some components may be consolidated or restructured before mainnet.
Data Flow
A typical job flows through the network as follows:
- Client submits job to a gateway node
- Gateway validates and forwards to coordinator
- Coordinator selects validators and assigns job
- Primary validator executes and generates proof
- Secondary validators verify and attest
- Coordinator aggregates attestations
- Result and receipt returned to client
- Receipt archived for future verification
Fault Tolerance
The network is designed for resilience:
- No single point of failure in the data path
- Automatic failover for validator failures
- Redundant archive storage across regions
- Graceful degradation under partial network partition