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.
Implemented cryptography
The public service uses Ed25519 execution signatures and SHA-256 content commitments under explicitly pinned policies. Legacy receipts retain sha256:ca5ccb4ac07f505c8cdc69d5368b677bb2b99c4eb3704655d689fa94c30e7f8e; the qualified patched-runtime policy is sha256:1b6ae938262ac0ba88b717cf416035def35f223eb5aed75ca149928fbe7eabcf. Embedded public keys alone are not a trust anchor.
What signatures do not prove
A valid signature binds a message to a key. It does not prove independent administration, truthful physical execution, sufficient scarce resources, universal computational correctness or financial finality.
Research mechanisms
General ZK/zkVM, universal correctness proofs and hardware-attestation integrations are not qualified public features. Do not interpret diagrams/placeholders as deployed cryptographic guarantees.
Trust boundaries and practical checks
Security comes from specific controls and explicit assumptions. No website badge, AI review or internal test count is an independent security audit.
| Boundary | Implementation / evidence | Meaning |
|---|---|---|
| Browser boundary | Same-origin HTTPS / fixed upstream routes | No caller-selected upstream or server-side wallet signing |
| Evidence boundary | Pinned policy / canonical commitments / Ed25519 | Reject altered, duplicate, unknown or mismatched attestations |
| Execution boundary | Fixed source, bounded input/runtime, non-root isolation | No arbitrary uploaded program or privileged host command |
| Economic boundary | Production activation remains gated | A receipt cannot authorize issuance, payments or governance |
Practical procedure
- 1Verify software/policy provenance through an independently trusted channel.
- 2Keep private identities local with restricted permissions.
- 3Retain authentic evidence and classify the scope of each successful check.
- 4Stop on source/state/runtime mismatches; never replace a failed check with a simulated success.
Read-only source and pinned artifacts ├─ HTTPS public API / bounded inputs ├─ qualified fixed-source runtime ├─ known-policy receipt verification └─ separate financial/consensus activation gate
Limits and failure cases
- Signatures do not prove independent administration or arbitrary computation correctness.
- Internal tests are scoped evidence; they are not an external audit or economic-security guarantee.
- No certified SOC/ISO/GDPR service or paid bounty commitment is claimed.