Create a Liquidity Pool on BNB Chain

Choose an exchange and version, supply your BEP-20 address, pair it with BNB or USDC, and enter how much of each to deposit. Those two amounts fix the opening price. One signature builds the pool, funds it, optionally buys in on your behalf, and burns or locks the LP if you asked. It trades from the block it confirms in.

A liquidity pool is a smart contract holding two tokens, and a decentralized exchange prices them from the ratio of tokens in the pool rather than by matching buyers to sellers. When you deposit both assets on a v2 pool you receive LP tokens representing your share of everything inside, and you earn trading fees in proportion to that share. Concentrated v3 pools issue a position NFT instead. They matter because what you do with them, keep, burn or lock liquidity permanently, is the first thing buyers on BSC check.

PancakeSwap, and it is not close. Counting pool creation events across a recent 24 hours, PancakeSwap accounted for roughly 87% of every new pool on BNB Smart Chain and Uniswap for about 13%. On lifetime pair counts the gap is starker still, with PancakeSwap's v2 factory holding hundreds of times more pairs than Uniswap's on this chain. PancakeSwap also carries around twenty times Uniswap's liquidity here. This tool offers both and defaults to PancakeSwap, which is where BNB traders already are.

Mostly no, and it is worth knowing before you read anyone's headline number. Sampling the pairs created on PancakeSwap v2 over a day, roughly two thirds were created by launchpad contracts rather than by a person, with one launchpad alone responsible for well over half. Only about one in eight new pairs came through the router that a human or a dapp actually uses. The real number of deliberate launches per day on BNB is closer to a couple of thousand than fifteen thousand.

PancakeSwap v2 charges 0.25%, not the 0.30% that Uniswap v2 charges, and this trips up guides constantly. More than one page currently ranking for this search states that all v2 pools have a fixed 0.3% fee, which is simply wrong on this chain. On v3 the tiers are 0.01%, 0.05%, 0.25% and 1%. Note there is no 0.30% tier on PancakeSwap v3 at all, and no 0.25% tier on Uniswap v3, so the choice of exchange changes the fees available to you.

For a new token on PancakeSwap v3, 1% and 0.25% are the two sensible answers, and both are common: across a recent week of new v3 pools, roughly half opened at 1% and a fifth at 0.25%. Take 1% when the pair will be thin or volatile enough that liquidity providers should be paid properly for holding it, and 0.25% when you expect steadier two-way flow. The 0.01% and 0.05% tiers exist for stablecoin and tightly correlated pairs.

Worth being straight about: PancakeSwap never shipped a v4. What would have been v4 was renamed Infinity and went live in 2025, with two pool types of its own. It is genuinely busy, accounting for a meaningful slice of BNB Chain's DEX volume and hundreds of new pools a day. This tool does not build Infinity pools. If your launch specifically needs one, create it on PancakeSwap directly. For a straightforward token launch, a PancakeSwap v2 or v3 pool is what the overwhelming majority of BNB projects open.

Not through this tool, and it is the one place where BNB Chain and our quote list diverge, so here is the honest position. USDT is by far the most used stablecoin on this chain, outnumbering USDC on new PancakeSwap pairs by roughly ninety to one. What this tool offers is BNB or USDC. For most launches that is the right pairing anyway, because BNB itself is the quote asset on the large majority of new pairs and it is what the first buy spends. If a USDT pair is essential to your plan, create it on PancakeSwap directly.

Not quite, and two details catch people out. Circle does not natively issue USDC on BNB Chain, so what circulates here is a Binance-pegged version rather than the Circle-issued token you would use on Ethereum or Base. Every major stablecoin on this chain also uses 18 decimals, including USDC, where the same ticker uses 6 on most other networks. Neither affects how the pool behaves, but both matter if you are copying amounts between chains.

