// Documentation

Build and trade
Robinhood Chain meta indexes.

HoodFunds is a wallet-first ETF layer for Robinhood Chain metas. A Hood is a tokenized basket: creators define a thesis, choose underlying Robinhood Chain or Robinhood Chain tokens, set weights and rules, and traders buy one index position instead of manually chasing every component.

One buy

A trader enters a full meta basket through a single Hood route. The split across underlying tokens is handled by the protocol layer.

Visible vaults

Weights, holdings, status, fees, and redemption mode are treated as first-class data. No fake TVL and no decorative volume.

Robinhood Chain native

Wallet connection, USDG settlement, Uniswap v4 routing, and Uniswap v4 liquidity where available. The product is designed around mainnet behavior.

// 01

Core concepts

HoodFunds separates the idea of a meta from the act of manually buying every token inside it. The creator publishes a Hood definition. The buyer sees one tradable surface. The protocol keeps the basket state readable.

Term	Meaning
Hood	A tokenized basket around a Robinhood Chain thesis: AI agents, DePIN, gaming, new launchpads, or any other liquid meta.
Underlying	A token held by the basket. Each underlying has a target weight and routing policy.
Vault	The on-chain or indexed accounting layer that tracks holdings, weights, status, and redemption rules.
Creator fee	An optional fee that can reward the creator while keeping the basket composition visible to traders.
Redeem mode	A controlled exit state where holders can move out through underlying assets when a Hood is closed or unwound.

// 02

Quick start

Connect a Robinhood Chain wallet. Use the wallet button to open the connection modal. After connection, the dashboard becomes the control room for creating and monitoring Hoods.

Pick the meta. Define the basket thesis, ticker, underlying tokens, target weights, creator fee, and max buy settings.

Review routing. HoodFunds prepares the swap route using Robinhood Chain liquidity, with Uniswap v4 first and Uniswap v4 where relevant.

Launch or save draft. Until real contracts are connected, the dashboard keeps drafts local and never pretends fake TVL or fake volume exists.

// 03

Create a Hood

A Hood definition should be small enough to audit and strict enough to route. Avoid vague names and unbounded allocation rules. The best Hoods make the thesis obvious from the ticker and holdings.

{
  "ticker": "AI-META",
  "name": "AI Agent Meta",
  "chain": "Robinhood Chain",
  "settlement": "USDG",
  "underlyings": [
    { "symbol": "GOAT", "mint": "...", "weight": 25 },
    { "symbol": "ZEREBRO", "mint": "...", "weight": 25 },
    { "symbol": "ARC", "mint": "...", "weight": 20 },
    { "symbol": "FARTCOIN", "mint": "...", "weight": 30 }
  ],
  "creatorFeeBps": 50,
  "maxBuySol": 25,
  "redeemMode": "creator-controlled"
}

Good basket rules

Weights add to 100, each mint is explicit, max buy protects thin pools, and fee rules are visible before launch.

Bad basket rules

Hidden substitutions, missing mint addresses, fake liquidity claims, or any language that implies guaranteed performance.

// 04

Buy flow

The buy path is intentionally boring: connect, quote, approve, route, settle, index. The UI should make every irreversible step clear before a wallet signs anything.

The trader selects a Hood from the directory or dashboard.
HoodFunds reads the basket definition and current status.
The router estimates underlying swaps against available Robinhood Chain liquidity.
The trader reviews expected allocation, slippage, fee, and max buy cap.
The wallet signs the transaction only after explicit approval.
The position updates with the basket state once settlement is confirmed.

No background buys. Wallet connection is not a trade approval. The connect modal may open for authentication, but any actual token movement must remain an explicit wallet action.

// 05

Vault states

State	Behavior	Trader expectation
Draft	Creator is composing basket settings.	Not tradable.
Active	Buys are open and routing can execute.	Review quote and sign manually.
Paused	New buys are disabled while state is reviewed.	Existing holders wait for update or redemption instructions.
Redeem-only	Entry is closed, exits can be processed through underlying assets.	Use holder exit path, not new buys.
Closed	The Hood is archived or fully unwound.	Historical state remains readable.

// 06

Wallet and access

HoodFunds uses a Robinhood Chain wallet connection as the primary entry point. The public project id can live in browser code, but any secret key, privileged API token, signer, or admin route belongs server-side only.

Connect wallet to enter the dashboard.
Keep wallet connection separate from transaction approval.
Show the connected address and network state clearly.
Never display secret keys or private signer material in HTML.

// 07

Dashboard

The dashboard is the working surface for creators and early testers. Its current job is to make the system tangible without inventing metrics.

Builder

Draft a Hood with ticker, thesis, weights, fee, and buy cap.

Status

Show wallet, USDG balance, API health, and bootstrap readiness.

Preview

Display the index definition before any on-chain launch path is enabled.

// 08

API reference

The current backend exposes lightweight bootstrap endpoints. They are intentionally conservative: health, account shell, stats shell, and Hood draft/directory data.

Endpoint	Purpose
`GET /api/health`	Returns service health and basic runtime status.
`GET /api/me`	Returns the current account shell once wallet/session wiring is present.
`GET /api/stats`	Returns real system readiness fields only. No fake TVL, fake volume, or fake user count.
`GET /api/hoods`	Returns Hood definitions or draft examples used by the frontend.

// 09

Risk model

HoodFunds does not remove market risk. It packages a meta into a clearer trading surface. Underlying tokens can move sharply, lose liquidity, or fail. Quotes can change between preview and transaction confirmation.

On-chain transactions are irreversible after confirmation.
Thin pools can create high price impact; max buy caps exist to reduce that risk.
Creator fees should be disclosed before a trader signs.
Redemption rules must be visible before launch.
Nothing in the interface should imply guaranteed returns.

// 10

FAQ

Is HoodFunds live trading yet?

The frontend and bootstrap backend are wired. Live trading should wait for final vault contracts, routing checks, and signer review. The site should not display fake production metrics before that exists.

Why use a Hood instead of buying tokens manually?

A Hood gives one thesis, one route, visible composition, and a cleaner holder surface. It is meant for traders who want meta exposure without manually maintaining every component.

Does connecting a wallet buy anything?

No. Wallet connection only identifies the user and enables the dashboard. A buy requires a separate quote and explicit wallet approval.

Where should announcements live?

Use the official X account: @hoodfunds.