# ComputeNet mandatory useful computation + complementary resource qualification

**Off-mainnet, unratified, unaudited. No returns, payment promises or production participation are offered.** The public Verification Centre is live; native consensus, issuance and COMPUTE rewards are inactive. These are new isolated protocol amendments, not the original whitepaper's proven useful-work scarcity construction.

Every credited record must carry a correct, public, nonempty registered document-SHA256 or integer-aggregate computation. Each full node recomputes its result; signed evidence binds to the exact parent/height/network/protocol/time/producer. A producer signs proof of possession. Semantic computation identity ignores runtime/order/key changes. A valid package with an already known result can qualify once on a canonical branch; the protocol does NOT prove a physical execution, economic demand, global off-chain uniqueness or independent people from signatures.

**Ordering security comes from additional fresh native header resource work, not from receipt count, job price, fee recycling, holdings or identity count.** Header roots bind useful payload and financial contents. No empty/header-only/control records, stake committee, founder veto, unknown work scheme, free payment-derived weight, or issuer override. Without fresh qualifying work the head stalls; peering, status and recovery continue. New valid tasks resume operation; there is no committed stop-height.

## Reproduce and join without founder credentials

Download the qualification archive, `install_validator.py`, SHA256SUMS and these instructions from the existing public operator-qualification page. Obtain digest confirmation through an independently checked channel. A checksum from the same compromised website is not a publisher signature. This qualification archive has no trusted maintainer signature and is NOT an approved mainnet release.

```sh
python3 install_validator.py --artifact computenet-compound-qualification.tar.gz --sha256 EXACT_PUBLISHED_SHA256 --destination ./computenet-qualification
cd computenet-qualification
python3.12 -m venv .venv
.venv/bin/python -m pip install --require-hashes -r candidate/requirements-hashed-linux-amd64-py312.txt
.venv/bin/python -m pytest native-work-correction/compound-consensus/tests -q --tb=short
.venv/bin/python -O native-work-correction/compound-consensus/measure.py
```

Use only reviewed hash-pinned wheels (offline `--no-index --find-links` where available). Actual Node execution requires the root-owned exact Node18.19.1/native-library profile and supplemental externalised JS source pins in `evidence/NODE-BUILTINS.json`; do not substitute binaries or relax the native executor ownership guards. The qualification image is a local reproduction vehicle, not a published container image. These old runtime pins reproduce the deployed execution codec; they are not a security-update endorsement. A runtime change requires its own source/profile qualification.

Tests generate **synthetic** eight-block history, ordinary identities and balances; never import a real wallet or production ledger into a writable test environment. `evidence/SETTLEMENT.json` is synthetic public data, not mainnet. Obtain the public off-mainnet bootstrap+digest from a consenting rehearsal. Each participant independently verifies its complete source pins and synthetic history. To create a private loopback node:

```sh
.venv/bin/python -I -B native-work-correction/compound-consensus/node.py init --bootstrap bootstrap.json --sha256 EXACT_BOOTSTRAP_SHA256 --directory ./my-node
.venv/bin/python -I -B native-work-correction/compound-consensus/node.py run --directory ./my-node --peers ./peers.json
# Separately, with your own identity and explicit non-confidential workload:
.venv/bin/python -I -B native-work-correction/compound-consensus/node.py propose --directory ./my-node --origin https://127.0.0.1:18444 --ca ./my-node/tls-cert.pem --workload public-workload.json
```

`public-workload.json`: `{"kind":"integer-aggregate","input":{"values":["7342","-7"]},"public_data_consent":true}`. Change input for the next task; repeating it cannot earn canonical credit. This consent publishes input/result permanently on the rehearsal history. No customer payment is necessary for a utility witness. For a consenting isolated private subnet pass `--bind YOUR_NUMERIC_IP --port 18444 --isolated-cidr EXACT_PRIVATE_CIDR`. For an independently owned external qualification host, `--qualification-public` is an explicit unprivileged opt-in; existing Gamma/Seed endpoints and the actual mainnet checkpoint are refused. Do not expose the raw node until its TLS edge/rate/connection/body/time limits, firewall, backup and provider recovery have passed host-specific qualification. No production service installer is included.

`peers.json` contains 1..8 operator-chosen entries: `{"origin":"https://NUMERIC_IP:18444","ca_file":"/absolute/path/peer-cert.pem","ca_sha256":"EXACT_CERT_SHA256"}`. Exchange only public certificates and source/bootstrap pins. Do not disable certificate validation. No founder credential is needed. New ordinary keys can propose valid work without a membership roster; four local receipt keys are labelled one administrator and have **zero consensus voting power**.

## Independent evidence to return

No application/admission committee, financial deposit or unnecessary personal information. The public invitation requests off-mainnet reproducibility/qualification only. Publish a signed operator statement and evidence link through an operator-controlled public channel; participation does not require sending credentials to the founder. Do not send private keys, wallet files, tokens or unrelated logs. Real people have not been enrolled or fabricated by this release.

Record source/archive/bootstrap/runtime pins, your ordinary public identity, evidence of separate administrative/infrastructure control, own key custody, actual sustained useful execution/header throughput, CPU/memory/storage/cost and resource commitments, WAN propagation/loss/jitter, multi-peer history replay, partitions, reorg/replay rejection, restart/snapshot recovery and safe founder-infrastructure outage. Another key or container is not another administrator. Keys/profiles cannot prove physical or human independence. Measure concentration and effective honest resource after founder outage; no arbitrary operator count is a security threshold.

The disposable envelope is LinuxAMD64/Python3.12/Node18.19.1, 1 CPU quota,384MiB,64 tasks, read-only root, no capabilities, no-new-privileges, internal TLS network and no host ports. It is not a production sizing/cost/DoS/WAN certificate. All test instances share one Docker host/administrator. Full-history validation/retained branches/backups consume increasing CPU/storage; capacity exhaustion stops admission, never silently discards history. Production pruning/scaling and edge load qualification remain separate acceptance requirements.

## Security and financial limits

Greatest fully validated expected header work orders history. Equal-work conflicts flag ambiguity and withhold local confirmation. No quorum certificate, receipt count, key splitting or paid quote adds weight. Any superior valid work can reorganise payments, including after a local confirmation. There is no finite unconditional maximum reorg depth and no irreversible BFT finality. Safety requires sufficient effective honest external resources, timely propagation and non-eclipsed clients. A majority-resource adversary can still reorganise. Identity splitting does not create hashes but hardware concentration/ASICs/rentable capacity matter.

The original 12/16 capture records are invalid under this protocol; that is NOT proof against resource-majority reorganisation. Recycled/self-paid jobs can supply payloads but cannot manufacture header proof. If useful tasks are absent, liveness stops rather than awarding empty work. A complementary resource consumes energy beyond the useful task: this is the exact material trade-off for ratification.

Customer-funded payout signatures, quote bounds, exact fee accounting, duplicate/nullifier/nonce checks and replayable balances reuse the original native settlement boundary. Isolated tests include real Node execution, four signed verifier receipts, four 1-base-unit payouts plus four 1-base-unit producer fees (8 units total), confirmations, superior-work reversal, pending re-inclusion and recovery. Funds/identities are synthetic. No live payment or new issuance occurred. The original21million cap,50/210000halving schedule, protected350issued/342balance/ordinal7 and stopped mining remain. Future issuance eligibility/cadence/recipients require explicit ratification; zero issuance here is not permanent abolition.

See `RATIFICATION.md` for the single amendment and remaining actual-resource/financial approval gates. Keep production inactive until satisfied. No external audit, trusted publisher signature, WAN qualification or genuine founder independence is claimed.