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.
Use the published qualification CLI
The frozen source provides native-work-correction/compound-consensus/node.py init/run/propose for consenting off-mainnet hosts. The reviewed installer only extracts a hash-verified archive into a new directory; it starts no service and installs no private key.
Withdrawn examples
Legacy commands such as computenet node start --mine, unverified one-line installers and unspecified computeverify SDK commands are not supported production instructions.
Trust boundary
Follow the exact source README and preserve private 0700/0600 identity state. Do not use production wallets or mainnet history in writable tests. Actual mainnet activation remains separately gated.
Install, initialize, qualify
The starter preserves the old simple joining intent while replacing its unpinned installer. It is deliberately off-mainnet and uses newly generated local identities.
| Boundary | Implementation / evidence | Meaning |
|---|---|---|
| Software identity | Frozen archive + starter manifest | Verify exact digests before running |
| Execution environment | Non-root disposable Linux container | Read-only root, zero capabilities, private state, no host ports |
| Node initialization | Synthetic public bootstrap / own fresh keys | Never imports a wallet, production history or founder credentials |
| Acceptance report | Locally signed public JSON | Records actual rehearsal results, not independent administration |
Practical procedure
- 1Open Join ComputeNet and review the requirements.
- 2Download and verify the qualification starter using the displayed pinned digest.
- 3Run its explicit qualification-only command in a fresh private directory.
- 4Inspect the acceptance report and retain your local private keys; no automatic upload occurs.
# Open the guided starter at /validator-qualification#join # It checks source/runtime integrity and preserves prior state. # No services, host ports, mainnet activation or financial option. Native CLI reference inside the verified source: node.py init --bootstrap PUBLIC_SYNTHETIC_BOOTSTRAP --sha256 EXACT_BOOTSTRAP_SHA256 --directory NEW_PRIVATE_DIRECTORY
Limits and failure cases
- Two local nodes remain one administrator; an outside operator must run their own infrastructure and keys.
- WAN/public exposure requires consenting peers, independently checked public certificates and host-specific qualification.
- Never reuse production keys or treat installation as reward entitlement.