Useful computation.
Evidence you can verify.
Run a genuine bounded workload, follow its result, inspect every signature and take the complete Compute Receipt with you. No fabricated customer activity. No synthetic confidence score.
Exact integer reconciliation
An actual public run—not a live volume counter
Signed result
10
4 submitted integer strings
Receipt boundary
Execution evidence
No ledger payment or finality
job_id: 8287124d6d4a00e9349d9255ce7e2ee2ba2180b6de099b4d535a84f4c18875a5
receipt: sha256:0ce80720e6826c699147da904c8fb327f592f28a776d4bde9ecda2c2c0b6eb81
Document + integers
Signed Compute Receipt
Not yet demonstrated
Inactive
Public gateway observation
Observation not loaded yet.
Source: same-origin HTTPS /api/public-work/health, with the policy digest checked locally. Gateway reachability is not proof of worker health, service uptime, throughput or ledger consensus. Submit a job to check execution.
The timestamp and round-trip above belong to that browser-to-gateway request. Worker uptime, aggregate daily volume, global validator latency and independent node counts are not inferred. Mining, issuance, COMPUTE payments and rewards remain inactive.
The verified compute standard
An inspectable result, layer by layer
The original dashboard’s architecture is useful when every stage has a specific claim and evidence boundary. These are capabilities, not security scores.
Genuine bounded execution
Registered source executes on public infrastructure. Document hashing and exact integer aggregation are available today.
Authenticated evidence
Assignment-bound Ed25519 evidence under a pinned policy. Initial replay processes share one administration.
Independent result checking
Inspect commitments, verify signatures on your device and recompute supported results from the submitted inputs.
Native network integration
Compound ordering and receipt-bound settlement have isolated tests. No production consensus, payment or reward activation.
The verification journey
From workload to portable evidence
Explore each boundary. The diagram explains architecture; it is not a simulated live job or a map of independently administered validators.
Canonical workload identity
Recovered ZIP 1 tooling gives a deterministic identity to a declared workload. Code, public inputs and runtime declarations are committed; changing the input changes the workload identity. An identity is not a correctness proof or a meter of physical compute.
- Canonical descriptor and deterministic input representation
- Code / input commitments
- Explicit workload and package identifiers
workload_id → cmp_work_… package_id → cmp_pkg_… These exact values are inspectable in a genuine receipt.
Your own execution
Submit. Recompute. Verify.
Use non-confidential public data only. The result below comes from the service, then its policy/signatures and your input are checked locally. A pending or failed job is never replaced with a demonstration result.
Run a bounded computation
Document SHA-256 or exact integer aggregation. Signed replay receipts, with no ledger finality or COMPUTE payment. Initial workers share one administrator. Availability is reported by the service; no demonstration results are substituted.
Authentic evidence · inspect, don’t assume
Inside a Compute Receipt
Choose a genuine public qualification execution, inspect your newly submitted result, or open a local result file. These are signed execution records—not synthetic customer activity or canonical payments.
Evidence explorer
LIVEFiles are never uploaded. Report dates and example results are not network-volume metrics.
Evidence you can take apart
Select a real record to reveal its assignment, signers, result and commitments. No sample receipt is marked verified before its cryptographic checks pass.
Check a downloaded signed result
Choose the complete JSON downloaded from the live submission below. This device checks the pinned service policy, Ed25519 signatures, job and output commitments. Files are not uploaded. This is signature verification, not a new execution or a claim of independent operators.
Execution topology, not an invented federation
Different boundaries. Different evidence.
The current gateway, bounded replay processes and historical ledger serve different purposes. Multiple keys or hosts under one administrator are not independent network operators.
HTTPS gateway
- Same-origin public work API
- Strict bounded request shapes
- Private upstream connection
- Observed availability, not global uptime
Replay and receipt policy
- Registered source and runtime
- Separate execution processes
- Known policy; 3-of-4 signing requirement
- Initial identities share one administration
Historical ledger
- Eight original blocks at height 7
- 350 issued / 342 reconciled balance
- Separate from public execution evidence
- Native financial activity remains inactive
Developer integration · genuine HTTPS contracts
Build with evidence, not a placeholder SDK
The existing bounded API supports public submission, result lookup and health observations. Examples use actual request shapes; HTTP success alone is not verification.
# Submit only non-confidential public inputs.
curl --fail --show-error https://www.compute-net.org/api/public-work/jobs \
-H 'Content-Type: application/json' \
--data '{"kind":"integer-aggregate","input":{"values":["12","-3"]},"public_data_consent":true}'
# Read job_id, then request its actual status/result:
curl --fail --show-error https://www.compute-net.org/api/public-work/jobs/YOUR_JOB_ID
# Pending is not verified. Save the complete JSON and check its signatures in CVC.Supported contract
- GET /api/public-work/health
- Gateway/policy observation; no worker uptime inference.
- POST /api/public-work/jobs
- Fixed-source, bounded, explicitly public inputs.
- GET /api/public-work/jobs/:id
- Actual pending/error/verified status and complete signed result.
No hidden financial operation
These examples do not enable mining, customer debits, rewards, issuance or production consensus. Arbitrary uploaded code, general SDKs and enterprise/compliance products are not offered.
Read the API guideWhere verification is useful
Start with what can actually be checked
Live bounded profiles are practical building blocks. Broader use cases remain research—not customer deployments, certifications or paid products.
Document integrity
Check the exact digest of public text and retain signed execution evidence.
Exact reconciliation
Sum public integer quantities without floating-point rounding and inspect the receipt.
AI and agent verification
Workload-specific assurance and reproducible model execution remain research.
Scientific workloads
Broader deterministic packages and independent assurance require qualification.
Access and scope
Choose a real next step
There is no invented enterprise catalog, compliance certification or production reward plan. Each path below corresponds to available software or an accurately identified research area.
Use public verification
- Two bounded deterministic profiles
- Explicitly public inputs only
- Signed JSON results and local checks
- No COMPUTE payment requested
Join operator qualification
- Verified source and installation
- Your own disposable identity
- Private TLS rehearsal and report
- No mainnet or financial activation
Explore the architecture
- Detailed Truth Stack layers
- Reproducibility and receipt schemas
- Native consensus security assumptions
- Broader workload/proof limitations
No invented confidence.
Inspect the evidence.
The strongest presentation is a real result you can independently recompute and a signature you can check. Native decentralized consensus and COMPUTE rewards remain separate, inactive qualification work.