Documentation

YieldBoost AI Docs Center

Product context, honest integration notes, user walkthroughs, 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

UI-ready deterministic scoring with streamed narrative fallback

Platform & Trust

Troubleshooting

Common runtime failures, what they usually mean, and which page or env to check next.

Best Debug Surface

History + console + API response

Most Common Cause

Missing env or wallet context

Store Fallback

Vercel KV primary store with local file fallback

symptom-table

Symptom table

Symptom
Likely cause
Where to check
Recommended response
Docs or app route 404
Route missing or server not rebuilt
Local dev server logs
Restart dev server and verify route tree
No wallet balance shown
No address, RPC off, or RPC error
Sidebar + portfolio API
Connect/paste a wallet and confirm RPC env
Optimization request failed
Agent route or provider issue
Boost page + `/api/agent/optimize`
Retry with default prompt and inspect provider envs
Proof storage failed
0G envs missing
`/api/0g/store` response
Set RPC, storage URL, and private key for the target network
No ProofRegistry entry
Registry address not configured or tx failed
Result card note + server logs
Describe the run as storage-only and fix env later
History empty after run
Store write failed or different wallet context
Runtime store + latest agent route
Check store backend and requested wallet address
debug-order

Recommended debug order

  1. 1

    Check the sidebar first

    Make sure the wallet and network state are what you think they are. Many downstream issues begin with an empty or mismatched wallet context.

  2. 2

    Check the API that owns the failing step

    Portfolio issues start at `/api/portfolio`, optimization at `/api/agent/optimize`, and proof persistence at `/api/0g/store` or `/api/0g/proof`.

  3. 3

    Check the store backend

    History and latest-proof views depend on the runtime store, which can be KV-backed or local-file-backed depending on the environment.

honest-demo-recovery

How to recover during a live demo

  • If ProofRegistry is unavailable, say the environment is running in storage-only mode and continue with the explorer link and stored receipt.
  • If LLM output falls back, explain that the recommendation wording degraded gracefully while the proof and UI pipeline stayed intact.
  • If the wallet provider is unavailable, switch to watch mode with the demo wallet so the review can continue without blocking on extension setup.