Skip to content
HomeEnter terminal

Launchpads

Seven venues, two chains, at different levels of completeness — and none of them accept a launch from this production build.

This page records how the venues differ so that, when Deploy is enabled, the differences are already written down. It is not a claim that you can launch today. Current submit status is Limitations and Launch.

How to read the table.

Term Meaning
Form lists it The Deploy catalog includes this venue
Not enabled This production build will not submit launch, buy, or sell on it
Intended What the product is built to do when that venue is turned on
Venue Chain In the form Launch / buy / sell in this build Intended shape
pump.fun Solana Yes Not enabled Deepest curve; graduates into its own AMM
Bags Solana Yes Not enabled Creator fees can be routed to a wallet or a social account
LetsBonk Solana Yes Not enabled A configuration on Raydium LaunchLab
Raydium LaunchLab Solana Yes Not enabled Graduates into Raydium
Meteora DBC Solana Yes Not enabled Segmented curve; highest configurability. Launch needs an on-chain config the operator has not created
four.meme BNB Chain Yes Not enabled BNB-native; USD1 pricing
flap.sh BNB Chain Yes Not enabled Customizable token economics (tax, burn, dividends, LP)

Nothing here is a bare checkmark. A checkmark cannot say “the form knows this venue” versus “you can spend into it today.”

For speed and liquidity → pump.fun. Deepest curve, most buyers, most mature graduation path. Usually the default.

To share creator fees → Bags. Recipient can be a wallet, a GitHub name, or an X account.

To design token economics → flap.sh. See below.

For the BNB ecosystem and USD1 pricing → four.meme.

Meteora DBC is the most configurable Solana curve. Launching it requires a configuration account the operator has not created. The product should refuse a buy it cannot price, rather than guess a curve of that shape.

Token economics on the other venues are mostly fixed. flap.sh lets the issuer set behaviour of the token itself.

Buy and sell taxes can differ (each 1%–10%), with an optional expiry and an anti-bot window. Collected tax is split across marketing, burn, holder dividends, and automatic liquidity; the four shares must sum to 100%.

What the form actually exposes today: a single “tax token” switch, with the rest at defaults (3% buy, 10% sell, tax to marketing). A full parameter panel is not in this build. That is a product gap, independent of submit being disabled.

Addresses on flap.sh use a fixed suffix that differs between standard and taxed tokens. When launch is on, the address is determined before send, so a mismatch between the announced address and the wallet prompt is a stop, not a detail.

Solana and BNB Chain are different assets. A “simultaneous” launch, when it exists, is two independent tokens, not a bridge.

That operation is not enabled. Ticking two chains in a draft does not create two tokens.

When several venues are selected, some settings apply to only a subset. The form should name which settings and why, before anyone could submit. A generic “not supported on some platforms” is not an explanation.