TESTEDOrdinary participation · own infrastructure · own keys

Your first step into
ComputeNet.

A straightforward, verifiable operator qualification path. No founder credential, financial deposit or permission to generate your own identity. Production consensus and rewards remain inactive.

Join ComputeNet — start qualification ↓

Open participation · safe first step

Join ComputeNet — Operator Qualification

The original simple joining experience, backed by a hash-pinned qualification starter. Download, generate your own identity, run a private TLS rehearsal and inspect an acceptance report. No founder credentials, financial deposit or mainnet activation.

Review the qualification boundary

The starter creates only a local disposable qualification environment. It does not install a daemon, expose a host port, connect to Gamma/Seed, activate consensus, issue rewards, import a wallet or move funds. Building initially downloads signed Ubuntu OS packages; application wheels and the legacy codec runtime are hash-pinned.

I understand this starter is unsigned and qualification-only, on my own authorized machine, with no production joining or reward promise.

Get the qualification starter

One browser download contains the launcher, verified source/runtime/dependencies and clear instructions. A browser cannot silently install software on a server. You run the reviewed command locally.

ZIP SHA-256 · 43.7 MiB

9a592e32294e940b1401fadc8fb901e4e95f2af7439819f369263dd41eb4b503

Integrity pinned · publisher signature unavailable

This ZIP is not publisher-signed and has no verified build attestation. Its hashes check byte integrity, not publisher identity. Compare the checksum through an independently trusted channel before running it; a checksum from this same page is not an independent trust anchor.

Checksums Version / manifest Complete installation and recovery notes

Install and follow real progress

The terminal streams actual checks: source/runtime integrity → fresh identities → useful execution → private TLS synchronization → restart recovery → signed acceptance report. This website does not pretend to monitor a remote installation.

Linux · checksum-checked download · qualification only

# Download the ZIP using the button first. Use your ordinary Linux user.
printf '%s  %s\n' '9a592e32294e940b1401fadc8fb901e4e95f2af7439819f369263dd41eb4b503' 'computenet-operator-starter.zip' | sha256sum -c -
# Use a fresh extraction destination; do not merge with an existing folder.
test ! -e computenet-operator-starter && unzip computenet-operator-starter.zip
cd computenet-operator-starter
python3 join.py --bundle-file qualification-bundle.tar.gz \
  --directory ./my-qualification --accept-qualification-only

If something fails

Keep the directory and starter.log. Correct the exact Docker/platform/digest prerequisite and choose a new private directory. Never disable guards, reuse unexpected state, upload keys or use the obsolete mainnet installer. The starter never restarts Docker or host services.

python3 join.py --directory ./my-qualification --inspect

Check your acceptance report

Select only my-qualification/state/operator-acceptance.json. The browser checks its signature and source/bootstrap scope locally. Nothing is uploaded; never select private identity or wallet files.

Public signed acceptance report

Ready for genuine outside-host qualification?

Keep your own credentials. Publish only a public alias, separate-administration statement and consenting resource/evidence link in the official intake. WAN/peer exposure requires a separately qualified TLS edge and explicit peer consent; this starter opens no port.

Open the existing volunteer intake

Full technical handoff

From local qualification to genuine independent operation

The existing frozen source, protocol decisions, consent and evidence procedures remain available. A successful starter report is a first step, not proof of WAN security, economic independence or mainnet admission.

Open invitation to reproduce ComputeNet’s off-mainnet qualification using your own infrastructure and keys. No founder credentials or financial deposit are required. No operators have been enrolled by this page.

The public Verification Centre is live. Native consensus, COMPUTE payments and rewards remain inactive. This complementary-resource consensus proposal is unratified and unaudited. Tests on one administrator’s containers do not demonstrate independent operation or economic security. No financial returns are promised or funds requested.

Volunteer for independent qualification

Respond in the official volunteer intake thread. Use your own infrastructure and keys. Initially provide only a public alias, independent-administration statement, actual resource/time commitment and consent to off-mainnet tests. Never post credentials, billing secrets, wallet files or confidential inputs. Publishing this invitation does not mean any outside operator has joined.

The thread also requests optional participant consent for a later separately authorised canary: exactly 0.00000008 COMPUTE total, comprising four 0.00000001 verifier payouts and four 0.00000001 producer fees. No funds are collected through the thread; no payer or recipient is presumed. Volunteering is not transfer authority or a promise of income.

Exact proposed core rule contract and its pinned SHA-256. Ratification and production parameters remain pending. Read-only operator measurements and evidence tools collect real data when consenting outside hosts exist; software tests do not supply those commitments.

What the candidate actually requires

Every credited record needs verified, nonempty registered useful computation and fresh complementary resource work. Full nodes recompute results. Receipt counts, payments, holdings and identities add no consensus weight. Useful computation alone has not been established as a scarce resource. Resource-majority reorganisations remain possible, including reversal of confirmed payments.

Verify before running

Check the archive digest through an independently trusted channel. Checksums served by this website are not a trusted maintainer signature or an independent audit. Use disposable identities and funds only; never upload wallets, keys, tokens or confidential workload inputs.

Genuine independent participation

Generate and keep your own keys. Follow the instructions to test on a consenting isolated host. Publish a signed statement and evidence link through a channel you control: source/runtime/bootstrap hashes, separate administration, measured resource commitments and costs, WAN synchronization, restart and recovery results. No sensitive personal information is requested. Another key is not another independent administrator.

Production difficulty, confirmations and funding require actual honest-resource and adversary-cost evidence. No number of test identities substitutes for those commitments. Mainnet activation and real payments require separate ratification, participant consent and production authority.

Use the live public Verification Centre

Your first step intoComputeNet.