How Oven works

Overview

OvenLaunch is a token launchpad on BNB Smart Chain. Anyone can launch ("bake") a token in one transaction, without putting up any liquidity. The whole supply goes into a PancakeSwap V3 pool whose liquidity is locked forever, and the token's creator earns 80% of the pool's LP fees for as long as it trades.

There is no bonding curve and no graduation: every token is a normal PancakeSwap token from its first block, tradable on PancakeSwap, aggregators, terminals and wallets right away.

How a bake works

One call to the Oven factory does all of this:

1. Deploys a fixed-supply token: 1,000,000,000 tokens, 18 decimals, no owner, no mint function, no transfer tax, no blacklist, no pause, no proxy.
2. Creates its PancakeSwap V3 pool at the 1% fee tier against the pair you chose, and opens it at the $6,000 starting market cap.
3. Places the entire supply in the pool as a single-sided position starting just above that price. You add no BNB: buyers' BNB (or pair asset) fills the other side as the price rises, like a bonding curve.
4. Sends the position NFT to the Oven locker, which has no function to withdraw it, and records the fee shares you chose. They can never change.
5. Runs your optional first buy (max 10% of the supply) inside the same transaction, so nobody can buy before you.
6. Starts the anti-sniper mode you picked: Shield or Degen.

The token address is created with an unpredictable CREATE2 salt, so nobody can pre-create its pool to block the launch. Your logo, description and links are stored on-chain in the factory; only you can update them later. Name, ticker, pair, mode and fee shares are final.

Starting market cap. Every launch opens at the same $6,000 market cap, converted to the pair asset at its live PancakeSwap price, so launches are comparable and nobody games the start. A $700 buy right after the launch gets about 10% of the supply, and Shield's 1% cap per wallet is worth about $60.

Cost. Baking is free: there is no launch fee. You pay network gas (well under $1 on BSC) and your optional first buy.

Shield & Degen

BNB Smart Chain is full of sniper bots. Every launch picks how to handle the first minute:

Shield reduces sniping; it can't stop a bot that splits its buys over many wallets. That is why every token page shows its Sniped %: the share of the supply bought by wallets other than the creator in the launch block and the two blocks after it, so you can judge a launch yourself. Launch transactions sent through a private RPC (like 48 Club or bloXroute) are invisible in the public mempool until they are mined, which helps further.

Blaze (coming in v2). A PancakeSwap Infinity hook with a high opening fee (for example 50%) that falls to 1% within minutes: snipers pay, everyone else doesn't. It needs a new pool type and an audit, so it ships after v1.

Doneness

Oven has no bonding curve, so tokens don't "graduate". They bake: doneness is how far a token's market cap has come from the $6,000 start to Golden brown at $69,000, shown as an oven temperature from room temperature (25°C) to 230°C.

Doneness follows the current market cap. It is a reading, not a promise: a token can cool down again.

Fair Bake score

Every token page shows a score from 0 to 100, computed in your browser from facts anyone can check on-chain. Checks whose data hasn't loaded yet are left out.

85 and above reads Fair bake, 65 to 84 Mostly fair, below 65 Handle with care. A high score is not investment advice: it says the launch was fair, not that the token will go up.

Fees

Every launch pool charges PancakeSwap's 1% swap fee on each buy and sell. It is a pool fee, not a token tax. PancakeSwap takes its protocol share; the rest goes to the locked liquidity position, and Oven's locker splits it at the shares fixed when the token was baked.

In numbers: a creator who keeps everything earns 80% × 68% = 54.4% of the 1% fee, about 0.544% of the volume. Oven earns 13.6% of the fee (0.136% of volume), or 10.2% when a referrer is set.

Fees paid in your token. Swaps pay the fee in whichever asset goes into the pool, so the position earns both the pair asset and your token. Your token's fees follow the same shares, except that the holder and buyback parts of them are burned.

Collecting. Fees accrue in the pool until someone collects them. Anyone can trigger a collection (the "Collect & pay out fees" button on every token page); the fees always go to their owners, never to the caller. A payout a recipient can't receive (for example a blacklisted address, or token fees above 1% of the supply during Shield) is held for that recipient instead of blocking the others.

Holder dividends & buybacks

💸 Holder dividends

A creator can route part or all of their 80% to the token's holders. That part of the pair-asset fees is paid into the token contract and shared among holders in proportion to their balance at the moment it arrives. Holders claim it on the token page or in their portfolio, as BNB for BNB pairs or the pair asset otherwise (a USDT pair pays USDT; a pair with a tokenized stock pays that stock).

