0G is the judge. We are the hands.

One errand, end to end: 0G decides, our agent acts, and each finished errand goes to 0G as an episode anyone can check.

Decisions on 0G Compute, episodes on 0G Storage and 0G Chain

An errand starts with one question to 0G.

“Buy me a chai.” Our Robot Agent sends facts only, and 0G answers with one decision.

  1. Robot Agent

    Item, invoice, budget left today, policy flags, merchant trust. No camera frames, no keys.

  2. decide

    0G Router, one forced tool call, temperature 0.

  3. Logged

    The answer, its reason, the 0G request id and chat id, the model and provider.

0G picks. Our agent does it.

0G never moves the duck and never touches money. It only chooses one of three answers.

When it ends, the errand becomes an episode.

Paid, denied, walked away or stopped: every ending writes one small record.

episodeId  the errand
robotId    which duck
item       "chai"
decisions  [ step, model, provider,
             requestId, chatId,
             action, reason, outcome,
             promptSha256, latencyMs ]
outcome    paid + Arc tx hash
             (or denied, walked_away, safe_stop…)
             approval id, if a human said yes
requestIds every 0G request id
  • Why it was bought: each 0G answer with its reason.
  • Where to trace it: the 0G request ids and the Arc payment.
  • No keys, no camera frames.
  • No prompt text: only its sha256.

Kept on 0G Storage, anchored on 0G Chain.

A small uploader outside Cloudflare picks up finished episodes, so the Worker never holds the storage key.

  1. Uploader

    Collects finished episodes from the app, up to 5 attempts each.

  2. 0G Storage

    The episode JSON is uploaded. 0G returns its root hash.

  3. EpisodeLog

    record(episodeId, rootHash, requestIdsHash) on 0G Chain.

requestIdsHash is keccak256 of the 0G request ids joined with commas, so the chain also fixes which 0G decisions the episode used. Today this runs on the Galileo testnet: EpisodeLog is 0x4C947E6D…E51a206A.

Anyone can check it.

Three places, kept by different parties, have to say the same thing.

Same root, same bytes, same request ids. On 6 Nov all 7 episodes decided by 0G passed this check from outside.

One step further, the TEE. On a TeeML model such as glm-5.3, an answer can also be checked with 0G's own SDK, which confirms it came from the provider's TEE. In our one test the signature was still there after 15 minutes and gone after 20, so this check is best run soon after the errand.

Space or arrow keys for the next screen