The 0G modules we use, and what each one carries.

Every receipt anchors here. The chain is what makes a verification two years from now produce the same answer as the verification ten seconds after the run.

endpointhttps://evmrpc.0g.ai ↗

The specialist runs inside a TEE so the plaintext is invisible outside the run. The TEE attestation is what makes verificationMethod: router_flag and compute_sdk_process_response honest claims; --tee-independent re-runs the broker check on a separate machine.

endpoint@0gfoundation/0g-compute-ts-sdk v0.8.x

The encrypted blob and the signed receipt JSON live here. The blob storage root is recorded inside the receipt; anyone can fetch the ciphertext later and confirm it matches.

endpoint@0gfoundation/0g-storage-ts-sdk v0.4.x

Carries the inference traffic and supplies the per-provider rate-limit and cost telemetry the receipt records. A reviewer can read the receipt and see how the work was billed.

endpointIVARONIX_ROUTER_URL (legacy: ZG_SERVICE_URL) — surfaced as routerTrace.x0gTrace inside every receipt

Every receipt is bound to a passport tokenId. A delegated agent (planning-01 §2A) gets its own passport so the trustScore accrues to the agent itself, not the operator. The receipt is signed by an AgentPassport-resolvable wallet — the chain confirms the signer matches.

endpointAgentPassportINFT — custom ERC-7857 implementation (V1 legacy + V2 K-1/K-4/K-6 fix)

On the integration roadmap. We do not claim integration we have not shipped. The path — receipt batching and evidence sharding via 0G DA — is documented in docs/PHASE_B_DISCLOSURES.md, and we will wire it when a public testnet endpoint is available.