Discovering Vaults

Implemented

How the market is ranked, what each badge proves, and what the four lifecycle states mean.

How the market is ranked, what each badge proves, and what each lifecycle state means.

#Ranking

Tab	Order
Top vaults	Sources that passed eligibility first, then by NAV. An unverified identity is never promoted into the top listing.
Most traded	By actual mirrored trade volume from indexed chain events. Not by NAV, and not by anything self-reported.
New	Reverse registry order — newest deployment first. There is no deployment timestamp in the snapshot, and inventing one to sort by would be a fabricated field.
Following	Reserved for a connected wallet. Empty until signing is wired.

New and curated carries one specific meaning of curated: the source passed the implemented eligibility rules and was activated onchain. It is not a rating, an endorsement, a performance claim, or a statement that anyone reviewed the trader's judgement.

#The four badges

Each answers a different question. They are rendered as four separate marks and there is no code path that merges them.

flowchart LR
  H["A handle"] --> R{"Resolves through<br/>FomoScan?"}
  R -- yes --> F["Fomo profile<br/>(advisory)"]
  R -- no --> U["Unresolved identity"]
  F --> E{"EVM address<br/>returned?"}
  E -- "no — or non-EVM only" --> X["Not eligible:<br/>structural mismatch"]
  E -- yes --> A{"Observable<br/>Robinhood Chain<br/>activity?"}
  A -- no --> N["Not eligible:<br/>no_robinhood_activity"]
  A -- yes --> V["Verified Source address<br/>(the only proof badge)"]

A linked X profile sits outside this flow entirely: FomoScan documents that field as self-declared and not verified, so it can never be part of an eligibility decision and is never drawn as a tick.

#Lifecycle states

State	Meaning
In sync	The vault matches every snapshot it has accepted.
Pending	The source has moved and the vault has not caught up yet.
Awaiting keeper	There is an actionable change nobody has called `sync` for.
Deposits paused	Deposits refused. Existing shares unaffected; withdrawal unaffected.
Execution paused	Mirroring halted. Withdrawal in kind still works.
NAV unavailable	A held position cannot be priced, so no NAV is claimed and deposits are refused.

Full definitions, with the exact condition that produces each, are in Status definitions.

#Identity data in this build

Identities come from recorded local fixtures, and the whole surface is labelled Development data with a line stating which half is fixture and which is read from chain. Vault balances, positions, trades, pause flags and lifecycle state are all live chain reads.

Fixture identities carry no photographs. Where a provider supplies none, the interface draws a monogram — never a generated face, and never a pattern pretending to be one.