Create Token
Deploy a plain token and its liquidity pool, with no launchpad involved.
Create Token is the launchpad-free path. It deploys a token contract you configure and pairs it on a normal DEX. There is no curve, no graduation and no platform in the middle: just a contract and a pool, both yours.
When to use this instead of a launchpad
A launchpad gives you discovery, a price that starts near zero, and a graduation event. It also fixes the supply, the taxes and the fee, and takes a cut of every trade.
Create Token gives you none of the discovery and all of the control: your own supply, your own opening price, your own taxes if you want them, and no third party in the trade path. Use it when the token needs a shape a launchpad will not give it.
Step by step
- Pick a template and fill in the token's identity, supply and any taxes.
- Choose the DEX to pair on, how much supply goes into the pool, and how much coin goes with it. That ratio is the opening price.
- Optionally add buyer wallets, which buy in the same run exactly as a bundle does.
- Run it, as one transaction or split into deploy-then-open.
- Afterwards, decide about burning the LP and renouncing ownership.
Templates
| Template | What it does |
|---|---|
| Standard | A plain ERC-20. No taxes, no limits. |
| Liquidity Generator | A tax that accumulates and is periodically swapped into the pool. |
| Baby | A tax that pays holders a dividend in another token. |
| Buyback Baby | A tax that buys the token back and burns it. |
| Tax Token V2 | Asymmetric buy and sell taxes that can step down over time, with wallet and transaction caps. |
The template list is fixed when the launcher is deployed. A new template means a new launcher, which is why the existing ones keep their addresses.
The opening price
Supply in the pool and coin in the pool set it, and nothing else does. Half the supply against 1 BNB and a tenth of the supply against 1 BNB are very different tokens on day one, and the form prints the resulting price and market cap before you commit.
Two things worth deciding deliberately:
- How much supply goes in. What you keep back is yours to sell later, and everyone can see how much it is.
- How much coin goes in. This is the depth. A thin pool moves on small trades, in both directions.
One transaction or two
One transaction deploys the token, adds liquidity and runs any buys together, so there is no moment when the token exists and the pool does not.
Deploy then open splits it, which lets you look at the contract on the explorer before any liquidity exists. Nothing is tradable in between: there is no pair, so there is nothing to front-run, but the token address is public from the first step.
Caps, if you set them
Tax Token V2 can carry a per-transaction cap and a per-wallet cap. Both are enforced by the token itself and both will refuse your own buys as readily as anyone else's, so the form checks the plan against them before it runs. A wallet cap smaller than the per-wallet share of your bundle is the usual mistake.
Buys made during the opening period pay the opening tax rate, not the settled one, and the estimate uses the opening rate because that is what your bundle will actually pay.
After launching
Two irreversible options, both offered on the page:
- Burn the LP. Sends the liquidity tokens to a dead address. Nobody can pull the liquidity afterwards, including you.
- Renounce ownership. Gives up the owner functions. On a tax template that means the taxes, caps and exemptions are frozen wherever they stand.
Both are permanent. Burn the LP and the liquidity is gone from your control forever. Renounce and no tax, cap or exemption can ever be changed again, including the ones that are currently refusing your own transactions. Test the token's behaviour before either.
Tokens created here are recorded as positions and sell through Tokens like any other, routed to the pair they were paired on.