Historical ledger and separate execution evidence

A preserved historical ledger and verified useful compute.

The eight historical blocks are preserved, not advancing production consensus. New public signed execution receipts are separate evidence and are not financial ledger anchors.

Historical Blocks

8

Historical Height

7

Historical Issuance

350 COMPUTE

Native Consensus

Inactive

Payments / Rewards

Inactive

Independent Operators

Not demonstrated

Genuine public execution examples

Dated qualification runs from 12 November 2026. These are signed execution examples, not an aggregate customer feed or ledger-anchored payments.

Dated public evidence
Public Job IDWorkload TypeAdministrationEvidence basisStatusTimestamp
35832594d1ec4d24…document-sha256One administrationSigned execution evidencePublic qualification example2026-11-12T19:25:47.000Z
8287124d6d4a00e9…integer-aggregateOne administrationSigned execution evidencePublic qualification example2026-11-12T19:26:13.000Z

What the Ledger Records

Supported public jobs return signed evidence; receipts are separate from canonical financial records and are not immutable ledger anchors.

Workload Hash

Cryptographic fingerprint of the compute task, ensuring integrity from submission to completion.

Result Hash

Deterministic hash of the compute output, enabling independent verification by any party.

Validator Signatures

Policy-bound signatures from separate processes under one initial administration; independently controlled validators are not demonstrated.

Evidence basis

Legacy score concept; not a measured correctness probability and not used as live consensus evidence.

Challenge Status

Record of any fraud challenges raised and their resolution through on-chain arbitration.

Epoch Inclusion

Protocol epoch in which the receipt was finalized and added to the canonical ledger.

Why This Matters

ComputeNet transforms useful compute into a verifiable public record. Every AI inference, every simulation, every data transformation becomes an auditable entry in an open ledger. This creates accountability without centralization, enabling trust in distributed computation through cryptographic proof rather than institutional authority.

Cryptographically verifiable
Independently auditable
Permissionlessly accessible

Build on the Ledger

Integrate verified compute into your applications. Query receipts, validate proofs, and build trust into your infrastructure.

Developer docs

No simulated receipt rows are displayed. Historical financial records and public execution receipts are separate. No token sale, ICO, or investment offering is being conducted.