Deploy a token
This guide walks through deploying a token with Launch Lab. It takes a few minutes. You'll need a wallet that can sign on the network you choose, holding enough of that network's coin (for example BESC on BESC Hyperchain) to pay the deployment fee.
1. Choose a template
- Open Settings → Advanced → Launch Lab (turn on Developer mode first).
- On Deploy, tap Start a launch, or scroll to Choose a template. Filter between Tokens and Bridge wrappers.
- Tap a template to see its contract, compiler, setup fields, what it supports and its safety limits. See Token templates for the full comparison.
- Make sure the wallet shown under Pick a wallet to sign the deploy is the one that should own the token.
- Tap Deploy Now, or Save Setup to save the basics and finish later.
The deploy screen has up to four steps: Identity → Launch → Tokenomics → Review. Tokenomics only appears for templates with fees, burn, swapback or rewards. Wrapped Bridge uses Identity → Bridge → Review.
2. Identity
- Launch Presets: start from a ready-made setup. Every field stays editable.
- Token name and Symbol (keep the symbol short)
- Initial supply: minted to you at deployment
- Decimals: 0 to 36 (default 9; 18 for wrapped tokens)
- Deployment chain
- Setup label: your own name for this launch inside Launch Lab
3. Launch
Routing
- Treasury address: defaults to your wallet.
- DEX router: Launch Lab loads the default V2 router for the chosen network (DEX Context shows the router, factory and wrapped coin so you can confirm them). It's required for templates with swapback, and whenever you create a pair.
Trading
- Create native pair: creates the token's trading pair against the network's wrapped coin (for example WBESC) during deployment, so it's ready for liquidity.
- Trading enabled on launch: leave off to open trading yourself later, after liquidity is in.
- Wallet and tx limits enabled, with Max tx bps and Max wallet bps (minimum 10 bps, which is 0.1% of supply).
Pair creation needs the right router
Pair creation runs inside the deployment. If the router isn't the live V2 router for that network, the deployment fails before a transaction is created, and no fee is charged.
Fee receivers
Where fee proceeds go: Liquidity, Marketing and Team receivers (default: your wallet) and the Burn receiver (default 0x…dEaD).
Launch protection
Opening-block defenses against sniper bots. Protection starts the moment trading goes live and lasts for the window you set.
| Setting | What it does | Limit |
|---|---|---|
| Protection blocks | How long protection lasts after trading opens | up to 2,400 blocks |
| One transfer per block | Each wallet can only buy, sell or transfer once per block | |
| Blacklist window blocks | How long, after trading opens, you can block sniper wallets | no longer than the protection window |
| Cooldown seconds | Minimum time between one wallet's buys or sells | up to 600 s |
| Max buy bps / Max sell bps | Largest single buy or sell during protection, as a share of supply | at least 10 bps if used |
| Penalty tax bps | Extra tax on buys and sells during protection, sent to the marketing receiver | up to 4,000 bps; needs swapback |
| Auto-lift wallet and tx limits | Turns off max tx and max wallet automatically when protection ends |
Addresses you mark fee-exempt or limit-exempt (such as your router, pair or treasury) aren't affected. Once the blacklist window closes, no new wallets can be blocked.
4. Tokenomics
Depending on the template:
- Burn Schedule: burn on buys, sells and wallet-to-wallet transfers.
- Fee Matrix: split buy, sell and (where allowed) transfer fees across liquidity, marketing, team, rewards and burn. "Launch" templates keep wallet-to-wallet transfers tax-free.
- Swapback: Threshold bps (when fee swaps start) and Max swap bps (most that swaps at once), each up to 2% of supply. Once this starts live, it stays on.
- Rewards: Reward token address (defaults to the network's wrapped coin), Min period seconds (how often a holder can be paid), Distributor gas, and Min distribution raw units (use the token's smallest units, not the rounded display amount).
Launch Lab checks your settings as you go, and explains anything that needs fixing before you can continue (Deployment needs one more fix). For example, liquidity, marketing, team or rewards fees need swapback on, and rewards need a reward token.
5. Review and deploy
Review Deployment is one last look before your wallet asks you to confirm:
- the template, preset and token details
- Trading / Limits, Launch protection, Fee Totals, Routing, Swapback and Rewards
- plain-English notes, for example Trading stays off until you turn it on, or Sell tax is in the high range for a public launch
- Network Fee: a live estimate of gas limit, gas price and total fee. Keep it, tap Refresh, or set your own Gas limit and Gas price (gwei).
- Before you deploy: Deployment is permanent: the contract can't be edited or removed, and the network fee is paid from your wallet.
Tap Deploy To (for example Deploy To BESC) and approve. Your wallet signs and sends the deployment, then Launch Lab waits for it to confirm.
When it's done you'll see Contract Deployed: Your contract is live on …. The contract appears under Manage → Live Contracts, and Launch Lab immediately sends it for verification.
If the deployment fails
| Message | What to do |
|---|---|
| Not enough … is available to cover deployment gas | Add more of the network's coin to the wallet. |
| Deployment was rejected by … before a transaction hash was created | Usually a wrong router while Create native pair is on. Check the router, or turn pair creation off. Nothing was charged. |
| Launch Lab could not simulate this deployment | Check gas, wallet balance and launch settings, then try again. |
| Contract deployed. Verification queue failed | Your token is live. Tap Verify on its card later. |
Save a setup for later
Save Setup stores the template, network, name, symbol and decimals on your phone under Saved Setups. If you deploy it some other way, open the setup and tap Add Live Contract, then paste the deployed address to manage it here.
