After you deploy
Once your token is live, Launch Lab guides you through the rest of the launch: verify the code, add liquidity and open trading. Everything happens from Launch Lab → Manage → Live Contracts.
Your contract card
Each contract shows its network, address (tap to copy), verification status, detected features (such as ERC-20, Ownable2Step, Swapback, Rewards), launch progress (for example 3/6 launch steps), and these buttons:
| Button | What it does |
|---|---|
| Run | Built-in contract actions for Launch Lab tokens |
| Verify / Refresh | Sends the source to the explorer, or checks the latest status |
| Explorer | Opens the contract on the network's block explorer |
| Add LP | Opens BESC Swap's liquidity page in the in-app Browser (BESC Hyperchain, BNB Chain and Ethereum) |
| Launch Flow | The guided post-deploy checklist |
| Inspect | Live reads of the contract's state |
| Methods | Call any read or write function from the ABI. See Contract console. |
| Delete | Removes the contract from Launch Lab only; it stays on-chain |
The Launch Flow
Tap Launch Flow for the post-deploy steps. Each step opens the right action for you, and you can mark steps done.
Tokens:
- Submit verification: publish the source on the explorer.
- Approve router: let the DEX router spend your tokens (needed before adding liquidity).
- Add liquidity: opens BESC Swap's liquidity page in the Browser. Pair your token with the network's coin.
- Register pair: tell the contract which address is the trading pair, so buy and sell fees and limits apply. (Pairs created during deployment are already registered.)
- Enable trading: open trading to everyone. If launch protection is on, this starts the protection window.
- Transfer ownership: hand the contract to its long-term owner (optional).
Wrapped Bridge tokens: submit verification, set bridge operator, then transfer ownership.
Add liquidity on the same DEX
Use the same DEX as the router your contract was deployed with, so the pair the contract knows about is the one holding your liquidity. If you add liquidity somewhere else, use Register pair with that pair's address.
Explorer verification
Verification publishes your contract's source code on the block explorer, so buyers can read exactly what it does. Explorers show a green check and a readable Contract tab.
How it works: right after your deployment confirms, Launch Lab asks BESC's service to verify the contract. The service submits the exact template source (as a Solidity standard-JSON input), the compiler version (v0.8.31, EVM paris), the contract name, your constructor settings and an MIT license to the explorer. Because Launch Lab templates are pre-compiled, the bytecode matches exactly.
| Network | Explorer |
|---|---|
| BESC Hyperchain | explorer.beschyperchain.com (Blockscout) |
| Ethereum | Etherscan |
| BNB Chain | BscScan |
On other networks, deployment works but verification isn't automatic. Verify the source on that network's explorer yourself.
Statuses: Verified, Pending (in the explorer's queue; tap Refresh in a moment), Failed, Unknown and Not checked. If the automatic submission didn't go through, tap Verify to send it again. Contract is already verified on the explorer means there's nothing more to do.
Contracts you add yourself
For contracts not deployed from a Launch Lab template, Verify checks whether the explorer already shows verified source. To verify custom code, use the explorer's own verification tool.
Contract actions
Tap Run for the built-in actions. Your wallet signs and pays the network fee. Switch to the owner wallet on the right network first.
Token controls:
| Action | What it does |
|---|---|
| Trading On / Trading Off | Open or pause trading |
| Set Limits | Turn limits on or off and set max tx / max wallet bps |
| Approve Router | Approve the router to spend your tokens (unlimited or a set amount) |
| Pair / LP | Register a pair address as an AMM pair (or unregister it) |
| Fee Exempt | Exclude an address from fees. Useful for router, LP, treasury, bridge, or migration addresses. |
| Tx Limit Exempt / Max Wallet Exempt | Exclude an address from limits |
| Swapback | Change threshold and max swap (templates with swapback) |
| Transfer / Accept / Renounce Ownership | See below |
Bridge controls (Wrapped Bridge): Pause, Unpause, Bridge Access (allow or remove a bridge operator), Mint Wrapped (mint to a recipient with a transfer id: use a 0x-prefixed bytes32 or plain text, which is hashed), plus the ownership actions.
Mint only after the source side
Mint wrapped supply only after you've confirmed the matching deposit on the source chain. A transfer id can only be used once.
Hand off or renounce ownership
- Transfer Ownership starts a two-step handoff. Launch Lab uses Ownable2Step, so the new owner still needs to accept ownership afterward. The new owner opens the contract (in their own Launch Lab, via Add Contract + ABI or the saved template) and runs Accept Ownership. All owner permissions move to them.
- Renounce Ownership removes every owner permission. This is permanent: no wallet will be able to run owner actions on this contract again. Fees, limits and trading stay as they are at that moment, forever.
Inspect
Inspect shows live reads such as name, symbol, decimals, total supply, owner, pending owner, paused, trading enabled, limits active, launch protection active, max transaction and max wallet amounts, LP pair, wrapped coin, origin chain and token, and reward token. Tap Refresh reads to update.