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

Technical Reference

Roadmap

What is already real, what still falls back, and the next logical production steps for the project.

Live Now

Docs, dashboard flow, proof storage pipeline, history

Current Limitation

Compute and narrative can still be fallback-driven

Next Frontier

Deeper execution and stronger verifier tooling

What is live now

  • A polished multi-surface workspace with dashboard, Boost, History, analytics, and docs.
  • Wallet connection and watch mode flow inside the sidebar.
  • Optimization requests with streamed narrative and stored result hydration.
  • 0G Storage upload path plus optional ProofRegistry contract anchoring.
  • A proof history ledger that can be demonstrated to judges and contributors.

Known limitations

  • Proof persistence depends on environment configuration; without the right envs, proof storage fails honestly.
  • The portfolio snapshot currently focuses on native balance retrieval plus the latest proof-derived portfolio total rather than a deep multi-asset on-chain portfolio engine.
  • The optimization engine is still demo-oriented and not a production trading executor.
  • Some UX copy references 0G-forward compute language more aggressively than the current compute implementation warrants.

Recommended next steps

  1. 1

    Deepen real portfolio ingestion

    Expand from native balance plus proof-derived totals into richer token discovery and protocol position parsing.

  2. 2

    Strengthen execution realism

    Separate recommendation, simulation, approval, and execution into clearer states with stronger safety controls.

  3. 3

    Make proof verification richer

    Expose proof payload viewing, explorer deep links, registry replay helpers, and failure notes more directly in the UI.

  4. 4

    Extend 0G integration

    Move more of the compute and verification story into explicitly live 0G-backed services so the product claim becomes even tighter.

Contributor notes

This docs center is intentionally typed and component-based instead of markdown-driven so it can stay visually aligned with the product UI and safely reuse live runtime facts.

When you extend the app, update the documentation at the same time, especially for anything that changes the truth around proof storage, registry behavior, network readiness, or fallback rules.