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

Technical Reference

Roadmap

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

Live Now

Mainnet proof, Judge Mode, Agent NFTs, marketplace

Current Boundary

Recommendation and proof, not autonomous fund execution

Next Frontier

Deeper execution safety and Proof-of-Optimization

live-now

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 Integrity Auditor and stored result hydration.
  • 0G Storage upload path plus ProofRegistry contract anchoring on the configured default network.
  • Judge Mode with mainnet/testnet switching and ChainScan links.
  • Strategy Agent NFT minting through YieldStrategyINFT.
  • Marketplace listing/adoption view for proof-backed Strategy NFTs.
known-limitations

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 recommends and proves strategies, but it is not a production autonomous trading executor.
  • The on-chain INFT `verified` flag is reserved for the attestation oracle path, so proof-backed NFTs can exist even when that flag is false.
next-steps

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

    Deepen Proof-of-Optimization

    Turn repeated high-quality optimization events into richer scoring, reward, and marketplace signals for future $YA0G mechanics.

contributor-notes

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.