Documentation

YieldBoost AI Docs Center

Mainnet proof flow, Judge Mode, Integrity Auditor, Agent NFT minting, marketplace adoption, and developer reference for the current state of YieldBoost AI.

Current Status

0G Mainnet is the active default workspace path, while the judge review can still switch networks on demand.

Runtime Truth

Mainnet-first optimizer with Integrity Auditor, proof storage, and Agent NFT minting

Back to dashboardOpen Judge Mode
Docs home

Optimization Flow

Proof & Verification

How proof records are created, stored, surfaced in the UI, and verified by a reviewer.

Primary verifier view

History + proof modal

Explorer base

https://chainscan.0g.ai

Registry mode

ProofRegistry is configured for 0G Mainnet

proof-package

What the proof package contains

The stored decision payload includes current APY, optimized APY, estimated gain, recommendation, confidence score, and reasoning text when available.

After a storage write succeeds, the app pairs that decision payload with transaction metadata such as storage tx hash, timestamp, block number when available, wallet address, Integrity Auditor result, and ProofRegistry metadata when anchored.

reading-identifiers

How to read tx hash, storage ID, and explorer links

Field
Where it appears
How to read it
Why it matters
Tx hash
Proof modal, dashboard proof row, latest result
Primary storage write transaction
Fastest external verification handle
CID / storage ID
Proof modal and result cards
User-facing storage identifier returned by the proof flow
Connects the run to stored content
Integrity Auditor
Proof modal, Judge Mode, stored payload
APPROVED or REJECTED guardrail result
Shows the AI output was checked before proof/mint
Explorer link
Proof modal and result cards
Direct link into the configured 0G explorer
Lets a reviewer verify outside the app
ProofRegistry tx
Result card or proof modal
Separate contract write for registry anchoring
Shows on-chain indexing layer
history-and-verification

How history and verification work

History is the proof ledger view for the current runtime store. It summarizes runs, shows the newest proof rows, and exposes a judge-friendly verification summary.

The proof modal prefers live stored proof data from `/api/0g/proof`; if a CID lookup is not available, it can still resolve receipt metadata from a known transaction hash so older Agent NFTs do not appear as pending forever.

  • Use History to show how proof entries accumulate across runs.
  • Use the proof modal when you want to focus on one record and copy tx hash or storage ID.
  • Use explorer links when the reviewer wants an external source of truth.
proofregistry-explained

How ProofRegistry works in this app

When a ProofRegistry address is configured for the active network, the storage route attempts a second write after the storage upload. That contract write records the proof reference and APY basis points into the registry contract.

The stored proof record is then enriched with registry address, registry tx hash, explorer link, and proof ID when the emitted event is available.

ProofRegistry write intent

text
recordProof(cid_or_rootHash, rootHash, storageTxHash, currentApyBps, optimizedApyBps)