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.
Unavailable service
An unavailable/timeout/rejected result is not a successful verification. Refresh once, retain the job ID, inspect the explicit error and do not substitute sample data. CVC signatures are checked under a pinned policy.
Qualification problems
Stop on source/lockfile/runtime/profile drift, unsafe permissions, TLS errors, unexpected staging files, missing recovery access or invalid history. Do not disable certificate checks, namespaces, ownership guards or resource limits to make a test pass.
Support
Use the official volunteer intake for non-sensitive qualification reports. Do not post wallet files, credentials or confidential workload data. Native activation and payments need separate authority.
Durability, interruption and safe recovery
Qualification can rehearse interruptions without touching protected mainnet state. Recovery must distinguish service evidence from canonical financial records.
| Boundary | Implementation / evidence | Meaning |
|---|---|---|
| Public evidence | Retained signed result JSON | Verify signatures and compare the original service lookup |
| Private node state | Own identity / durable local store | Never restore an unrelated or stale writer |
| Snapshots | Verified source and state hashes | Restore into a fresh qualification directory first |
| Production cutover | Exclusive authoritative writer / explicit approval | Not enabled by a website or installer |
Practical procedure
- 1Keep verified evidence, exact source/runtime pins and current state.
- 2Stop only your own affected qualification process on an integrity failure.
- 3Restart with the same verified private identity and validate the recovered head.
- 4Use forward recovery after real canonical advancement; do not reset historical balances.
Preserve evidence → verify hashes → fresh restore rehearsal → validate complete history/accounting → start one authorized writer Starter recovery test: private process restart only. No production rollback, service restart or funds are involved.
Limits and failure cases
- Local simulated restarts are not independent WAN continuity evidence.
- No instruction here authorizes production service/firewall/authentication changes.
- Private identities and financial wallets must never be uploaded as diagnostic evidence.