ROBINHOOD CHAIN · THE LAUNCHPAD RECORD
The Robinhood
launch economy
Where the coins begin, how fast the platforms grow, and what the activity earns. A daily record of launchpad families across Robinhood Chain, with the unclassified activity kept in view.
Every launch day
Daily launches
One token, one creation date. UTC days; the current day is excluded.
Share of mapped launches
Daily launch figures & CSV
Selected family and dates. Missing attribution is a dash.
The launchpads
Compare launches, platform activity and the token behind each venue. Shared factories are grouped; a directory listing alone does not establish a launch count.
Click a column to sort all matching launchpads. Scroll within the table for every row and column. Each volume and revenue cell shows its own latest UTC day; growth is seven complete days versus the previous seven.
Each volume cell identifies a platform feed or an indexed-pool fallback. The latter assigns each DEX swap to the more recently created token in its pair, and excludes unindexed pools and curves. Any day with unpriced swaps has no complete dollar total; its observed priced portion is marked with an asterisk and shown in grey on the chart. Neither measures turnover in the platform’s own token alone. Feeds can overlap underlying exchanges and have different product coverage, so their volumes are not added into a chain total. An asterisk (*) marks only the priced portion of indexed swaps, with the priced/total swap count shown. It is a lower bound, not a complete volume figure. A dash means unavailable, unverified or an incomplete window.
The business behind the launches
Platform volume by day
Protocol revenue by day
Daily financial figures & CSV
Selected launchpad; all financial history on file.
Only complete 30-day windows ending yesterday, with matching token and revenue scope and a recent circulating cap, receive a multiple. Multichain tokens use all-chain protocol revenue where explicitly sourced; the multiple cell prints that denominator separately from Robinhood revenue. Otherwise they stay blank. No FDV substitution, no estimate from swap fees, and no conversion of buyback spending into revenue. Annualising a short history is a run rate, not a forecast.
What returns to the token
Documented buyback programmes, their beneficiaries and the evidence available. An allocation is not proof a purchase happened.
For other directory entries, no buyback policy has been established by this collector. That means unknown, not a confirmed absence of buybacks. Policies are reviewed separately from the daily activity feeds.
The next arrivals
Full factory census CSV ↓New directory entries appear as public sources add them. New token deployers enter the chain census even before their platform has a name.
Unclassified deployers, ranked by recent activity
These can include launchpads, bridges, LP tokens and one-off contracts. They are not counted as named launchpads. The table shows the top 100; the CSV contains every recorded factory and day.
Sources, coverage & method
Download JSON ↓What counts as a launch
The public Dune census joins contract creation traces to ERC-20-shaped mint events in the same transaction on chain 4663. It counts distinct token addresses once per immediate deployer and UTC creation day. Standard NFT transfers and helper contracts without a mint are excluded. Tokens minted only in a later transaction are outside this definition. This measures deployments, not a promise that a token is a meme, tradable or economically active.
Factory mappings identify launchpad families. PONS versions and shared front ends share one row. The Doppler factory includes LONG and other interfaces; those deployments cannot all be attributed exclusively to LONG. The Uniswap UERC20Factory predates the pools.trade instant-launch interface. A listed factory can still use an unmapped helper or introduce a new version, so mapped totals remain a lower bound on attributed activity.
How far the history goes
The first backfill scans the full indexed creation history without a project launch-date cutoff. Daily passes replace the latest four covered days, including days whose corrected counts become zero; monthly passes reconcile the full record. Source indexing can lag or omit records. A successful query establishes the scanned interval, not independent proof that every chain event was indexed.
Money, growth and missing observations
DefiLlama supplies daily protocol revenue and platform volume with Robinhood-specific breakdowns. A second Dune query backfills indexed DEX turnover for mapped factories. Each swap is counted once and assigned to the newer token in its pair, with address order breaking a same-time tie. This is a reproducible allocation rule, not proof of which website routed the trade. Where a platform feed is absent, the explicitly labelled indexed-pool series is used; days containing unpriced swaps remain unavailable. Some feeds exclude older versions, small pools or other product activity. Their own coverage dates and methods remain attached to each launchpad. Growth is the change between consecutive complete seven-day windows; a zero prior period has no finite percentage. Today is excluded. No missing day is filled with zero in financial history.
Token prices and circulating market caps come from CoinGecko where listed. Contract-matched DEX Screener pools can supply a price when CoinGecko is unavailable; their unverified market caps do not feed the multiple. A token's price may be from another chain where the platform token trades. It is a dated public quote, not an executable offer.
Discovery and refresh
The existing 00:30 UTC publishing run refreshes the chain census and unions DefiLlama's protocol, fee and DEX catalogues. Previously seen entries are retained. New public listings are added automatically; new deployer identities remain unclassified until factory evidence is reviewed. Policy notes show their review date. This is open-ended discovery, not a guarantee a public directory has found every new website.
Prices and public financial feeds refresh hourly; the launch census and launchpad directory refresh daily. Indexed DEX history refreshes with the daily census. The page checks the published snapshot every minute while visible. Independent failures retain the source's original observation time and coverage, and remain labelled. Refreshing the page does not make an old source current.