If your answer isn't here, ask in Telegram.
A fair launchpad for ERC-20 tokens (BEP-20 on BNB Smart Chain) using PancakeSwap Infinity (V4). Anyone pays 0.005 BNB and gets a token deployed and a CL pool seeded in one transaction. LP is locked forever. Creator fees split among up to 5 wallets, claimable any time.
Same UX, different chain. HATCH20 is built natively on BSC + PancakeSwap V4: real LP from minute 0, no bonding curve graduation, hook-based fee schedule. We chose BSC because gas is ~30× cheaper than Ethereum and PancakeSwap Infinity launched mature in 2024.
The CL liquidity position is owned by the HATCH20 launchpad contract with salt = bytes32(0). The launchpad has no function that calls modifyLiquidity with a negative liquidityDelta. So liquidity is locked by absence-of-feature, forever. This is stronger than transferring an LP NFT to 0xdead because there's no possible upgrade path that could let anyone withdraw.
No. Recipient table is set in one transaction at launch, frozen forever. Even the contract's hardcoded admin can't rewrite it (there is no admin).
Then the fees you'd have earned accumulate in the hook contract under that wallet's address until someone with the keys claims them. There's no recovery mechanism - that's a design choice for trustlessness.
No. The pool uses native BNB (currency0 = address(0)). You pay BNB directly when launching, and buyers pay BNB directly when buying through PancakeSwap with our hook.
PancakeSwap's Universal Router 2 picks up our pool because the PoolKey is unique per token. When a user buys/sells via the official PCS app or any aggregator that's V4-aware, our hook fires automatically. The hookData field in the swap call tells us which token+reserve to apply the fee to.
Always exactly 1,000,000,000 tokens with 18 decimals. Hardcoded. No mint/burn after deploy.
Not via the contract. The token has no burn() function. If you want to "burn" tokens, you can transfer them to 0x000...0dEaD, but you can't reduce the supply on-chain.
Not yet. We've done internal review and documented the audit findings in HatchSelfAudit.md. We strongly recommend testing on BSC testnet before launching with real money. A formal audit is on the roadmap.
From any coin's page on hatch20.fun, click "Buy on PancakeSwap" - that opens the official PancakeSwap UI with the right input/output set. Their V4-aware router routes through our pool, so our hook fee applies automatically.
The dev buy is the FIRST swap on your fresh pool. You pay 0.005 BNB creation fee + (your dev buy amount) BNB. The dev buy BNB seeds the BNB side of the pool and the equivalent tokens land in your wallet. Set it to 0 if you don't want a dev buy.
HATCH20 uses single-sided liquidity. At launch, the pool has 1B tokens and 0 BNB. The first swap puts BNB into the pool - and that first swap is your dev buy if you set one. If you skip the dev buy, the pool launches empty on the BNB side and waits for buyers.
You get all your BNB back (minus gas). Common causes: ticker already taken, recipient bps don't sum to 100%, or you sent less than 0.005 BNB. The pool config (sqrtPrice, liquidity, ticks) is hardcoded in the contract - there's no off-chain math to get wrong.
Verified on BscScan after we deploy. Until then, see contracts/HatchToken.sol, contracts/HatchHook.sol, contracts/HatchLaunchpad.sol in the project repo.