Assets
Tokenized stocks
How the collateral list for equities is sourced — live from Robinhood Chain's own registry.
Stock-token collateral isn't a hand-maintained list. It's fetched live from Robinhood Chain's own asset registry, so a newly tokenized stock appears as eligible collateral in the UI without a code change.
Where it comes from
GET https://api.robinhood.com/rhj/assets- Only assets with
status === "ASSET_STATUS_ACTIVE"are kept. - Only the deployment matching Robinhood Chain mainnet (
chainId 4663) is used — an asset with no mainnet deployment is dropped entirely. decimals,symbol, and contract address all come straight from that deployment record.- The response is revalidated every 900 seconds (15 minutes) via Next.js's fetch cache, proxied through
/api/protocol/tokensfor client components.
Display order isn't eligibility
A hand-ranked list of ~35 large-cap tickers (NVDA, AAPL, MSFT, and so on) exists purely to put recognizable names first in preview grids that only show a handful of tokens — the alphabetical registry order alone buries them under names like AAOI. This list only reorders; it never filters. A ticker absent from it is just as usable as collateral, and simply sorts alphabetically behind the ranked ones.
The registry is the eligibility check, not the frontend
Even if a token shows up in this list, the deployed LendrMarket contract still independently enforces its own allowedCollateral(token) allow-list, fixed at deploy time. The registry determines what the UI offers to show; the contract determines what it will actually accept.