Submitting Jobs

Current implementation, supported use and explicit qualification limits.

Experimental Feature

This feature is experimental and may change significantly in future versions.

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.

Submit public data

Use the HTTPS CVC form or POST /api/public-work/jobs. Set public_data_consent=true only for non-confidential public data. The service publishes results/input commitments. Never submit secrets, personal data, credentials or wallets.

Request shapes

Document body: {"kind":"document-sha256","input":{"data_b64":"YWJj"},"public_data_consent":true}. Integer body: {"kind":"integer-aggregate","input":{"values":["12","-3"]},"public_data_consent":true}. These are request examples, not claimed execution results.

Status and signed result

Read job_id from the accepted response, then GET /api/public-work/jobs/<job_id>. A successful HTTP response is not enough: wait for status=verified, inspect errors and verify the receipt. Refresh result in the form if the job is pending. No COMPUTE payment is requested or implied.

Verified HTTPS health endpoint

curl --fail --show-error https://www.compute-net.org/api/public-work/health

This command queries the real gateway. Its response is not a workload result or proof of global worker health.

The real public API contract

The supported integration is HTTPS and explicit public data. There is no invented SDK package or arbitrary-code runtime behind these examples.

BoundaryImplementation / evidenceMeaning
GET /api/public-work/healthNo bodyGateway and pinned-policy observation, not worker uptime
POST /api/public-work/jobskind, input, public_data_consent:trueAccepts registered bounded public work
GET /api/public-work/jobs/:idActual returned job_idPending, failure or verified signed result
Unavailable / invalid requestActual HTTP errorNever a fake receipt or healthy fallback

Practical procedure

  1. 1POST a non-confidential input and inspect the actual response.
  2. 2Retain job_id; poll with a bounded retry policy if pending.
  3. 3Treat verified status as a claim to check, not a proof by itself.
  4. 4Download complete evidence and verify it against the known policy.
Technical reference · scope is explicit
curl --fail --show-error https://www.compute-net.org/api/public-work/jobs \
 -H 'Content-Type: application/json' \
 --data '{"kind":"integer-aggregate","input":{"values":["12","-3"]},"public_data_consent":true}'
# Then GET /api/public-work/jobs/YOUR_ACTUAL_JOB_ID
# Preserve pending/errors; verify the final signed result.

Limits and failure cases

  • Never submit keys, credentials, personal data or confidential inputs.
  • Document input is bounded to 64 KiB; vectors to 1,000 canonical integer strings, each ≤32 characters.
  • This API does not authorize or perform COMPUTE settlement.