ComputeNet — Join Operator Qualification

This is NOT mainnet activation, mining, an investment or a reward entitlement.
Requirements: ordinary non-root Linux AMD64 user, Python 3.10+, locally authorized Docker 28+ (API 1.49+), approximately 2GiB free disk and 2GiB RAM recommended for Docker/build overhead. The running test container is capped at 1 CPU, 512MiB and 96 tasks. Building initially fetches signed Ubuntu OS packages; pinned application wheels are offline. No third-party Python package install on the host.

Verify the ZIP digest against the website and an independently trusted channel. Checksums are not a trusted publisher signature. Extract into a fresh directory.

Run: python3 join.py --bundle-file qualification-bundle.tar.gz --directory ./my-qualification --accept-qualification-only

The starter verifies source/runtime/wheel hashes, builds its own disposable runtime and generates your own keys. It runs two private TLS processes, genuine registered computation, signed evidence, full replay and a process restart. No host service or port is installed; no outside peer, Gamma, Seed, wallet or funds are used. Real progress streams as JSON in your terminal. The signed public report is under my-qualification/state/operator-acceptance.json. Private keys remain local in restricted directories: NEVER upload them.

This tests qualification software, NOT independent administration, WAN security, production sizing or economic security. Two processes still share your administration. Native production consensus and COMPUTE rewards remain inactive.

If a guard fails: preserve the directory and starter.log. Fix the exact prerequisite, then choose a fresh directory; no unsafe fallback. To read an existing public report: python3 join.py --directory ./my-qualification --inspect. Do not overwrite node keys or reuse unrelated state.

For consenting outside-host/WAN qualification, use the existing frozen README/native CLI and exact public bootstrap/certificate pins only after host-specific network/TLS edge/recovery qualification. The one-command starter deliberately publishes no ports and does not silently expose a node. No founder credentials are necessary.

Runtime note: the frozen Node18 profile reproduces the legacy registered execution codec only inside this offline sandbox. It is not endorsed as a supported public server runtime. A modern runtime requires separate profile/codec qualification.