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.
• 0G Compute broker inference is attempted when the active network has a compute provider address and ledger signer configured.
• Integrity Auditor checks the recommendation before the proof write and before Agent NFT minting.
• The UI consistently surfaces the resulting storage tx hash, explorer link, Integrity Auditor status, ProofRegistry transaction, and mainnet contract artifacts.
• The current explorer path is built from the configured explorer base and the returned transaction hashes.

0G Compute and attestation metadata

• 0G Compute is the highest-priority narrative path when configured, falling back honestly if unavailable.
• The UI displays verification metadata only when it exists in the returned proof package.
• Attestation metadata can be persisted in the stored proof record and linked to Agent NFT verification.

How proof enters 0G Storage

1. 1

   Serialize decision payload

   The app creates a temporary JSON file that includes optimization values, timestamp, Integrity Auditor result, optional compute metadata, 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, Integrity Auditor fields, compute metadata, 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