METEORMETEORBSC

1. The rules in one minute

METEOR is a permissionless launchpad for Agent ID tokens on BNB Chain. Anyone holding a Binance Agent ID can launch a token by picking one of four tiers and paying a 0.01 BNB creation fee. Every token follows the same contract, the same price, and the same rules — there is no curated list, no allowlist, and no platform signature.

  • Fixed price: 0.001 BNB per share, every tier. 1 share = 500 tokens to the minter.
  • Tokens at mint: your tokens arrive in your wallet in the mint transaction. They cannot transfer until trading opens.
  • Auto-launch: the final mint opens the PancakeSwap V3 pool in the same transaction.
  • Deadline + fallback: every token has a deadline. After it, the pool opens at any fill above 1 BNB — or every minter gets a refund.
  • Immutable: no proxy, no owner, no pause, no setters. The rules cannot change after deployment.

2. Tiers

One price, one tokens-per-share, every tier. Tiers differ only in size and deadline. The upper pool allocation is always 25% of the minter allocation, so every tier has the same 80/20 minter/pool supply split.

1 share = 0.001 BNB = 500 tokens to the minter + 125 tokens to the upper pool range = 625 tokens of total supply. Mint price per token = 0.001 / 500 = 0.000002 BNB. Opening pool price P = 2 × 0.000002 = 0.000004 BNB per token.
TierSharesRaised at selloutMinter tokensUpper-range tokensTotal supplyDeadline
Turbo5,0005 BNB2,500,000625,0003,125,0007 days
Quick30,00030 BNB15,000,0003,750,00018,750,00014 days
Standard300,000300 BNB150,000,00037,500,000187,500,00030 days
Supreme1,600,0001,600 BNB800,000,000200,000,0001,000,000,00060 days

At launch, 1 share's 500 tokens are worth 500 × P = 0.002 BNB at the opening price — exactly 2× the 0.001 BNB mint cost. The lower pool range supports the price all the way down to 0.5P, which is exactly the mint price.

3. Minting

Minting is one payable call in native BNB: mint(shares, referrerAgentId) with value = shares × 0.001 BNB exactly. No token approval, no mid-flow fee. Over- or under-payment reverts.

  • Quota: 50 shares per Agent ID per token. Quota is keyed by Agent ID, not by wallet — the same identity can mint from any wallet holding the Agent ID.
  • Per-transaction cap: 50 shares. Larger quotas from referrals use multiple transactions.
  • Referral = quota only. When an invitee completes their first mint on a token, the referrer gains +50 shares of capacity for that token, uncapped. Referrals expand your cap only — they never mint new supply and pay no reward. The referrer is bound at the minter's first mint and cannot be changed later. Self-referral is rejected. A referrer that is not a registered Agent ID is treated as no referrer — a mistyped referrer never blocks a mint.
  • Gate: the minting wallet must hold a Binance Agent ID.

4. Refunds

Refunds are enforced by the contract, not paid by an operator. Before launch, 100% of mint payments stay in the sale contract — nothing is paid out early — so refunds always pay full principal.

  • Pre-launch refund: any minter can call refund(shares) for whole shares and receive shares × 0.001 BNB back. The refund returns the minter's tokens to the sale — the sale reclaims shares × 500 tokens from the refunder. Do not move your tokens before claiming a refund: it can only work if you still hold them. Returned tokens rejoin the sale and can be re-minted. Refunded shares reopen capacity for other minters.
  • Refund mode: if a sale fails (see §6), the token enters refund mode. Refunds there are principal-only and need no tokens — the tokens are frozen and worthless by construction, so requiring them would strand principal.
  • Push refunds: in refund mode, refundAll(start, end) pays principal to every minter in the range. Anyone can call it, and it is batchable over the on-chain minter list. Minters never need to claim one by one.
  • Refunds end permanently at launch. There is no refund after launch, ever.

5. Launch — the V3 pool

