Public verificationLive

A dedicated verification layer
for computation

Compute anywhere. Verify through ComputeNet. The live service runs bounded document hashing and exact integer aggregation with signed receipts. Broader AI, software and scientific verification remains a research and integration objective.

Explore VerificationOpen Compute Verification CentreDocumentation

A new computational trust infrastructure — not a blockchain or cryptocurrency.

Open SourceJoin ComputeNet — Operator Qualification

Public verification is live. Native consensus, mining, issuance and COMPUTE payments/rewards are inactive. Independent operation is not yet demonstrated.

Network illustration — not measured validator locations

Scroll to explore

Computational trust infrastructure

A new trust layer for computation

ComputeNet separates execution from trust. Computation can happen anywhere. ComputeNet provides an independent layer for establishing what ran, how it ran, and what evidence supports the result.

Today

Result only
Application / AI / Cloud
Computation
Result

The recipient generally has to trust the system that produced the result.

With ComputeNet

Evidence included
Application / AI / Cloud
Computation
ComputeNet Verification
Evidence
Verifiable Result

Category clarity

What ComputeNet is — and isn't

ComputeNet is

  • A computational-verification ecosystem
  • A trust layer for computation
  • Infrastructure for proof-carrying computational results
  • A network designed for independent verification
  • Applicable to AI, cloud, software, and scientific computing
  • Designed to verify computation performed anywhere

ComputeNet isn't

  • A cryptocurrency
  • A blockchain
  • A speculative token network
  • A crypto-mining system
  • Another decentralised cloud provider
  • Limited to workloads executed on ComputeNet

One ecosystem, many utilities

ComputeNet is bigger than one application

ComputeNet is being built as a broad computational-verification ecosystem and protocol. CVC is its first utility; the surrounding architecture is being developed deliberately and honestly.

ComputeNet
Computational-verification ecosystem and protocol
LIVE

CVC — Compute Verification Centre

The first utility built on ComputeNet. Customer-facing verification centre and developer gateway.

IN DEVELOPMENT

Universal Verification Compiler

Canonical workload identity and reproducible package tooling; not a universal correctness compiler.

PLANNED

Adaptive Verification

Determines appropriate verification strategies according to workload characteristics and assurance requirements.

PLANNED

Verification Network

Off-mainnet qualification; independent administration not demonstrated.

ALPHA

Compute Receipts / Compute Passports

Portable evidence describing computational execution and verification.

PLANNED

Verification Exchange

Intended marketplace for computational assurance.

IN DEVELOPMENT

Reality Forge

Adversarial verification research and protocol improvement.

Network of networks

Compute anywhere.
Verify through ComputeNet.

ComputeNet does not require organisations to move their computation onto a new cloud. It is designed to sit across existing infrastructure as an independent verification layer.

Local machine
AWS / cloud
Enterprise infrastructure
AI inference
GPU infrastructure
Scientific computing
Independent compute network
ComputeNetALPHA
Verification evidenceCompute receiptCompute passport (future)

For builders

Your infrastructure doesn't need to change.

The long-term goal is to let developers integrate verification without becoming cryptographers or replacing the compute infrastructure they already use.

Target developer experience — not yet publicly available
target developer experiencePLANNED
computenet compile ./workload
computenet verify ./workload
computenet inspect <receipt-or-passport>
First utility · LIVE

Compute Verification Centre

ComputeNet is the ecosystem. CVC is its first verification utility — a customer and developer interface for computational verification.

Open CVC
A portable trust layer

The internet made information universally transportable. Cloud computing made computation universally accessible. ComputeNet is being built to make computational trust portable.

…

Historical block height

Chain computenet-mainnet-1

…

Historical COMPUTE issuance

of 21,000,000 max

21,000,000

Max Supply

Fixed COMPUTE cap

…

API-reported node reachability

Configured nodes; not independent validators

Loading historical API observations…

Known host observations

Configured Seed/Gamma hosts; not independent operators

Read API unavailable

Configured hosts only; online status not measured. Last update: Never

Network Status

Connecting to network…

Loading…
chain_id:computenet-mainnet-1
coin:COMPUTE
block_height:—
mined_supply:—
max_supply:21,000,000
legacy_api_validity_report:—
head_hash:—
reported_reachable_nodes:Not measured

What is ComputeNet?

ComputeNet is an experimental verification ecosystem designed to make computational results independently checkable. Computation can remain on existing infrastructure while ComputeNet develops the evidence, policies, and network capacity needed to establish what ran and how it was verified.

