Appearance
Token Launchpad
The Token Launchpad at chaindaddy.io/_launch lets you launch a token in one step — no upfront liquidity, liquidity locked by design, and a free verified token page on chaindaddy.io. This page explains each option on the launch form; every info tip on that form links to the section here that covers it.
Launching is not the only way in. If you already have a deployed token, see Claim an Existing Token; if you want the advanced two-sided flow with your own liquidity, see Create a Token.
What the launchpad is
A one-page way to launch a new token with liquidity that is locked at launch and a free verified token page. The pool's trading fees are recorded to the addresses set when it is created, and by default the largest share of them is yours — see Fee routing.
$20 once or 1% of trades
There are two ways to get a new token onto Chain Daddy, and the Launch New Token drawer asks which one you want before it asks anything else. They are different products, not two prices for the same thing.
| $20 one-time fee | 1% on trades | |
|---|---|---|
| Cost to launch | $15 + $5 per chain, at checkout | Nothing. You pay gas — and on some chains and sign-in methods we cover that too (gasless launches) |
| Ethereum | Priced live against L1 gas, 1x–8x the standard price (why) | No launch fee — but you pay L1 gas yourself; Ethereum is the one launch chain the operator does not cover |
| Two or more chains | 10% off every chain (bundles) | Free either way |
| Our share of your trading | None, ever | A share of the pool's swap fee — see the split |
| You supply liquidity | Yes, afterwards — add a pool with your own capital | No. The pool is created for you, single-sided and locked by design |
| Chains | Every supported chain | Robinhood, Base, Ethereum and Solana (coverage) |
| Where you finish | Checkout, then the token creation wizard | The launch form at chaindaddy.io/_launch |
Both give you the same verified token page and the same registry listing. Picking the fee-stream option in the drawer carries the ticker and chains you already chose into the launch form, so nothing is retyped.
What the 1% actually is
The 1% is the pool's swap fee, paid by traders — not a fee we charge you. It is the standard 1% fee tier the pool is created at, and an EVM launch can lower it to 0.3% in Advanced.
Two things make a single percentage a poor summary of what a trade actually pays, and both are properties of the engine your chain runs rather than of the price:
- On a chain with two fee streams the tier is charged twice — once by the pool and once by its hook. The rate you pick is what a trade pays on each leg, not across both.
- A Protected open launch does not start at the tier. On the decaying-fee mechanism trading opens far above it and settles down to it over about ten minutes, so the tier is where the fee ends up rather than where it begins.
The pool's own swap fee is divided by share, fixed when the pool is created. You are the largest share of it:
| You keep | Chain Daddy | Underlying protocol | |
|---|---|---|---|
| EVM (Robinhood, Base, Ethereum) | 75% | 20% | 5% (Doppler's airlock floor) |
| EVM on PRO and above | 90% | 5% | 5% |
| Solana | 80% | 20% | 20% (Meteora, taken first) |
| Solana on PRO and above | 95% | 5% | 20% (Meteora, taken first) |
The Solana rows split a smaller pot. Meteora's bonding curve takes a fixed 20% of the pool fee before anything else happens, so the percentages on those rows are shares of the 80% that remains — not of the whole fee, the way the EVM rows are.
So at the default 1% fee tier, $1,000 of trading collects about $10 as the pool's own swap fee, of which $7.50 is recorded to you on the free plan and $9 on PRO. On Solana the same trade leaves $8 to split after Meteora's cut, so $6.40 is recorded to you free and $7.60 on PRO. The headline percentage is higher on Solana and the money is lower — that is Meteora's skim, not our cut, which is 20% (5% on PRO) on both venues.
On a two-stream chain that arithmetic covers one of the two streams. The hook's stream is charged separately, at the same tier, and settles at the single address the pool records — yours unless you sent it somewhere else. Two streams is the section that explains why it works differently, and it is worth reading before you touch Fee routing.
You claim what has accrued from My Tokens — see The trading-fee stream.
Your plan is read when the pool is created, and the split is fixed from then on. Subscribing after you launch does not change a token you already launched — it applies to your next one. That is not a policy choice: the split is written into the pool at creation and cannot be edited afterwards, on either venue.
Which one to pick
Pay once if you already have liquidity to add, want a chain the launchpad does not reach yet, or simply want no ongoing arrangement with us. Take the fee-stream option if you have no capital to put up, want the pool created and locked for you, and would rather take a share of the trading than pay up front.
You are not locked in either way: a token launched on the fee-stream path still gets its free verified page, and a token created on the paid path can add liquidity on its own terms later.
Where the fees go: two streams
This is the thing to understand before you choose anything in Fee routing.
On the chains that run the decaying-fee engine — Robinhood today; the launch form names the engine for each chain you select — a launched pool does not have one fee stream. It has two, held by two different contracts, divided in two different ways. Every routing choice below means something different to each.
Picture a single trade. A buyer sends ETH in; your token comes out.
Stream one — the pool's own swap fee. Taken off the side going in. It is held by the pool's initializer contract, which records a share per address: yours, Chain Daddy's, and the underlying protocol's. Each of those is paid separately, on its own transaction, to whoever sends it. This is the stream the split table describes, and it is the one a co-creator split divides.
Stream two — the hook's fee. Taken off the side coming out. It is held by the pool's hook contract, which records exactly one address for the whole thing. Every bucket it divides its fees into — the buyback, and the bucket named for the beneficiaries — settles at that one address when it is claimed. There is no share, no list, and no second name on it.
Side by side:
| Stream one — the pool's own swap fee | Stream two — the hook's fee | |
|---|---|---|
| Taken from | the side of the trade going in | the side coming out |
| Held by | the pool's initializer contract | the pool's hook contract |
| Divided by | a share per address | nothing — one address holds all of it |
| Paid to | each address separately, on its own claim | the one address the pool recorded |
| A split reaches it | yes, exactly as typed | no |
| A burn reaches it | no | yes, all of it |
| Where you claim it | My Tokens | My Tokens |
Three consequences follow, and they are the reason this section exists.
A split cannot reach the second stream. Percentages you type into Share the fees divide the first stream exactly as written. They do not touch the second, because there is nowhere on that contract to record them. A partner shown "20%" is being shown a number that is right about one stream and silent about the other.
A burn takes the second stream whole. Picking the burn destination sets that one address to the burn address — so the whole hook stream settles there, not only the boost share you chose. See Where the buybacks go.
The first stream survives a burn. Your recorded share of the pool's own swap fee is untouched by anything in the boost controls. You keep it, and you claim it from My Tokens like any other launch.
On Solana there is one stream. The Solana launchpad runs on Meteora's bonding curve, which has no such hook, so nothing in this section applies there.
Launch mode: zero capital vs dev-buy
Two mutually exclusive ways to launch. Zero capital (the default) means you spend nothing — the pool is created single-sided and locked by design. Dev-buy means you buy a chunk of your own token at launch, seeding it with your own capital instead of leaving the first buy to the market.
A dev-buy is a second transaction after the launch, so it is wallet launches only. It is also paid in the chain's native token, which cannot buy into a pool quoted in another asset — so it is offered only on launches quoted against the chain's wrapped native. Pick the dollar stablecoin and the dev-buy option is not part of that launch; the API refuses the same combination with a message saying so rather than failing at signing. Either way the liquidity position itself is locked — see Lock, burn, or keep your LP tokens for what that means and how it is proven on-chain.
Chains
The chain (or chains) to launch on. Selecting more than one launches the same token symbol on each, and the resulting verified token pages are linked into one multi-chain registration.
The chain also decides which quote assets you can pick from — every launch chain offers its wrapped native token, and most also offer that chain's canonical dollar stablecoin. The launch form shows the options for the chains you have selected.
Not every chain can run a one-step launch — see Per-chain coverage for what each one supports, and Which chain should I choose? for how to pick.
Token name
The full, human-readable name of your token (for example, "Chain Daddy"). Shown on the token page and in wallets. You can edit it later from Token Management.
Ticker symbol
The short trading symbol for your token (for example, "CDADDY"). Registrations are first-claim-wins per symbol, chain, and token — once a valid registration exists it is not displaced by a later claimant. A symbol can free up if its registration lapses; see Reclaiming an expired slot.
Image
The token's logo. Shown on the token page, in wallets, and in listings. Square looks best. Once you own the page you can change it, along with the rest of the look, from the style editor.
Supply
The total number of tokens minted at launch.
None of the supply comes to you. The permanently-locked pool keeps what it absorbs and the rest is sent to a burn address as the token is created; on one Base launch measured afterwards that worked out close to half and half, with nothing to the creator. How it divides depends on the shape of the pool's book. There is no creator allocation on this path — your side of the launch is the fee stream.
See How much can you add? for how supply and decimals interact with a pool.
Pool trading fee
The swap fee tier of the liquidity pool — the share of a trade collected as fees. Part of it is recorded to you and the rest to the launch's other beneficiaries, for the life of the token.
On a chain with two fee streams the pool and its hook each charge this rate, so the tier is what a trade pays on each leg rather than across both. On a Protected open launch it is also where the fee settles rather than where it starts.
Where those fees go — the address, any split, and Boost — is set in Fee routing.
Starting market cap
The market cap your token opens at, in US dollars — the value of the whole supply at the first trade. Pick one of the offered figures or enter your own. The pool's range reaches about 10x the opening market cap, so buying walks the price up toward that ceiling.
The figure is entered in US dollars whichever quote asset you pick, and it is converted into that asset at the rate quoted when you launch, so the opening market cap is approximate rather than exact. For what moves the price after launch, see What sets the price?.
What your launch is paired against
Every pool trades one asset against another. Your token is one side. The quote asset is the other — what buyers spend, what the opening market cap is converted into, and what your side of the trading-fee stream arrives in.
Two classes of asset are offered and no others — the chain's wrapped native token, and the canonical dollar stablecoin that chain carries. On every launch chain today that works out to two options, and the launch form shows the ones your selected chains carry:
| Chain | Quote assets |
|---|---|
| Ethereum | ETH (wrapped) · USDC |
| Base | ETH (wrapped) · USDC |
| Base Sepolia (testnet) | ETH (wrapped) · USDC |
| Robinhood Chain | ETH (wrapped) · USDG |
The chain's wrapped native token is the default, and it is available on every launch chain. The canonical dollar stablecoin is the second option, offered wherever that chain has one. A chain added later arrives with whichever of the two classes it actually carries — the set is read per chain, not assumed. A Solana launch runs on a different venue and takes no quote-asset choice.
There is no field for typing an address, on the form or in the API. Both options are read from the chain's own entry in Chain Daddy's chain registry rather than from a list of token addresses, so the picker cannot be pointed at an arbitrary third-party token — which is also why a launch cannot be paired against a tokenised equity, or anything else that happens to trade on the same chain. This is a fixed technical restriction on what the launch tools will build, not a review or an approval of anything.
Launching on several chains at once: you pick the asset once, and it resolves to that chain's own address on each. An asset only some of your selected chains offer is still shown, with the chains it is offered on written on it — pick it anyway and the launch is refused for the chains that cannot run it, so drop those chains or pick something all of them carry.
What picking the stablecoin changes
Read all three before you pick it:
- Your fee stream arrives in that asset. A pool's fees accrue in the two assets it trades, so the side that would have been ETH on a wrapped-native launch is the stablecoin instead. How you claim, and what share you keep, are unchanged — see The trading-fee stream.
- Your opening market cap is converted into it. Same dollar figure, same form, different asset on the other side of the conversion.
- Dev-buy is not offered. The dev-buy leg pays with the chain's native token, which cannot buy into a pool quoted in another asset. Picking the stablecoin leaves the zero-capital launch, which is the default anyway.
Trading works either way: the buy and sell buttons on your token page reach a pool quoted against the stablecoin, and a buy there is paid in that stablecoin rather than in the chain's coin — so it takes a token approval first, the same way selling does. Your token page derives its price and market cap from that same route, in that asset.
Everything else is the same either way: the fee split, the fee routing options including Boost and its burn destination, the protected open mechanism, and the per-wallet cap.
The pool records its quote asset when it is created, and this form gives you no way to change it afterwards — so make the choice deliberately. Chain Daddy makes no claim about how a pool quoted against either asset will trade.
How trading opens: Standard vs Protected open
Standard creates a permanently-locked pool with a per-wallet cap. It is tradeable from the first block, at a fixed opening price.
Protected open defends the opening against bots. What that means depends on the chain, because the two mechanisms are genuinely different — the launch form names the one your selected chains will run, with its real timings, before you launch:
- Decaying fee (the multicurve engine). Trading opens at a punitive fee — 80% today — that falls to your pool's standing fee over about ten minutes. A bot buying in the first seconds pays most of its trade to the launch rather than getting a cheap entry. There is no auction and no raise target, and your pool is tradeable immediately. That opening premium is charged by the hook, so on a launch that chose Burn it goes to the burn address along with the rest of that stream.
- Dutch auction (the classic engine). Your token runs a timed auction first: the price starts high and falls until buyers step in, so there is no fixed opening price to front-run. The auction must raise a minimum amount — 0.1 ETH today — inside its window to graduate to a permanent pool. A launch that does not clear that target does not get its permanent pool, so this mechanism is an explicit opt-in and is never preselected for you.
Protected open is offered only where every chain you have selected supports it (see Per-chain coverage). The per-wallet cap applies to both mechanisms. Launching this way replaces the manual open-trading step of the advanced flow.
Fee routing
One section of the launch form, shut by default, holding every choice about where your token's trading fees end up: the address that collects them, any split with other people, and Boost.
Everything in it is set when the token is created, and the form gives you no way to change it afterwards. The contracts that hold and route these fees have no function to move a destination once a pool exists, and neither of them is upgradeable. A launch that leaves this section alone gets the ordinary arrangement — fees to the launching wallet, no split, Boost off — and is never asked to confirm anything. The two choices that cost you something, a burn and the liquidity slice, ask you to tick what they mean before the token can be built.
Read Where the fees go: two streams first. Every control here behaves differently against each stream, and which of them a choice reaches is the part that is easy to get wrong.
Fee address
The address the pool records for your fees. Defaults to the wallet that launches.
On a chain with two streams the pool records this one address for both of them — your share of the pool's own swap fee, and the hook's own stream.
A burn overrides it for the second one. If you point the buybacks at the burn address, the hook's stream is fixed there and this field does not move it; what this field still does is collect your share of the pool's own swap fee. Both were asked for, and the irreversible one wins.
Because this address collects for the life of the token, a Safe multisig is worth considering over a hot wallet.
Share the fees
Optional. Name other addresses and the percentage each takes, and the pool records their shares alongside yours when it is created.
A split divides one of the two streams. It divides the pool's own swap fee, exactly as typed, and each named address claims its own share on its own transaction. The hook's stream is recorded against a single address, so no split reaches it — which is why a percentage shown to a partner is right about one stream and silent about the other.
For the same reason, Boost is refused on a launch with named beneficiaries, and on a collab launch made under an agreed split: the buyback pays one address, so turning it on would route a share none of the named parties have a part of and make every percentage on the form smaller than the number they were shown. The form refuses the combination rather than quietly re-cutting it.
Boost your token
Optionally point a share of your token's own trading fees at buying it back.
You pick the share of the trading fees that gets routed, then say where the bought tokens go and how much of that share is added to the pool as liquidity instead. Off routes none of it — the whole fee keeps streaming to the launch's beneficiaries, of which you are one.
Nothing is preselected. Boost starts Off. The offered shares are set by the operator rather than fixed in the form, so the figures on the launch form are always the live ones, and the form works your choice out as arithmetic against $100 of collected pool fees — the same share, ending in a different place, with no assumption about how much your token trades.
The buyback happens inside the trade. The pool's hook contract does the buying, in the same transaction as the swap, trade by trade, once the accumulated fee clears a dust minimum. Nobody has to press anything, and the tokens go from the hook to the destination — they do not pass through Chain Daddy.
It is best-effort, not every trade. Below that dust minimum nothing is routed and the amount is carried into a later trade rather than lost. The hook's own swap can also decline to run — if its simulation fails, or if it would come back with nothing. Treat it as trade by trade once the fee clears the minimum, not as a thing that fires on every single swap.
When routing starts depends on the engine. On a decaying-fee chain the hook is configured at launch and the pool never migrates, so routing is live from the first trade. On a Dutch-auction chain the configuration rides the migration instead, so routing starts once the launch graduates — and a launch that does not raise its minimum never graduates, so no buyback happens at all. The launch form states which, for each chain you selected.
The contracts are not ours, and their owner can switch this off. The pool and its hook are Doppler/Whetstone contracts. We set their configuration when your token is created; the contracts themselves belong to that deployment, and the account that owns it — not Chain Daddy — can disable the hook's per-swap step for a whole chain. That stops the buybacks on every pool there, including yours, without touching anything we wrote: your pool would keep its configuration and stop routing. We can tell you exactly what the mechanism does. We are not in a position to promise it keeps running, and nothing here should be read as promising a particular outcome for a token.
Boost runs on the fee-rehypothecation engine, so a boosted launch always uses Protected open, never Standard. It is offered on Robinhood, Base and Ethereum today, and shown only when every selected chain supports it.
Where the buybacks go
Two places, and only two. The form and the API take a word here, not an address, and refuse anything that is not one of the two — so there is no third destination this control can name:
- Your fee address — the Fee address you set, or the wallet that launched if you left it blank.
- The burn address —
0x000000000000000000000000000000000000dEaD, an address nobody controls.
They are a choice between, not a mix. The pool records one address, so there is no configuration in which some of it goes to each.
Burning is a choice about your own fees, and it lowers what you can claim. It is also larger than the share you set. Because the pool records that one address for the hook's whole stream, picking Burn sends all of that stream to the burn address when it is claimed — the buyback and the bucket named for the beneficiaries alike — not only the boost share. On a Protected open launch that includes the opening fee premium, which for a young token is usually the largest part of what it has collected so far.
Your share of the pool's own swap fee is a separate stream that a burn does not touch. You keep it, and you claim it under My Tokens like any other launch.
Tokens sent to the burn address leave circulation, but the token contract's total-supply figure does not change — an explorer may keep showing the number you launched with. No holder receives anything as a result of a burn, and a burn is not a statement about what the token will be worth. See the Terms for the full disclosure.
It is permanent. The destination is written into the pool as the token is created. The contract has no function to change it afterwards, and it is not upgradeable. Pick it before you launch or not at all.
Adding part of the boost to liquidity
The boost share does not have to go entirely into buybacks. A quarter, a half, three quarters or all of it can be added to the pool as liquidity instead. That split is of the boost share you picked, not of the whole fee.
That slice does not come back to you. The position is held by the hook contract itself, across the full price range, and the contract has no function to remove it. It is given to the pool — not fees held somewhere on your behalf, and not something you can claim later. On a trade where the pool cannot be balanced for it, the slice stays with the beneficiary share instead.
It is offered only on chains running the decaying-fee engine, and refused elsewhere. "All of it" and the burn address cannot both be picked: sending the whole share to liquidity leaves nothing to buy back and send to the burn address, so the form disables whichever you reach for second and says why.
Description
A short description of your token, shown on its verified token page. Editable later from Token Management.
Banner
A wide banner image (about 3:1) for the top of your verified token page. It, the background, and the rest of the page's look are editable later — see Token Page Themes.
Anthem
An optional song for your token page. Upload an audio file (MP3, M4A, WAV or OGG, under 10 MB and under 5 minutes — both limits are enforced, so a long track is refused even well inside the size cap) and the page is built with an audio player already on it, loaded with your track — you do not have to add or configure the widget yourself.
The player is part of the page's layout, so it appears when your free verified token page is claimed. Where the launch form claims that page for you — EVM chains, via the switch above — the anthem field asks you to turn the switch on first, and your song is there the moment the page exists. Where the page is claimed afterwards instead, from the token page (Solana), your track is recorded with the launch and the player is built in whenever you claim, even from another device or a later session.
Afterwards the player behaves like any other widget: move or resize it, swap the track, turn looping and play-on-start on or off, or remove it entirely from Token Management. Your track is also saved as the page's anthem metadata, so it survives publishing the page on-chain.
Want more than audio? Custom video backgrounds and custom CSS are PRO features; third-party apps and watermark removal are PRO+.
Website, X & Telegram links
Optional links to your project's website and social accounts, shown on the token page. Adding a link is not the same as proving you own the account: to get a verified badge next to it, see Social Verification.
Free verified token page
Every launch is eligible for a free verified token page on chaindaddy.io — proof of ownership, a public profile, and the registry listing — at no extra cost. That is the same page a registration normally buys you; see What you get for the full list.
Registering with the launch is optional. If you skip it, you can claim the page for free later from the wallet that launched.
Gasless launches
Social and fiat launches are broadcast for you (operator-broadcast), and where enabled a small gas top-up lets a brand-new embedded wallet complete its token-page registration without holding gas first. The launch form marks which of your selected chains the operator can cover. Where it cannot, you pay the chain's normal fee — see Gas estimates.
The trading-fee stream
Liquidity is locked by design; the fees it collects are not. They accrue continuously and you claim what has accrued whenever you want to — nothing is claimed for you, and there is no schedule.
Fees arrive in the assets the pool trades, which means your token on one side and the quote asset you picked on the other. Launch against a dollar stablecoin and the side that would have been ETH is that stablecoin instead. Nothing else about claiming changes — same screens, same buttons, same shares. What the unit does change is the dollar figure shown next to a row, which is derived from a price for that asset like any other.
Claim from My Tokens, at chaindaddy.io/_tokens. It lists every token you launched and every fee stream that token has. A launch on a two-stream chain shows a row for each, with its own claim button: the two sit on different contracts and are collected by different calls, so they are claimed separately. A launch that chose Burn still shows both — the hook stream keeps accruing and keeps reporting what it accrued; what the burn fixed is where it settles when the claim is sent.
The figure shown for the pool's own swap fee is a floor rather than an exact amount. That contract counts only what it has already pulled in, and the only thing that pulls is the claim itself, so a claim collects at least that much and often more.
A Solana launch is claimed from its token page instead, not from My Tokens — it runs on a different venue with one fee stream, and the claim lives on the page for that token.
The split is set by your plan when the pool is created. On EVM you keep 75% of the pool's own trading fee on the free plan and 90% on PRO and above; the remainder covers the underlying protocol's 5% and Chain Daddy's cut. On Solana there is no underlying-protocol floor, so the same cut leaves you 80% free and 95% on PRO — of the 80% of the fee that survives Meteora's own 20%. The Solana figure the launch form shows is the cut frozen into that cluster's launch config when it was created, which is the cut every Solana launch on it actually pays, rather than the EVM setting; on the EVM chains the figures above are the configured ones.
Per-chain coverage
Which chains support a one-step launch, and which route to the advanced two-sided flow. The launch form lists what each chain you have selected can actually run — its launch engine, which quote assets it offers, whether Protected open and Boost are available, the per-wallet cap, and whether the operator can cover registration gas. Coverage expands over time.
Quote-asset coverage is the one that varies most simply: the wrapped native token is everywhere, and the dollar stablecoin is wherever that chain has a canonical one. It is read per chain rather than assumed, so a chain added later arrives with whichever of the two it actually carries — and a launch quoted against the stablecoin is not reachable by Chain Daddy's own buy and sell buttons today, which is worth weighing per chain along with everything else on this list.
The launch engine is the thing to read there rather than assume: it decides whether your pool has one fee stream or two, and whether a boosted launch starts routing at the first trade or only at graduation. It is probed per launch against what is actually deployed on the chain, so it can change without the product changing.
For the chains Chain Daddy supports generally — beyond the launchpad — see Supported Chains.
Linked multi-chain registration
Launching the same symbol on multiple chains from one wallet automatically links the token pages into a single multi-chain registration — no extra step, and no extra cost. See Linking Is Automatic for how the peer group works and One registration per chain per wallet for the limit.
After you launch
Your token page is a live product surface, not a receipt:
- My Tokens — every token you launched, and the fee streams you claim from
- Token Page Themes — colors, backgrounds, layouts, featured links
- Airdrops — allowlist or first-come-first-served distributions
- Listing Export — submit to CoinMarketCap, CoinGecko and DEX listings
- Holder Notifications — reach holders on Discord, Telegram and mobile push
- Token Health & Anti-Squatting — keeping your registration active
- Plans — what each tier unlocks, including the 90% fee keep