Getting started
Testnet onlyFind a source you want to follow, read what its vault actually holds, and deposit.
Testnet. Nothing here has been deployed to mainnet, and the deploy script refuses chain 4663 outright. Connecting a wallet and depositing work against a local chain and the testnet; withdrawal is not yet wired for signing.
#1. Find a source account
The homepage is the market. Each listing shows who the vault follows, what it holds, and how closely it currently matches.
Four separate verification facts are shown, and they never merge into a single tick:
| Badge | What it proves |
|---|---|
| Fomo profile | An identity resolved through FomoScan. Advisory — it decides which address to observe, never what the vault mirrors. |
| Linked X account | The account claims an X profile. Self-declared and not verified. A claim, not a proof, and not X verification. |
| Verified Source address | Source eligibility passed: a resolved EVM address with observed Robinhood Chain activity, activated onchain. |
| Observed on Robinhood Chain | The displayed address has validated onchain activity. |
Only the third is drawn as a check, because it is the only one asserting a proof. A source that fails eligibility is still listed and still labelled — hiding it would present the market as cleaner than it is.
#2. Read what the vault actually holds
Open a vault. The sheet shows NAV, every position with its allocation as a share of NAV, the cash held, and — importantly — where the vault currently differs from its source and why.
Two numbers deserve attention:
- Return reads No history rather than
0.00%. There is no NAV series yet, so no return can be computed. A zero would be a claim. - Allocation is only shown when every held position can be priced. If one cannot, no percentages are claimed for any row, because a portfolio summing to 91% while presenting itself as complete is worse than one that explains itself.
#3. Deposit
Depositing mints shares at the vault's current NAV. Browsing a deposit requires no wallet: NAV, capacity, caps and constraints are all read from chain and shown before any connection is requested.
A deposit is refused, with the reason stated, when:
- deposits are paused on that vault;
- the vault is at its NAV cap;
- NAV cannot currently be computed, because pricing something wrongly is permanent.
See Depositing.
#4. Know how you get out
Before depositing, read Withdrawals and in-kind exits. The short version: burning shares for a pro-rata slice of everything the vault holds has no pause switch and no price-feed dependency, and it is the guarantee the rest of the design is arranged around.
#Running the stack yourself
The whole system runs locally against an Anvil node. Deploy the contracts, seed a market, then start the API and the web app:
pnpm install && pnpm verify:chainEvery command, with its expected output, is in the repository's local development guide.