Skip to content

Launch Battles guide

How Launch Battles work

Two coins still trading on their launch curves compete on qualifying volume. The winner earns a share of the battle’s actual fee pot for eligible holders.

A battle in three steps

The two coins must use the same paired asset, be at similar launch stages and still be pre-graduation.

  1. Invite

    One creator challenges another. The other creator can accept, decline or ignore it. Under current release rules, declaring costs 0.0001 BNB plus gas and is non-refundable.

  2. Trade

    Qualifying buys and sells during the active window add gross volume to each side. A battle lasts 1 to 24 hours, with up to one extra hour if the lead changes near the end.

  3. Settle

    More qualifying volume wins at the timed finish. A coin that graduates during the battle wins immediately. Eligible winning holders share 30% of the actual battle pot.

Losing does not confiscate tokens, curve reserves or future pool liquidity. Trades still incur fees, and prices and positions can change in value.

Worked example: 100 BNB of volume

Coin A records 60 BNB and Coin B records 40 BNB of gross qualifying curve volume. Coin A wins. This is an arithmetic example, not an earnings forecast.

Example assumptions

  • The default 1% ordinary curve fee applies.
  • Both ordinary holder-reward windows are open.
  • No opening tax or creator tax applies in this example.
  • Neither coin graduates; the battle reaches its timed finish with eligible balance-time on Coin A.

The 60 versus 40 split is trading turnover: buys and sells both count. It is not 100 BNB of deposits or net liquidity. The 1% fee produces 1 BNB of ordinary fees.

Coin A

60 BNB

Trading volume

Winner

Shared holder reward

0.09 BNB

Coin B

40 BNB

Trading volume

Example only. Coin A wins by volume, and eligible holders share the reward.
Allocation of one BNB in ordinary trading fees
Where the 1 BNB goesBNB
Coin A’s fixed creator fee recipient0.3000
Coin B’s fixed creator fee recipient0.2000
Ordinary holder pools across both coins0.2000
Active battle pot: platform share0.3000
Allocation of the 0.3 BNB battle pot
Battle-pot allocationCalculationBNB
Winning coin’s eligible holder prize30% × 0.30.0900
Public settlement tipmin(0.003, 1% × 0.21)0.0021
Treasury credit0.3 − 0.09 − 0.00210.2079

The upcoming release’s separate 0.0001 BNB declaration fee goes to Treasury and is not part of these fees or the prize. The shown settlement tip applies to this timed BNB example; automatic graduation settlement pays no public tip.

What one holder could receive

The prize is divided by eligible token-balance-time, not wallet count. Holding more tokens for longer creates a larger share; buying just before the finish does not count as holding throughout.

reward = prize × wallet eligible balance-time ÷ total eligible balance-time

Gross holder rewards from a 0.09 BNB prize
Share of eligible balance-timeGross battle reward
1%0.0009 BNB
2%0.0018 BNB
10%0.009 BNB
100%0.09 BNB

At 2%, the gross reward is 0.0018 BNB before claim gas, acquisition or sale costs, other fees and price changes.

Creators are not automatically the winning holders. Creator fees are paid for trading activity regardless of who wins, and the registered creator address is excluded from prize balance-time.

Selling does not erase eligible time already recorded. Integer base-unit calculations can round individual rewards down. The settled on-chain pot and prize are authoritative.

Optional: a self-funded bot example

In an attacker-favourable closed system, one operator controls both coins, supplies all 100 BNB of turnover and captures both creator streams, all ordinary holder rewards, the whole winning prize and the public settlement tip.

Maximum fee recovery in the self-funded example
Maximum reclaimable feesBNB
Both creator fee streams0.5000
All ordinary holder rewards0.2000
All winning-holder rewards0.0900
Settlement tip0.0021
Total recovered from 1 BNB of fees0.7921

That recovers 0.7921 BNB and leaves 0.2079 BNB of trading fees unrecovered, plus the 0.0001 BNB declaration fee, gas and any adverse trading effects. The fee-only result is at most −0.208 BNB before gas.

This does not say that 100 BNB of principal is lost: the volume is recycled turnover. It is not a universal proof that bots or market strategies cannot profit. Outside traders, changed policies and price moves can change the result.

Asset and stage boundaries

Rewards use the battle’s exact paired asset. USDT does not mix with USDC, and native BNB differs from WBNB. The BNB settlement-tip cap in this example is not the cap for every paired asset.

Current Launch Battles are pre-graduation only. Graduated coins cannot enter this Arena, and this guide does not advertise a future community-battle system.

Frequently asked questions

Does the losing side lose its tokens or liquidity?

No. There is no losing-side confiscation of tokens, curve reserves or future LP liquidity. Participants still bear trading fees, gas and market-price changes.

Does the winning creator receive the holder prize?

Not automatically. Creator fees are separate and are paid on each coin’s trading activity. The fixed creator address is excluded from eligible battle-prize balances.

What if I sell and buy again?

Both holding periods count separately. Selling preserves eligible holding time already recorded, but a zero balance earns no new time. Buying again starts a new period; it does not backdate the new tokens to your first purchase. Only time inside the battle’s measurement window counts.

What happens on a tie or with no eligible holders?

No holder prize is created for a tie or when the winner has no eligible balance-time. Treasury receives the remainder after any settlement tip.

Does the example prove every bot loses money?

No. It bounds fee recovery under one default, self-funded scenario. It does not model every position, outside trader or market move and makes no promise of profit or loss.

Do the declaration fee and limits describe the old testnet?

No. The 0.0001 BNB non-refundable declaration fee is an upcoming-release rule, not a claim about the older testnet. Always rely on the deployed version’s displayed settings.