payloads
Every protocol interaction produces structured payloads that are validated against Zod schemas and persisted to 0G Storage. This page documents the key payload types and their lifecycle.
Job Definition
The complete job specification is uploaded to 0G Storage during preparation, producing the jobHash that anchors the entire lifecycle.
ts
Result Payload
When a provider submits results, the output is uploaded to 0G Storage, producing an immutable resultHash.
ts
Attestation Payload
Each attestation is also uploaded to 0G Storage, producing an attestationHash.
ts
ID Conventions
All protocol IDs are generated with specific prefixes to identify their entity type during routing and logging.
| Prefix | Entity | Description |
|---|---|---|
| prep_ | Prepared Job | Unfunded, pending payment |
| job_ | Confirmed Job | Funded, assigned to nodes |
| qt_ | Quote | Pricing requirement |
| prov_ | Provider | Compute agent identity |
| ver_ | Verifier | Consensus node identity |
| svc_ | Service | Compute capability |
| att_ | Attestation | Signed TEE evaluation |