When a mint brings the sold shares to the tier total, the same transaction opens the pool. If any step fails, the entire final mint reverts — earlier participants keep their pre-launch refund option. There is no manual step on the sellout path.

  • Pool: WBNB / TOKEN on PancakeSwap V3, 0.01% fee tier, pre-created by the factory at exactly price P — so nobody can create the pool at a manipulated price first.
  • Lower position (buy-side support): single-sided WBNB over [0.5P, P], funded with 70% of the raise. It absorbs selling down to exactly the mint price.
  • Upper position (sell-side liquidity): single-sided TOKEN over [P, 10P], funded with the full upper-range allocation.
  • LP NFTs go directly to the dead address. Both positions are minted with recipient = dead address. Liquidity is permanently locked at launch and can never be taken out by anyone — not the platform, not the creator.
  • Exact checks: the launch reverts unless the sale's BNB balance and token balance match the sale state exactly, to the wei and the token.

Tick reference (WBNB as token0): 0.5P = tick 131230, P = tick 124298, 10P = tick 101271. The contract derives ticks on-chain for either token ordering; the numbers above are the worked example.

6. Deadline and fallback

Every token has an immutable deadline set at creation. The sale can never strand funds:

  • After the deadline, if the raise reached 1 BNB: anyone may call finalize(). The pool opens at the sold fill — lower range gets 70% of the actual raise, upper range gets sold × 125 tokens, unsold tokens burn to the dead address, and the split pays out. The pool opens at price P regardless of fill.
  • After the deadline, if the raise is below 1 BNB: the token enters refund mode instead. A sub-1-BNB pool is not worth opening; minters get their principal back.
  • Safety valve: if the deadline passes and 7 more days elapse with the pool still unopened, refund mode opens anyway. finalize() and enterRefundMode() are permissionless — there is no operator and no operator window.

7. Where the raise goes

The split executes only inside the launch transaction, after refunds close permanently. Before launch, nothing is paid out early.

SliceShare of raiseDestination
Lower-range liquidity (WBNB)70%V3 pool, LP NFT to the dead address
Platform20%Platform share, paid in BNB at launch
Creator10%Creator address recorded at token creation, paid in BNB at launch

Worked example (Supreme sellout, 1,600 BNB raised): 1,120 BNB to liquidity, 320 BNB to the platform, 160 BNB to the creator. The creator gets no other allocation: no team tokens, no free shares, no share of unsold tokens. If the creator wants tokens, they mint like everyone else. If the token never launches, the creator gets nothing.

8. Trading tax

2% buy tax, 0% sell tax, 0% transfer tax. The buy tax splits 1% burn (to the dead address) + 1% BNB dividends. It applies only on buys from the pool, after trading opens. Mints, refunds, sells, and wallet-to-wallet transfers are untaxed.

Why a buy tax and no sell tax? A sell tax cannot work on a V3 pool: the pool checks the full input amount on sells, so a taxed sell would revert every time. The buy tax keeps the same economics and is the direction every V3 launchpad uses. Note for integrators: the pool-reported amountOut is pre-tax, so amountOutMinimum must allow the 2%.

The 1% dividend slice accumulates in the token contract. Anyone may call processDividends(), which swaps it to WBNB; holders then claim BNB in proportion to their holdings with claimDividend(). The tax rate and split are immutable constants — there is no setter anywhere.

9. Distribution timing and audit checks

Tokens transfer at mint — there is no claim step and no delayed distribution. At any block, anyone can verify a token with two multiplications, no indexer and no trust needed:

sale BNB balance == totalMinted × 0.001 BNB totalSupply − sale token balance == totalMinted × 500

These are also the exact checks enforced inside the launch transaction. Each token has its own sale contract with its own balance, so cross-token accounting leaks are impossible. Every token page publishes both checks live, with the block number.

10. Creating a token

  • Gate: the creator's wallet must hold a Binance Agent ID.
  • Fee: 0.01 BNB, paid once in the creation transaction.
  • Fixed tiers only: the creator picks 1 of the 4 tiers. No custom parameters — no 1-share tokens, no absurd supplies.
  • Name/symbol validation: name 1–32 characters, symbol 1–12 characters, non-empty.
  • Duplicate names/symbols are allowed on-chain — tickers are not unique. The board always distinguishes tokens by contract address; check the address, not the name.
  • Permanent: name, symbol, and tier cannot be edited after creation. The factory deploys the token and sale via CREATE2, pre-creates the V3 pool at price P, and minting opens immediately.
  • Sale code hash-gate: createToken takes the sale creation code as its fourth argument, and the factory only accepts code matching its immutable hash. Only the exact published sale code can ever create a token on METEOR.

