HomeArchitecture

System Architecture

ComputeNet is built on a modular architecture where each component can evolve independently while preserving protocol interoperability.

High-Level Architecture

The protocol consists of validator nodes, deterministic compute runners, proof engines, receipt engines, consensus coordinators, and telemetry systems.

Compute Input
Execution
Verification
Consensus
Layer 1

Deterministic Execution

Layer 2

Receipt Generation

Layer 3

Validator Consensus

Core Components

Validator Nodes

Validators receive compute receipts, verify deterministic outputs, attest validity, and participate in consensus.

  • Receipt validation
  • Output verification
  • Validity attestation
  • Consensus participation
  • FastAPI-based services

Deterministic Runner

The execution layer ensures workloads produce reproducible outputs with stable execution and predictable results.

  • Stable execution
  • Predictable outputs
  • Reproducible hashing
  • Deterministic receipts
  • Workload isolation

Receipt Engine

Execution results are transformed into structured receipts containing job metadata and proof payloads.

  • Job identifiers
  • Manifest hashes
  • Execution hashes
  • Validator metadata
  • Timestamps & proofs

Proof Engine

Verifies compute validity through local deterministic proofs and placeholder ZK integration layers.

  • Local proofs
  • ZK placeholders
  • Aggregate structures
  • Future zkVM
  • Hardware attestation

Consensus Layer

Validators independently verify receipts, cast weighted attestations, and finalize accepted compute.

  • Independent verification
  • Weighted attestations
  • Consensus ratios
  • Finalization
  • Future BFT research

Telemetry Systems

Protocol telemetry for validator uptime, peer liveness, receipt activity, and consensus reports.

  • Validator uptime
  • Peer liveness
  • Receipt activity
  • Consensus reports
  • Runtime metrics

Peer Registry

Validators maintain peer registries with bootstrap lists, gossip sync, and liveness scoring.

  • Bootstrap peers
  • Gossip synchronization
  • Liveness scoring
  • Trust weighting
  • Discovery protocols

Public Observer

Public-facing infrastructure providing readable telemetry and bootstrap peer visibility.

  • Public telemetry
  • Peer visibility
  • Genesis candidates
  • Explorer access
  • Read-only mode
Verification Flow

Verification Pipeline

The protocol approaches verification through a layered pipeline where verification is designed to be cheaper than execution.

Job Manifest

Deterministic execution blueprint

1

Execution

Reproducible workload processing

2

Hashing

Immutable output fingerprint

3

Receipt

Portable evidence artifact

4

Validation

Independent re-execution

5

Consensus

Distributed agreement

6

Data Flow Architecture

The protocol processes compute through a structured flow: manifests define workloads, runners execute deterministically, receipts capture evidence, and validators reach consensus.

1

Input Layer

Job manifests define deterministic workloads

2

Execution Layer

Reproducible compute with stable outputs

3

Evidence Layer

Receipts capture execution proof

4

Consensus Layer

Validators attest and finalize

>// Compute flow visualization
manifest.json
deterministic_runner
execution_hash
compute_receipt
validators[]
verify(receipt)attest()
consensus_ratio:1.00
Future Research

Long-Term Architecture Goals

The architecture is designed to evolve. Future research directions may include zkVM integrations, recursive proof systems, hardware attestation, and trusted execution environments.

View Research

zkVM Integration

Research

Recursive Proofs

Planned

Hardware Attestation

Exploration

Async BFT

Research