ComputeNet Whitepaper

Compute anywhere. Verify through ComputeNet. ComputeNet is a computational-verification ecosystem. The live public service performs bounded document hashing and exact integer aggregation, returning policy-bound signed execution evidence. Broader decentralized verification and native consensus remain qualification work.

Reproducible workload identities, execution packages, replay and signed evidence help users inspect computation. They do not by themselves prove arbitrary program correctness, economic security or independent network administration. The current service does not execute arbitrary customer code or AI workloads.

The intended protocol is permissionless and ownerless, with equal ordinary participant rights. This is a design objective, not the current deployment state. Seed, Gamma and the initial execution/signing identities share one administration; actual independent consensus participation has not been demonstrated.

The existing website and CVC reach a server-side HTTPS gateway. Supported jobs run in bounded execution environments; separate verifier processes issue Ed25519 evidence under a pinned policy. Public receipts are separate from the protected eight-block historical ledger. The compound native ordering and settlement adapter is an isolated candidate, not a production writer.

The frozen compound proposal requires unique eligible useful computation plus fresh complementary native resource work. Empty records, copied receipts, duplicated computation and recycled payments must not manufacture canonical credit. Successful tests do not establish a sufficient security-resource budget. No such ordering or new COMPUTE issuance is active in production.

For the two live deterministic profiles, users can independently recompute the result and verify policy-bound signatures and commitments. A signature authenticates an attestation by a key, not universal correctness or independent ownership. General ZK/zkVM proofs, arbitrary AI verification and hardware attestation are not qualified public guarantees. Truth Stack research is described separately.

Two known infrastructure hosts are not two independently administered operators. Four signing keys in the initial execution policy are not four independent validators. Fresh peer reachability, global regions, network-wide latency, uptime and validator throughput are not inferred from configured addresses. Off-mainnet volunteer qualification is available without founder credentials; live consensus joining is inactive.

The unactivated compound candidate proposes greatest fully validated accumulated resource work, conditional on qualified useful computation. Confirmations are probabilistic and reversible; there is no guaranteed finality depth or unconditional maximum reorganisation. Resource-majority, propagation and eclipse assumptions must be supported by real independent resource commitments before activation. Insufficient eligible useful jobs means a stalled head, never empty-work credit.

The live service returns a complete signed result JSON with job, assignment, policy, evidence and result commitments. Download it in CVC and check the pinned policy and signatures locally. Recompute the submitted input separately. Signed execution evidence does not establish COMPUTE settlement, ledger finality, legal compliance or independent administration.

Isolation, bounded input/runtime limits, HTTPS, source/policy pins and signature validation are real engineering boundaries. Internal tests and AI review are not an independent security audit. Compromised keys, implementation defects and shared administration remain material risks. Do not submit confidential data, credentials or wallet keys to public workloads.

CVC reports an actual gateway health observation, client check time and request round-trip when available. This is not worker uptime, consensus health or global peer latency. Aggregate throughput, verification volume, region coverage and independent validator counts are not published as measured production metrics.

The protected computenet-mainnet-1 history has eight blocks at height 7, 350 COMPUTE historical test issuance and a reconciled migrated balance of 342 after transfers of 5, 2 and 1. The declared cap is 21,000,000; original subsidy research specifies 50 COMPUTE and halving every 210,000 issuance events. Mining, new issuance, customer payments, transaction fees and rewards are inactive. Neither this page nor a receipt ratifies future economics or authorizes changing balances.

LIVE: bounded document hashing, integer aggregation, signed receipts and their public HTTPS interface. ISOLATED CANDIDATE: compound consensus, receipt-bound settlement, recovery and ordinary operator tooling. NOT ACTIVE: production native consensus, mining, issuance, COMPUTE payments and rewards. NOT DEMONSTRATED: genuine independent operator control, resource security and founder-offline live continuity. The original PDF is a historical research artifact and may contain superseded status descriptions.

A useful-computation network with independent operators and verifiable native accounting remains the intended destination. Broader workloads, economic security and ownerless live operation require additional qualification and explicit protocol/economic and production approvals. They are not offered as current service guarantees.

Preserve original history and wallet access, publish reproducible technical evidence and make future participation objective rather than founder-privileged. Historical founder-controlled test issuance must be disclosed; intentions of fair participation are not evidence of an already independent launch.

The live public service is experimental bounded computation verification; it is not an active reward or investment offering. No guaranteed value, returns, mining income, compliance certification or universal correctness proof is promised. No financial or consensus activation is authorized by these web descriptions.