Current release status
Public document hashing and exact integer aggregation are live with signed results. Native consensus, mining, issuance, COMPUTE payments and rewards are inactive. Independent operation is not yet demonstrated.
What a receipt binds
The public result includes a job ID, registered workload/package identity, pinned execution policy, signed execution evidence and output commitments. A receipt is separate from the eight historical ledger blocks.
How to check it
Download the complete result JSON in CVC. The on-device checker verifies the known policy digest, Ed25519 signatures, request/job linkage and output commitment. Recompute your submitted input independently. Four initial signing identities do not mean four independent operators.
Limits
Policy replay agreement is not universal proof of correctness, physical resource metering, legal certification, ledger finality or COMPUTE settlement.
Receipt anatomy and verification
The public service returns a real policy-bound execution artifact. Its fields have specific bindings; they are not an arbitrary proof or an independent-operator census.
| Boundary | Implementation / evidence | Meaning |
|---|---|---|
| assignment | workload_id, package_id, request_id, policy_id | Binds the result to the exact registered job context |
| policy | Known digest and initial signing keys | Compare to an independently retained pin, never trust embedded keys alone |
| evidence[] | Unique Ed25519 execution attestations | Check signatures, successful return code, runtime and stdout digest |
| output_commitment / receipt_id | Canonical commitments | Detect altered execution metadata and receipt contents |
Practical procedure
- 1Retain the complete result JSON, not just a receipt identifier.
- 2Check the known policy, assignment and unique signatures.
- 3Compare the signed stdout digest with the actual returned result.
- 4Recompute the original public input separately; preserve the evidence.
Trusted legacy policy sha256:ca5ccb4ac07f505c8cdc69d5368b677bb2b99c4eb3704655d689fa94c30e7f8e Patched-runtime policy (after qualified cutover) sha256:1b6ae938262ac0ba88b717cf416035def35f223eb5aed75ca149928fbe7eabcf GET /api/public-work/jobs/YOUR_ACTUAL_JOB_ID Receipt agreement ≠ canonical financial finality.
Limits and failure cases
- Signatures authenticate keys, not independent people.
- The initial workers share one administration.
- A local check report is unsigned and does not replace the original receipt.