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

FAQ

Frequently asked questions for non-technical users, judges, and contributors.

Audience

Non-technical first

Style

Short answers, no inflated claims

Glossary

Included at the bottom

Common questions

  1. 1

    Is YieldBoost AI moving funds automatically?

    Not by default in the code shown here. The product demonstrates optimization logic, proof persistence, and result surfacing. Treat it as a guided demo workflow unless your execution environment explicitly adds the missing production controls.

  2. 2

    What does `Boost My Yield Now` do?

    It runs the default optimization request from the dashboard and then tries to store the resulting proof record so you can verify the outcome.

  3. 3

    What does `Execute Optimization` do?

    It runs the same optimization idea from the Boost page, but with a clearer prompt field and more explicit progress and result surfaces.

  4. 4

    Do I need to know blockchain details to use the app?

    No. A normal user can stay at the level of APY lift, proof receipt, and explorer link. The docs only go deeper when you want to inspect how the system is wired.

Questions judges usually ask

  • What part is live? Answer: the UI flow, wallet context, proof storage route, explorer links, and history surface are real code paths; some optimization and narrative stages can still fall back depending on environment.
  • Is this testnet? Answer: yes by default, unless the active environment has mainnet RPC, storage, and registry configuration.
  • How do I verify it? Answer: open History or the proof modal, then follow the explorer link and compare it with the stored identifiers.
  • What makes it different from a dashboard mock? Answer: the app stores runtime proof records and exposes them consistently across multiple product surfaces.

Glossary

Term
Simple meaning
Where it appears
Why it matters
APY
Projected annual yield rate
Dashboard and Boost result cards
Main performance headline
Tx hash
Blockchain transaction identifier
Proof modal and result surfaces
Fastest verification handle
CID / storage ID
Proof storage identifier
Proof modal and latest result
Used to reference the stored record
ProofRegistry
Optional on-chain registry contract
Proof modal and result card
Adds an extra verification layer
Watch mode
Tracking an address without wallet connection
Sidebar
Useful for demos and read-only review
0G explorer
External verification site
Proof links
Lets reviewers inspect transactions outside the app