vaulted pools capital into on-chain vaults that mirror the best fomo traders programmatically. this page is the whole manual: the three vault classes, the path a trade takes from a tracked wallet to the vault, every risk limit with its default and its trade-off, how money goes in and comes out, and what it costs.
vaulted is a vault protocol on robinhood chain. you deposit into a vault, the vault's execution engine mirrors the trades of a chosen fomo trader, a fomo clan, or a curated basket of traders, and you hold shares whose value rises and falls with that strategy. when the strategy is profitable, you earn. when it is not, the share price goes down.
in one sentence: the fomo leaderboard, turned into an asset class.
vaulted is not fomo. it is an independent protocol built on top of the public fomo leaderboard and public on-chain activity. it is not affiliated with, endorsed by, or operated by fomo or robinhood.
every vault is the same contract with the same engine. the classes differ only in what signal source the engine follows.
| class | tracks | who creates it | fee share to |
|---|---|---|---|
| user vault | one fomo trader's wallet | anyone, permissionlessly, against a wallet that meets the criteria | the trader, once claimed |
| clan vault | a clan's member wallets, weighted | anyone, against a ranked clan | the clan members, once claimed |
| protocol vault | a curated basket by strategy theme | the protocol | constituent traders, pro-rata to signal contribution |
each user vault tracks a single fomo trader's wallet. when the trader buys a token on robinhood chain, the engine detects the transaction and executes a proportional buy from pooled vault capital within the same or next block. when they sell, the vault sells proportionally.
any trader whose fomo-linked wallet meets the minimum criteria can have a vault proposed against them: 90 days of history, a minimum realised pnl, minimum win consistency, and no wash-trading flags. the trader can then claim the vault. a claimed vault is strictly better for the trader: the more capital that follows them, the more they earn from fees rather than only from their own book.
fomo clans are team-based trading squads ranked by collective pnl. a clan vault copies the aggregate behaviour of a clan's member wallets rather than one individual, with configurable weighting:
| weighting | what it follows |
|---|---|
| equal | every member wallet at the same weight. |
| pnl-weighted | members in proportion to their rolling pnl. |
| core member default | the two or three members with the deepest consistent records, rather than whoever got lucky once. |
a clan's rank can be carried by one or two outsized positions; the weighting model smooths that out and captures the consensus signal. when several core members independently accumulate the same token before it moves, the vault treats that as a high-conviction entry.
baskets we design, curate and rebalance on a fixed cadence, bi-weekly, under public inclusion and exclusion rules: rolling 30/60/90-day pnl, drawdown profile, consistency score, and behavioural flags. a trader who dumps on followers is excluded.
| vault | basket | profile |
|---|---|---|
| rh trader · flagship | top traders concentrated on robinhood chain: native memecoins and, where available to the vault's jurisdiction, tokenized-stock momentum. | where the densest signal lives: about 75% of fomo volume settles here. |
| solana trader | top fomo traders whose edge is on solana: launches, bonk-class assets. | solana exposure via cross-chain routing or robinhood-chain-native representations; the execution model is disclosed per vault. |
| degen | the fastest, most aggressive short-horizon traders: launch snipers, momentum scalpers. | tight per-position caps, hard stops, strict drawdown breaker. frequent small losses, occasional large wins. the highest-variance product here. |
| long-term | position traders with long holds, low turnover, multi-month consistent pnl. | more majors and tokenized equities, lower rebalance frequency, lower fees, looser withdrawal terms. |
read the drawdown before the return. every vault page shows historical max drawdown and worst month as prominently as returns. these are trading strategies, not fixed-income products.
an indexer watches the wallets each vault tracks in real time, mempool and confirmed transactions, across the supported chains. every observed trade is normalised into a signal: wallet, token, side, size as a percentage of the trader's own portfolio, venue, timestamp.
the signal goes to the execution engine, which trades vault capital through robinhood chain dex aggregation with slippage bounds. before it fills, the engine runs the signal through the vault's rules. the first one that matches stops the copy, and the skip is logged on the vault page with its reason:
| rule | skipped when |
|---|---|
| circuit breaker | the vault is past its max drawdown threshold. no new entries until it resets. |
| tracking suspended | the tracked wallet has repeated anti-dump flags. |
| latency budget | the signal is older than n blocks. it is discarded, not chased. |
| blacklist | honeypot, flagged rug, or a contract younger than the age threshold. |
| minimum liquidity | the fill would make the vault more than x% of the pool. |
| max position · max concentration | the vault is at its per-token cap, or the portfolio would be too concentrated. |
| skin in the game | the vault would hold more than the allowed multiple of the trader's own dollar position. |
| delay and verify | the trade deviates sharply from the trader's history. executed at reduced size, or held one verification epoch. |
| slippage cap | the quote exceeds the cap even after order splitting. |
because the vault trades in the same or next block as the tracked trader rather than after a push notification reaches a human, its fill quality is structurally better than manual copying. that is the core mechanical edge, and the tracking-difference chart on every vault is where you check it.
the vault copies proportions, not absolute amounts. a trader putting 3% of their book into a token results in the vault putting up to 3% of vault capital into it, capped by the limits below. there is no per-depositor setting: every share in a vault gets the same exposure.
a $400 buy from a $40,000 book is 1%. the vault buys 1% of its nav, whether that is $10,000 or $1,000,000.
what it implies: the vault's book keeps the shape of the trader's book, probes included. what stops it from also keeping the trader's mistakes at scale is the cap stack below.
each member's signal is scaled by their weight before sizing. under core-member weighting, a signal from outside the core is sized down or ignored.
what it implies: two core members buying the same token compounds into a larger entry. that is by design: consensus is the signal.
limits are set per vault and published on its page. protocol vaults set them by strategy: the degen vault runs the tightest caps and stops, the long-term vault the loosest. a claimed user vault lets the trader set a deposit cap, never loosen a risk limit.
no single token can exceed this share of the vault, whatever the trader does.
what it implies: a trader's 40% conviction bet becomes the vault's 10% bet. you keep the direction, not the leverage of their conviction.
a portfolio-level cap on how much of the vault sits in its largest positions.
what it implies: it caps how much one theme can do to the vault, not how much the vault spends.
the vault never becomes more than this share of a token's pool. the fill is sized down to the floor, or skipped.
what it implies: the vault can always leave through the door it came in by. this is the rule that most often turns a signal into a partial fill on small launches, and the tracking-difference chart shows the cost.
the vault will not hold a position larger than this multiple of the tracked trader's own stake in that token.
what it implies: if the trader's own stake is trivial, the vault's stays trivial. a trader cannot steer large vault capital with a tiny personal bet.
a fill that would exceed the cap is split across blocks. what still cannot fill inside the cap is dropped.
what it implies: the vault pays for the trader's move, not for its own footprint. on a violent candle a large vault fills worse than a small one, and worse than the trader.
a signal older than the budget is discarded rather than chased.
what it implies: the vault never buys the candle the trader created. a discarded signal is a missed entry, and a missed entry is cheaper than a late one.
maintained by the protocol, applied to every vault.
what it implies: the degen vault misses some very early launches. that is the price of never holding a token that cannot be sold.
if a tracked trader sells into a position shortly after the vault entered, the pattern is flagged. repeated flags trigger automatic tracking suspension and, for protocol vaults, removal from the basket. trader-claimed vaults contractually acknowledge these rules; violating them forfeits accrued fee share.
what it implies: the single biggest failure mode of social trading, influential traders exiting into their followers, is priced against the trader, not the depositor.
executed at reduced size, or held for one verification epoch.
what it implies: the vault is slower on the trades that look least like the trader. those are also the trades most likely to be a mistake or a setup.
past the threshold, new position entry pauses and the vault can de-risk to stables.
what it implies: a paused vault is not a closed vault. exits still mirror, withdrawals still settle, and in-kind redemption is always open.
three ways, in order of how often they happen:
a token that cannot be sold. if a route disappears, the position is marked unsellable, its cost booked as a loss in nav, and the tokens stay in the vault. in-kind redemption hands you your slice of them; the position comes back if a route does.
open continuously, in usdc or eth on robinhood chain. deposits mint shares at the current nav. nav is computed from on-chain oracle pricing of the vault's positions: share price = vault nav ÷ shares outstanding.
withdrawals use a short epoch so the engine can unwind illiquid positions in an orderly way instead of market-dumping into thin pools. you request, the request settles at the nav of the settlement block.
| vault | settlement |
|---|---|
| long-term | fastest, looser terms |
| user · clan · rh trader · solana trader | 24 to 72 hours |
| degen | the strictest, at the top of the range |
any depositor can redeem in-kind at any time: burn shares, receive your pro-rata slice of the vault's actual token positions plus stables. no epoch, no queue, no permission. it is the guarantee that funds are never truly locked, and it is enforced by the contract, not by us.
what in-kind means in practice. you get the tokens, at the size and in the pools the vault holds them. selling them is then your job, and on a thin memecoin that is the very problem the epoch exists to handle. it is the exit you take when you do not trust the epoch, not the exit you take for convenience.
| fee | rate | charged on |
|---|---|---|
| management | 1–2% annualised, streamed | nav, continuously |
| performance | 15–20% | profit above the high-water mark only |
| deposit · withdrawal | none | gas and dex fees are paid by the vault as part of execution |
the high-water mark means you never pay a performance fee twice on the same gain: after a drawdown, no performance fee accrues until nav is back above its previous peak.
the performance fee splits three ways: the protocol treasury, the tracked trader or clan if they have claimed the vault, and a buyback and incentive pool. protocol vaults route the trader share to the basket's constituent traders pro-rata to their signal contribution. the exact split is published per vault.
everything is inspectable on the vault page:
a user vault is proposed against a wallet; the trader behind it can claim it by signing from the fomo-linked wallet. a claimed vault:
a claim cannot loosen any risk limit, pause withdrawals, or touch depositor funds. a clan vault is claimed the same way by the clan's members, and the fee share is split among them.
no. a vault is a trading strategy. its share price goes up when the tracked traders are profitable after fees and slippage, and down when they are not. the drawdown figures on the vault page are the ones to read first.
you can, and most people who do lose money: the signal reaches you late, you size badly, and the trader can exit into your buy. the vault fills in the same block, sizes proportionally, and enforces the limits above. it does not make the trader better. it removes the ways copying them loses on top.
no. the vault tracks a public wallet; the trader has no key, no role and no permission on the contract. claiming a vault gives them a fee share, a deposit cap and a display name, nothing else.
one of the rules in how a copy happens: past the latency budget, under the liquidity floor, at the position cap, over the skin-in-the-game multiple, on the blacklist, or held for verification. every skip is logged on the vault page with the rule that caused it.
24 to 72 hours for most vaults, faster for the long-term vault, at the top of the range for the degen vault. if you cannot wait, redeem in-kind and receive the tokens themselves immediately.
their positions are unwound over the epoch, their signals stop, and their share of future performance fees goes to zero. the basket change is published with the rule that triggered it.
no. a claim can set a deposit cap and a display name. risk limits can only be tightened by the protocol, never loosened by anyone.
on a memecoin strategy, yes: a token that cannot be sold is booked as a loss, and a strategy can draw down past its breaker before it pauses. the caps limit how much of the vault any single token can take with it. they do not make the strategy safe.