Useful Computation

Computational work should produce reusable value, not just difficulty competition.

Verifiable Execution

Users can reproduce the supported deterministic results; independent network operators remain unqualified.

Independent Corroboration

Trust emerges from independently reproduced evidence, not a single authority.

Why Useful Compute Matters

Modern compute markets suffer from structural problems. At the same time, existing proof-of-work systems consume energy while producing computational outputs with little reusable utility. ComputeNet explores an alternative: computational work should produce reusable value.

Centralized cloud dependency
Opaque compute pricing
Unverifiable execution
Fragmented idle compute
Weak trust guarantees
Poor interoperability

The Core Thesis

Useful computation can become a native protocol primitive.

Instead of hashing purely for difficulty competition, nodes compete by executing deterministic workloads, generating verifiable outputs, producing cryptographic execution receipts, and participating in decentralized validation.

Protocol Foundation

Proof of Useful Compute (PoUC)

In PoUC, computational work must produce reusable outputs that are independently verifiable. Verification participants must be able to reproduce execution, and receipts must carry corroborated evidence. Useful computation is mandatory in the unactivated native compound proposal, alongside fresh complementary resource work. This page does not claim active mining, block production or issuance.

Determinism

Inputs produce reproducible outputs

Verifiability

Separate processes replay supported jobs

Replay Resistance

Receipts resist duplication

Fraud Detection

Invalid signatures and mismatched outputs rejected

Cost Efficiency

Verification cheaper than generation

Utility Production

Network generates reusable value

Verification Pipeline

The protocol approaches verification through a layered pipeline combining deterministic execution, reproducible workloads, execution hashing, portable compute receipts, validator re-execution, and corroborated evidence.

Job Manifest

Deterministic execution blueprint

1

Deterministic Execution

Reproducible workload processing

2

Execution Hashing

Immutable output fingerprint

3

Receipt Construction

Portable evidence artifact

4

Validator Re-execution

Separate-process replay

5

Evidence Corroboration

Policy-bound signature agreement

6
evidence_review:illustrative
verification-participant-A
reproduced
verification-participant-B
reproduced
verification-participant-C
reproduced
Example corroboration view — not a live validator count or confidence score.

Independent Verification Participants

The proposed network has independent verification participants. Current processes share one administration. They verify receipts, provide attestations, and corroborate execution evidence. No single participant is treated as authoritative — trust emerges from independent reproducibility.

Verification without blockchain consensus

ComputeNet does not require a blockchain or native cryptocurrency to provide computational verification. Validators are verification participants, not cryptocurrency miners.

  • Receipt validation
  • Consensus participation
  • Peer propagation
  • Fraud detection
Learn about validators
Verification-First Principles

Open Protocol Principles

ComputeNet prioritizes open-source infrastructure, transparent verification rules, and participation over exclusivity. The protocol is research-first and utility-oriented: it does not require a native cryptocurrency or token sale to establish computational trust.

No Token Dependency

Computational verification does not require a native cryptocurrency

No Speculative Launch

No token sale or fundraising mechanism is part of this concept

No Central Custody

Verification evidence is not held by a single custodian

Open Participation

Verification participation follows published rules

Utility-First

Prioritize useful compute over speculation

Research-First

Experimentation over marketing

Public verification live

Current Development Status

Public bounded computation and signed verification receipts are live. Historical mining remains stopped. Native consensus and COMPUTE payments are not active; independent operation has not been demonstrated.

Protocol experimentation
Validator architecture testing
Compute receipt verification
Consensus validation
Distributed systems research
Native consensus services
Inactive
Compute Receipt Generation
Operational
Historical API observation
Read-only
Future Directions

Long-Term Vision

The long-term objective of ComputeNet is a decentralized protocol for verifiable useful compute. The protocol exists to explore whether useful compute can remain decentralized and whether verification can remain cheaper than execution.

AI inference verificationDistributed scientific workloadsRendering networksSimulation marketsDecentralized benchmarkingVerifiable agent executionCryptographic proof marketplaces

Open Research Questions

01How should useful compute be measured?
02How should fraud be penalized?
03How can deterministic execution scale?
04What workloads qualify as useful?
05Can useful compute remain decentralized?
06Can verification remain cheaper than execution?

ComputeNet does not claim to have fully solved these questions. The protocol exists to explore them experimentally.

Explore the Protocol

ComputeNet is open-source and research-first. Read the whitepaper, explore the architecture, and follow the protocol's development.

Read WhitepaperView ArchitectureOpen ExplorerGitHub