What is live in the 0G integration

• Network configuration is modeled explicitly for testnet and mainnet in the wallet layer.
• The proof storage route can upload a JSON proof package through the 0G TypeScript SDK when the active network has RPC, storage URL, and private key configured.
• TEE-verified inference is available via 0G Compute Network when the active network has a compute provider address and ledger signer configured.
• The UI consistently surfaces the resulting storage tx hash, explorer link, TEE attestation badge, and optional ProofRegistry transaction.
• The current explorer path is built from the configured explorer base and the returned transaction hashes.

TEE-verified inference via 0G Compute

• TEE inference is the highest-priority narrative path when configured, falling back to deterministic narrative if unavailable.
• The UI displays a 'TEE Verified' badge in the agent panel and proof modal when attestation is present.
• TEE metadata (provider, model, chat ID, verification status) is persisted in the stored proof record for audit trails.

How proof enters 0G Storage

1. 1

   Serialize decision payload

   The app creates a temporary JSON file that includes optimization values, timestamp, TEE metadata (if available), and `appId: yieldboost-ai`.

2. 2

   Upload through the 0G SDK

   The storage route wraps that file with `ZgFile`, then calls the indexer upload flow using the configured RPC and signer.

3. 3

   Capture the returned metadata

   The route stores the returned root hash, tx hash, block info when obtainable, wallet address, explorer URL, TEE attestation fields, and optional note flags.

4. 4

   Persist locally or in KV

   The proof record is inserted into the runtime store so History, the proof modal, and the latest agent state can all read the same record.

Compute and narrative fallback behavior

Network matrix