CCompared · 4 min read

Robinhood Chain launchpad survival rate compared

Robinhood Chain launchpad survival rate, defined and computed live: the share of each pad's tokens whose pool still holds liquidity 30 days after creation.

938 words · about 4 minutes·Article updated 20 August 2026
The short answer

Robinhood Chain launchpad survival rate measures one thing: how many of a pad's tokens still have a pool holding liquidity a month after creation. Use it to see which pads produce launches that keep trading. Do not use it to pick a winner — it says nothing about price, and nothing about your launch.

How Robinhood Chain launchpad survival rate is computed

Survival rate is the share of a launchpad's tokens whose pool still holds liquidity 30 days after pool creation, computed from Locksley's index of Robinhood Chain pools. A pool counts as surviving if it holds any liquidity at the 30-day mark. It counts as not surviving if liquidity was withdrawn, burned to zero, or never replaced after graduation.

Three deliberate choices sit inside that definition. Tokens created less than 30 days ago are excluded, because they have not had the chance to fail yet. Price is not part of it — a pool down heavily still counts as surviving. And the measurement is per pool, not per project, so a token relaunched under a second pool appears twice.

One row below is our own. MintPlus is Team Finance's free launch route, and Locksley is built by TrustSwap and powered by Team Finance, so read that row with the relationship in view. Pads are listed alphabetically, not ranked.

Launchpad30-day survival rateLaunches in the sampleLive page
FlappendingpendingFlap launches
MintPluspendingpendingMintPlus launches
PonspendingpendingPons launches
All indexed padspendingpendingAll launchpads

As of pending, Locksley indexes pending launchpads on Robinhood Chain. Every row uses the same definition, the same 30-day window, the same exclusion of tokens younger than 30 days and the same pool-state reads from the contracts. No pad, ours included, is measured on a different rule.

What the rate does not measure

It is not a return. A pad whose tokens all survive at a fraction of their opening price scores exactly the same as a pad whose tokens survive and rose.

It is not a promise about the next launch. The rate describes tokens already created; yours is not in the sample.

It is not a quality judgment on the pad. A pad used mostly for experiments will show a lower rate than one with a high entry cost, and the difference is a filter on who launches there rather than a difference in the software.

It is not a lock. Surviving liquidity can still be withdrawn tomorrow unless it is held by a liquidity lock or burned. A lock guarantees exactly one thing: the pool cannot be withdrawn before the release date. Not the price, not the team, not the token. A locked pool can still fall.

Why a high rate does not cause anything

Survival rates differ across pads. The pad is one candidate explanation and rarely the strongest one.

The people who choose a pad differ. Entry cost, audience and reputation sort projects between pads before a single contract is deployed, so a pad's number partly reports who showed up. Timing differs too: a pad busy during a quiet stretch produces a different cohort from one busy during a rush, and both cohorts are dated. Default settings differ — a pad that locks or burns the pool position at graduation mechanically produces surviving pools, which is a property of the default, not evidence about the pad's users.

Correlation is what this table has. Causation is what it does not. Read a rate as a description of a cohort that already happened, and nothing more.

How to actually use the table

Compare pads with similar sample sizes. A rate computed over a handful of launches moves wildly on one outcome; a rate over a large cohort moves slowly.

Then look past the rate at the mechanism, because the mechanism is what applies to you: what the pad charges, what happens to the pool position at graduation, and whether that position ends up locked, burned or back with the deployer. Every Robinhood Chain launchpad, compared lays those out side by side, and Pons vs Flap vs MintPlus takes the three named pads head to head.

If a pad's liquidity handling is unstated, treat it as unknown rather than assuming either outcome. On a token page, "No lock found" means we found none — not that none exists. Locksley does not yet index every locker.

Whichever route you take, the decisions that survive contact with the market are the ones in tokenomics that don't look like a rug. The free route, MintPlus, runs through launch a token on Robinhood Chain — and the disclosure applies again here, because Locksley is built by TrustSwap and powered by Team Finance, so that is our own product being pointed at.

Frequently asked questions

How is launchpad survival rate calculated?

Survival rate is the share of a launchpad's tokens whose pool still holds liquidity 30 days after pool creation, computed from Locksley's index of Robinhood Chain pools. Tokens younger than 30 days are excluded from the sample. Price is not a factor: a pool that holds liquidity counts as surviving regardless of what it is worth at the 30-day mark.

Does a high survival rate mean a launchpad is better?

No. The rate describes what happened to one cohort of tokens, and pads attract different kinds of projects at different costs, which shapes the number before the software does. A pad that locks or burns the pool position by default will mechanically produce surviving pools. Compare the mechanisms and the fees alongside the rate.

“No lock found” means we found none, not that none exists: we do not index other lockers yet, and it is never a claim about the project.

FiguresEvery number on this page is frozen at the date printed beside it and refreshed when the page is rebuilt — not live. The sentences reason about the figures, so a value that changed underneath them would make the prose wrong. Live values live on Explore and the pages it links out to. Methodology →
CorrectionsFound something wrong? Send the page and what you computed instead through the contact page. Every correction is logged publicly.
ReusePublished under CC BY 4.0. Quote it, translate it, fork it — cite the page and the date.
Who wrote thisWritten and maintained by the Locksley editorial team. Locksley is built by TrustSwap, which also owns Team Finance — the tool linked above.