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.
Off-mainnet installation only
Use the published hash-pinned qualification source and its reviewed fresh-directory installer. Never run an unverified curl-to-shell script or the old legacy Docker instructions as a mainnet installer. Do not copy production wallets, keys, databases or ledger files into a writable test runtime.
Identity and participation
Generate your own private qualification identity locally. Independently compare source/bootstrap/runtime hashes, control your own TLS certificate and infrastructure, and validate history. No founder credential, financial deposit or staking transfer is needed for off-mainnet qualification.
Mainnet status
The released qualification CLI rejects the actual mainnet checkpoint and is not a writable-mainnet activation tool. No production joining, mining or reward entitlement is activated by installing it.
The layered verification pipeline
Different verification mechanisms answer different questions. The implemented public lane makes a narrow result independently checkable; broader proof systems remain research.
| Boundary | Implementation / evidence | Meaning |
|---|---|---|
| Identity / package | Recovered ZIP 1 and ZIP 2 tooling | Identifies code, inputs and runtime declarations |
| Execution / replay | Registered Node profiles | Real bounded hashing and exact integer arithmetic |
| Signed evidence | Ed25519 / known policy | Authenticates an execution attestation |
| General proofs | ZK / zkVM / hardware attestation | Research—not qualified guarantees in today’s public service |
Practical procedure
- 1Choose a supported profile and explicitly public input.
- 2Execute fixed source under the qualified runtime boundary.
- 3Compare outputs across separate replay processes.
- 4Verify the signed artifact and recompute the supported result.
Public input → registered package → bounded execution → assignment-bound signatures → output and receipt commitments → portable result / on-device checks
Limits and failure cases
- No arbitrary customer program, AI proof or universal correctness claim.
- A deterministic output can be independently recomputed; administration independence needs separate evidence.
- No synthetic score is substituted when execution or signature validation fails.