Yes, and BNB Chain has the highest measured volume of launch sniping of any network by a wide margin, with academic work counting sniping operations here in the millions against tens of thousands on Ethereum. But the mechanic is not what most guides describe. Measuring pairs created through the PancakeSwap router, none were bought in the same transaction and none in the same block. The median time to the first outside trade was around twenty blocks, roughly nine seconds, clustered so tightly that it reads as bots polling on a fixed interval rather than watching the pending queue. Your first buy runs inside the creation transaction, so it lands before any of that begins.

Because getting it wrong on BNB has a documented history. In early 2025 a launchpad that graduated tokens into PancakeSwap v3 pools was exploited for roughly 183,000 dollars when an attacker pre-created the destination pool at a manipulated price, so migrating liquidity landed into a market someone else had already rigged. That launchpad now graduates to v2 instead. Creating the pool and funding it atomically, at a price you set, closes exactly that window.

Tokenry charges 0.01 BNB and neither exchange charges anything to open a pool, so the rest is gas, and gas is genuinely not the story on this chain. Measured from real pool creations at the current 0.05 gwei, a PancakeSwap v2 pool costs about thirteen cents, a v3 pool about twenty, and a Uniswap v4 initialisation a cent or two. The service fee is the larger number by far. Comparable tools charge 0.024 to 0.03 BNB for the same job, so this is roughly half the cheapest of them.

Swap fees are the income and they are split between liquidity providers in proportion to each one's share of the pool, so as the only provider at launch the early flow is entirely yours. The risks are real though. Impermanent loss means the pool sells your token into rising demand, leaving you with more BNB and fewer tokens than holding would have. Both deposited assets stay exposed to price. And burning or locking is irreversible, so treat it as a decision you make once.

No minimum is enforced, so judge your initial liquidity by price impact rather than a target figure. The BNB side is what buyers spend against, and a shallow one means ordinary trades swing the chart hard, which is exactly what makes a pool look untouchable to anyone evaluating it. Deposit tokens you can leave in place, because removing them later moves the price and every withdrawal is visible on-chain. Relative to your total supply, how much you commit is itself a signal people read.

This is the one thing no other tool on BNB does in the same transaction. Burning sends the LP to a dead address so the liquidity can never be pulled, which on this chain is close to an expectation rather than a nice extra. Locking is available on Uniswap v4, where a fee-forwarding contract deployed for your pool holds the position permanently while the trading fees still route to you. Competing tools either tell you to burn manually afterwards or sell locking as a separate paid step; here both are part of the launch and both are off unless you turn them on.

No, and it is worth asking every tool this. Several BNB launch tools implement multi-wallet buying by asking you to paste private keys into their site. This tool never does that. The first buy is made by the wallet you connected, inside the transaction you are already signing, so there is nothing to import and nothing to trust us with.

PancakeSwap's own interface is free apart from gas, and for simply adding liquidity to an existing pool it is perfectly good. The difference is what happens around the pool creation. Doing it there means separate steps to create, fund, buy and then burn or lock, each one a transaction with a gap after it. Here those are one atomic transaction, simulated first, with the opening price fixed and the LP disposed of before anything else can act on the pool.

Barely, and the difference is smaller than most pages claim. BEP-20 was derived from the ERC-20 standard, and the only changes the specification actually makes are that the symbol and decimals functions become required rather than optional. Everything a pool contract touches behaves identically, which is why the same Uniswap code runs on this chain unmodified.

Usually not. Tokens created through Tokenry include a permit function, which turns the approval into a signature that costs nothing. Permit2 covers many other tokens if your wallet has traded on Uniswap. A plain approval is only needed for tokens supporting neither, and you are told which applies before you begin.

Send those to a v2 pool, on either exchange. Tokens move straight from your wallet into the pair there, so an owner exemption in your contract still applies, and if a cut is taken anyway the BNB side is rescaled so your intended price survives. Concentrated pools verify that what was promised is what arrived and reject the deposit otherwise, so they will not accept a taxing token unless the launcher is exempted first.

Yes, as long as the position was not burned or locked. Add liquidity deepens the pool at its live ratio, and remove liquidity withdraws any share from 1% to 100%, returning both assets along with the fees a v3 position has collected.