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

Platform & Trust

Wallet & Security

How wallet connection works, what watch mode means, and what safety boundaries users should understand.

Supported Wallets

MetaMask, Rabby, Coinbase, Trust, OKX

Fallback Mode

Manual watch-only address

Security Boundary

Non-custodial recommendation and proof UX

wallet-modes

Wallet modes in this app

Mode
How it starts
What it can do
Caution
Connected mode
Injected wallet connect flow
Reads account, listens for account/network changes
Still only as safe as the current environment config
Watch mode
Manual address entry
Tracks a valid address without provider auth
No signing and no provider-backed network context
Disconnected
No valid address yet
Shows empty states
No live optimization possible
security-notes

Security notes

  • The app does not custody funds in the code shown here; it orchestrates wallet context, optimization output, and proof storage metadata.
  • The current public deployment is mainnet-first on 0G Mainnet, while 0G Testnet stays available for comparison.
  • A proof receipt is not the same thing as guaranteed profitable execution. It is evidence of what the app recommended, audited, produced, and stored, not a promise of future APY.
  • Do not commit `.env.local`, API keys, private keys, access tokens, or wallet secrets into Git.
0g-storage-data-safety

What the app stores in 0G Storage

The proof route writes a compact JSON proof package that is meant to support verification and replay of the optimization result. In the current implementation, this package can include the optimization decision, timestamp, wallet-scoped metadata, and a portfolio snapshot when the client provides it.

That means the stored record is useful for auditability, but it should be described honestly: it is proof-oriented application data, not a private zero-knowledge portfolio vault.

Data type
Current behavior
Why it exists
What it does not include
Optimization decision
Stored
Lets judges and users inspect the recommended route and APY change later
Does not include private keys or seed phrases
Integrity Auditor result
Stored
Shows whether the recommendation passed the anti-hallucination guardrail
Does not guarantee future market outcomes
Wallet-scoped metadata
Stored
Keeps proof history tied to the review wallet
Does not grant signing authority
Portfolio snapshot fields
Optionally stored
Helps replay the recorded context behind the proof
Not a full encrypted vault of wallet history
Secrets and credentials
Not stored
Should remain in envs or wallet software only
Never belongs in proof payloads
network-switch

How network switching works

When a supported injected wallet is connected, the sidebar can request a network switch or add the target chain if it is missing.

The selected network is also saved into local storage and cookies so the rest of the app can fetch portfolio and proof data consistently across reloads.

demo-wallet

Demo wallet consistency

The current default demo wallet is 0x8a3c7524Aaed081825aC88eC7f4cCECFc583ee7D. If `NEXT_PUBLIC_DEMO_WALLET_ADDRESS` is set, the app uses that value; otherwise it falls back to the repository default.

Keep documentation, screenshots, and spoken demos aligned with the active demo wallet to avoid confusing reviewers when the address shown in the sidebar differs from the docs.