• The pool, the locker, the burn address and other infrastructure never earn dividends.
• Dividends start once holders own at least 1,000 tokens in total; earlier amounts wait and are paid out then.
• Transfers and burns don't change what a holder has already earned.
• The share is fixed at launch: nobody, not even the creator, can stop or redirect it.

Known limits. Dividends are shared when fees are collected, by the balances at that moment, so a bot could buy just before a large collection and sell after. Frequent collections keep each one small. Other pools of the same token (for example a V2 pair someone creates) hold tokens that earn dividends nobody can claim, which slightly dilutes holders.

🔥 Buyback & burn

A creator can also route part of their share to buybacks: that part of the pair-asset fees buys the token back in its own pool and burns everything bought. Anyone can run a buyback; nothing goes to the caller. A buyback only runs while the price is within about 3% of its 3-minute average, and each run moves the price by at most about 2%, so nobody can sandwich it. Whatever can't be spent waits for the next run.

Referrals

Every wallet has a referral link: ovenlaunch.fun/bake?ref=YOUR_ADDRESS. When a creator bakes through it, the referrer earns a quarter of Oven's platform share of that token's LP fees (5% of all its LP fees), for as long as it trades. The creator's 80% is not affected. The referrer is recorded on-chain at launch; you can't refer your own launch. Bots, KOLs and communities are welcome to use it.

Pairs

Your token can trade against:

• BNB (the default, paired as WBNB).
• USDT (BSC's USDT has 18 decimals) and USD1. USD1 is an upgradeable contract whose issuer can pause transfers; while it is paused, tokens paired with it can't trade.
• CAKE.
• Any other BEP-20 with a PancakeSwap V3 market against BNB or USDT, such as tokenized stocks. Such tokens must not take a fee on transfers or rebase: those break PancakeSwap V3 pools.

Whatever the pair, buyers can pay with BNB: the swap routes through the pair asset automatically. Creator fees and dividends accrue in the pair asset.

Safety & risks

What Oven guarantees by code

• Launch liquidity can never be removed: the locker has no withdraw function.
• Every Oven token has a fixed supply and no owner, tax, blacklist or pause; holders can always sell.
• Fee shares, holder dividends and buybacks are fixed at launch and can't be changed by anyone.
• The platform owner can only change the launch fee (capped at 0.05 BNB), the fee recipient, the platform and referral shares for future launches (capped at 30% and 50%), set the buyback contract once, and pause new launches. It has no power over existing tokens.

What it can't promise

• Anyone can bake a token with any name, including fakes of real projects. Oven flags look-alikes and can hide tokens from this website, but the contracts stay permissionless. Always check the contract address.
• Creators can hold a large share (see "Dev holds") and sell it. A token's price can go to zero.
• Shield reduces sniping but can't stop every bot.
• Smart contracts can have bugs. The contracts are open source and tested; an external audit is planned before large-scale promotion.

Nothing on OvenLaunch is financial advice. See the Terms.

Contracts

Third-party contracts

Checked on-chain before every deploy (npm run check:bsc).

For developers, terminals & bots

Every Oven token is a standard BEP-20 in a standard PancakeSwap V3 pool (1% tier), so it trades through any PancakeSwap integration from its first block. To label tokens as Oven launches:

• Listen for TokenLaunched and LaunchTerms on the factory: name, symbol, pool, pair, start price, mode, fee shares, referrer and first buy, all in the launch transaction (details on the Developers page).
• Every Oven token address ends in 0000: the factory refuses any other.
• Read a launch with getLaunch(token) or getLaunchView(token): creator, pool, pair, mode, fee shares, referrer and first buy. Page through all of them with launchCount() and getLaunches(offset, limit).
• Fee payouts emit FeesCollected(token, caller, fees) on the locker; dividends emit DividendsDistributed and DividendsClaimed on the token; buybacks emit BoughtBack(token, quoteSpent, tokenBurned).
• While Shield is on, limitsEndAt() on the token returns when it ends; transfers that would leave a wallet above 1% of the supply revert with MaxWalletExceeded.
• Note that PancakeSwap V3's Swap event has two extra fields compared to Uniswap V3 (protocolFeesToken0, protocolFeesToken1), and slot0().feeProtocol is a uint32.

JSON ABIs, a public JSON API and progress data for bonding-curve tools are on the developer page. The source is verified on BscScan.