- LAUNCH is a place to make your own coin, and to trade coins other people made. Making one takes a couple of minutes and costs about $2.00. "The pad" on the rest of this page just means this site.
- You choose what your coin is priced in. That choice is called the peg — dollars, ETH, or the price of a share. It is the measuring stick your coin is worth something against. You pick it once, when you make the coin, and it can never be changed.
- There is nobody on the other side of your trade. The price comes from a formula instead of from a buyer or a seller: every purchase pushes the price up, every sale pushes it back down. That is why a big order gets a worse price than a small one.
- Every trade pays a small fee — 0.25%–2.00% of what you trade, set by whoever made the coin — and 25 cents of every fee dollar is spent buying $LAUNCH, this site's own token, on the open market.
- Most coins made here end up worth nothing. Only put in money you are genuinely fine with losing. Nothing on this page is a promise that anything goes up.
Everything below is the same thing again, with the exact maths and live numbers you can move yourself. You do not have to read it to use the site.
Mechanics no mystery.
This page explains, in plain terms, exactly how the pad works before you put money in.
The product is called LAUNCH IT. The address is li.app — L for Launch, I for It. Launching and trading are one surface, not two apps: trade.li.app is the same site, pointed at the terminal.
Every number on this page is solved by the same two engines the pad trades on — the curve and the fee split — running here in your browser. Move a slider and the docs re-derive. If the code changed, this page would change with it, because there is nothing typed to go stale.
The curve
The single function every price on this site comes from. Move the sliders and each figure below re-solves in your browser.
A coin on LAUNCH has no order book and no market maker. It has two virtual reserves: a quote reserve denominated in the peg, and a base reserve of the coin itself. Their product is held constant.
Buying takes base out of the reserve, so base falls and quote rises — and because k cannot move, the price rises with every token that leaves. Selling does the exact reverse. Nobody sets the price. Arithmetic does.
Each lane is seeded differently on purpose. The virtual base reserve decides how violently the price accelerates: the $LAUNCH and equity lanes are seeded tight and move hard, USDC is seeded loose and moves least. A lane is not a label on the same curve — it is a different curve.
A round trip always returns less than went in. The coin's fee comes off the way in and off the way out again. Your own buy also moved the price — but on a constant product curve your sell moves it back by exactly as much, so the impact nets out and the fee does not. The table below solves that rather than asserting it, and it is why the round trip is the same number in a violent lane and a calm one.
Every readout to the right is produced by buy(), sell() and state() — the functions the trade ticket calls. There is no separate "docs maths" to fall out of sync.
Read the last two columns together. The round trip column is the same -1.99% in every lane and that is not a rounding artifact — on a constant product curve the price your buy moved is handed straight back by your sell, so all that survives is that coin's fee charged twice. What genuinely differs is the column before it: the tighter lanes hand you fewer tokens for the same money because you paid more over spot to get them. Then the peg moves and none of that mattered: a 5% drop in the quote asset costs about 2.5× what the whole round trip did. The USDC lane is the only one with nothing in that column, which is the entire argument for it.
The fee ladder
Every fill pays one fee, and that fee is cut into fixed slices. The slices are set in code and sum to the chosen rate at every rung.
TABLE on a $250.00 trade, each side $2.50 1.00% of notional
The fee is a band, not a constant. Whoever deploys a coin picks its rung once, in 0.25% steps, from 0.25% to 2.00%. Press a key and the whole table below re-solves: every slice scales together, so the ratio between them never moves. 2.00% is a hard ceiling enforced inside the fee engine — no launch can exceed it, and the build refuses to run if any rung stops summing.
The split is enforced in code: the build walks every rung of the band and if the 5 slices stop summing to that rung — or if the 2.00% cap stops holding — it throws and this page never renders. That is the only reason you can trust the table above.
The slice is spent as a market buy of $LAUNCH, at whatever the book asks at that moment. It is a bid funded by volume, not a distribution and not a claim on anything. It is not a yield and it is not a guarantee — when volume stops, the bid stops with it.
Every figure in this block is ILLUSTRATIVE and derived from one seeded volume number. Halve the volume and every number here halves with it.
Graduation
What happens the moment a curve completes: the curve stops, liquidity migrates, and the lock starts. It is a threshold, not a milestone anyone chooses.
A locked pool is not a floor and nothing here promises a coin survives its own graduation. 3 coins in this ILLUSTRATIVE seed set have graduated, carrying $5.27M of combined cap between them — a survivorship sample, not a hit rate. The ones that died are not on the list, which is exactly why a list like this proves nothing.
The LP forwarder
Burning LP is permanent but earns nothing. Locking it earns but comes back. This does both at once, and here is exactly how.
Every pad has to answer one question at graduation: who holds the migrated LP? There are two usual answers and both of them give something away.
Burn it and the pool can never be pulled — but the fees that pool earns accrue to nobody for the rest of its life. The largest recurring revenue line in the whole product is set on fire to buy trust.
Lock it and the fees stay claimable — but the principal is only permanent until the timer runs out. That is not permanence, that is a deadline.
The third answer. The LP is transferred to an immutable contract that has no withdraw function at all. Not a timelock, not a delay, not a multisig — there is no code path that moves the position out, so nobody can pull it in any year, ever. The permanence is a property of the bytecode, exactly as it is with burning, and it is verifiable the same way: by reading the contract.
But the position is still owned, so what it earns is still claimable. The contract exposes one external function, collect(), callable by anyone, which sweeps the accrued pool fees straight into the same $LAUNCH buyback the trade fee funds — split 50.00% burn, 50.00% stakers, no discretion in between.
Every graduation stops being a one-off. Today a graduation pays one 1.50% slice of migrated liquidity. Under the forwarder it also becomes a permanent stream, and streams accumulate: graduated pools keep trading long after curve volume has rolled over, which is the half of the bid that does not die in a bear.
The pool inherits the coin's own fee rung, so this adds no new dial — a 2.00% coin forwards twice what a 1.00% coin does per unit of volume. It is not a yield and nothing is owed. No trading in the pool means nothing to sweep, and the forwarder sits there earning nothing at all.
The one seeded input is the 55% turnover — ILLUSTRATIVE. Everything else runs through the same fee engine the ticket charges with. Halve the turnover and every figure here halves.
That is $1,602 a day of $LAUNCH bought by pools that have already graduated — before a single new coin trades. Under a burn it is $0. This is a shape, not a projection: it holds only while those pools keep trading, and none of it is promised to anyone.
The LP goes to a dead address. Nobody can ever pull it, and nobody can ever claim a basis point of what it earns either. The trust is real and the revenue is set on fire with it.
The LP sits in a timelock. Fees are claimable the whole time, which is the point — but on day 365 the timer ends and the position can be pulled. The trust has a date on it.
The LP is held by an immutable contract with no withdraw function. There is no code path out, so permanence is a property of the bytecode — the same guarantee burning gives. The one function it does expose sweeps the pool fees into the $LAUNCH buyback.
Read the middle column honestly: a 365-day lock and the forwarder earn the same $228.80 a day. The difference is not the revenue, it is what happens on day 366 and who the revenue belongs to. The 365-day figure elsewhere in these docs is a timelock on the forwarder's routing parameters — the principal is not on a timer at all, because there is nothing to time when there is no withdraw.
The LAUNCH rules
A short list of what the protocol fixes in code and what the person deploying a coin still gets to pick. Everything else is presentation.
The fee band, worked
The same three questions at the floor, the default and the ceiling. Every figure below is splitOf() and bpsOf() — the functions the ticket charges with — run at that rung.
After graduation the pool inherits this rung, so a 0.25% coin forwards $20.9K a year into the buyback at the illustrative pool turnover — while volume lasts.
After graduation the pool inherits this rung, so a 1.00% coin forwards $83.5K a year into the buyback at the illustrative pool turnover — while volume lasts.
After graduation the pool inherits this rung, so a 2.00% coin forwards $167.0K a year into the buyback at the illustrative pool turnover — while volume lasts.
The presets
A preset is a bundle of launch constraints, picked once at deploy and disclosed on every card the coin ever appears on. It constrains the creator. It does not protect the price, and the loosest one is deliberately still allowed.
You take nothing at deploy. Every holder, including you, buys off the same curve at the same price.
A small opening buy, locked and released daily over a month. Anti-snipe holds the first blocks open.
No lock, no cap, no anti-snipe. The creator can sell in the same block you buy, and the badge says so.
Where it executes
Which chain the curve actually settles on, what the pad does off-chain, and where the line between the two sits.
We run exactly one bonding curve, and it lives on Robinhood Chain. That is the whole integration. When a coin on this pad prices, fills, charges a fee and graduates, it is src/curve.mjs and src/fees.mjs doing it against an Robinhood Chain pair — the same two engines every figure in the six chapters above came out of.
Every other chain on this site is presentation. The chain rail on the terminal, the chain tags on your bags and the multi-chain folds in the portfolio are an ILLUSTRATIVE aggregated-router view: a quote drawn to show what a route would look like against third-party liquidity. We do not run a curve there, we are not integrated with those venues, we hold no inventory on them and we route nothing to them.
Nothing on this build executes anywhere. Not on Robinhood Chain, not on the 5 router-quoted chains, not on any venue. There is no order, no fill, no settlement and no custody behind any button on this site. The ticket solves arithmetic and prints it.
If you find any wording anywhere on this site that reads as though we execute, settle, custody or route on a chain other than Robinhood Chain, it is wrong and it is a bug — the intended claim is the one on this page and nothing stronger.
Both rows end the same way: no order is executed anywhere. The badge says what a number is drawn from, never what was traded.
The curve, the fee split and graduation all run here. Even so, this build is a design review: nothing is executed on Robinhood Chain either.
Shown for routing context only. ILLUSTRATIVE — we are not integrated with SOL liquidity and no order is executed there.
Shown for routing context only. ILLUSTRATIVE — we are not integrated with ETH liquidity and no order is executed there.
Shown for routing context only. ILLUSTRATIVE — we are not integrated with BASE liquidity and no order is executed there.
Shown for routing context only. ILLUSTRATIVE — we are not integrated with BSC liquidity and no order is executed there.
Shown for routing context only. ILLUSTRATIVE — we are not integrated with TRON liquidity and no order is executed there.
6 chains are named across this build and 1 of them carries a curve. The gas prices, block times and native asset prices used to draw the router rows are ILLUSTRATIVE reference figures, not a live gas read, and a router quote is not a fill, not a guarantee of a fill, and not an offer to arrange one.
What this does not do
The limits, stated at the same weight as everything above. Read this part slowly.