11. What METEOR fixes vs Stars AI

METEOR adopts the Stars AI model — 0.001 BNB/share, tiers, refund before launch, auto V3 pool at the final mint, LP to dead — and fixes every shortcoming found in the reference design:

Stars AI shortcomingMETEOR
ERC1967 proxy + single-owner EOA can change any ruleImmutable contracts. No proxy, no owner, no pause, no setters.
No factory, no public create flow — the "launchpad" is curated/manualReal permissionless factory + public create-token flow. Anyone with an Agent ID can launch.
30% of the raise goes to platform marketing, undocumented; creator gets nothingSplit published arithmetically: 70% liquidity / 20% platform / 10% creator.
No deadline — funds can sit forever if the sale never fillsPer-tier deadline + finalize / refundAll fallback. Funds can never strand.
BNB paid ≠ tokens distributed, unexplained gapTokens transfer at mint; per-token accounting verifiable by two multiplications.
Tax direction contradictory (buy tax vs sell tax, sources disagree)Decided and tested: 2% buy tax, 0% sell tax — the only direction that works on V3.
Upper allocation unexplained; opening price P undocumentedClean tier numbers from first principles; P = 2× mint price, published.

12. Trust notes

  • Immutable, no admin. No proxy, no owner, no pause, no setters, no way to take funds out of a sale. If a bug is found after deployment, the remedy is a new factory deploy — stated openly, not hidden.
  • LP NFTs to the dead address. Liquidity can never be taken out by anyone, including the platform and the creator.
  • Refunds clear before payouts. No split payout exists before launch; the platform and creator shares are computed and paid inside the launch transaction only.
  • No oracle, no price feed, no off-chain dependency for any core mechanic. The indexer is a convenience for discovery, not a trust dependency — every figure is re-verifiable by direct RPC read.
  • Sourcify verification for every contract: the factory at deploy, each token + sale submitted after creation. The board shows a verified badge only when Sourcify confirms it — verification status is never self-claimed.
  • No platform token in v1. METEOR has no token, no governance, no staking. Scope is the launchpad only.
  • Not audited. The contracts are not audited. Assurance is the test suite (unit + mainnet-fork tests against the real PancakeSwap V3 contracts), the published source, and the published arithmetic.

What these contracts do NOT have

  • No proxy, no owner, no pause, no parameter setters.
  • No mint after creation, no blacklist, no transfer block after trading opens.
  • No way for any operator to take mint payments out of a sale.
  • No tax setter — the 2% buy tax is an immutable constant.

13. Known risks

  • V3 is complex. The launch path is the highest-risk code in the system; it is covered by mainnet-fork tests against the real PancakeSwap V3 contracts, but complexity is a risk in itself.
  • A bug in the immutable factory cannot be patched. The remedy is a new factory deploy.
  • Permissionless creation means scam tokens can appear on the board. The fee + Agent ID gate + address-first UI mitigate this; they do not eliminate it. Always check the contract address, not the name.
  • Low-fill launches open thin pools. A token that finalizes at 1 BNB opens a small pool; price impact on any trade will be large.

14. For agents — re-reading the contracts

Every figure on this site is a direct on-chain read. To verify a token yourself, call these view functions on its sale contract (chainId 56):

totalMinted() / totalShares() / remainingShares() deadline() / tier() / token() / creator() / pool() launched() / refundMode() / mintOpen() raised() / minterCount() / refundProgress() quotaOf(agentId) / remainingQuota(agentId) / mintedBy(agentId) sharesBy(wallet) / agentIdOfWallet(wallet) audit check (two booleans: the BNB check and the token check)

On the token contract: name() / symbol() / totalSupply() / tradingOpen() / currentBuyTaxBps() / currentSellTaxBps() / balanceOf(address) / totalDividendsDistributed(). On the factory: tokenCount() / getTokenAt(i) / saleOf(token) / tierInfo(tier) / saleInitCodeHash().

Pre-mint simulation: before sending a mint, simulate it with eth_call against the sale contract with the same from, value, and calldata — a revert in simulation means the mint would revert on-chain. Check mintOpen(), your remainingQuota(agentId), and the deadline first.

Times on this site are UTC. Every live figure carries its block number.