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.
| Tier | Shares | Raised at sellout | Minter tokens | Upper-range tokens | Total supply | Deadline |
|---|---|---|---|---|---|---|
| Turbo | 5,000 | 5 BNB | 2,500,000 | 625,000 | 3,125,000 | 7 days |
| Quick | 30,000 | 30 BNB | 15,000,000 | 3,750,000 | 18,750,000 | 14 days |
| Standard | 300,000 | 300 BNB | 150,000,000 | 37,500,000 | 187,500,000 | 30 days |
| Supreme | 1,600,000 | 1,600 BNB | 800,000,000 | 200,000,000 | 1,000,000,000 | 60 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.
| Slice | Share of raise | Destination |
|---|---|---|
| Lower-range liquidity (WBNB) | 70% | V3 pool, LP NFT to the dead address |
| Platform | 20% | Platform share, paid in BNB at launch |
| Creator | 10% | 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:
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 shortcoming | METEOR |
|---|---|
| ERC1967 proxy + single-owner EOA can change any rule | Immutable contracts. No proxy, no owner, no pause, no setters. |
| No factory, no public create flow — the "launchpad" is curated/manual | Real permissionless factory + public create-token flow. Anyone with an Agent ID can launch. |
| 30% of the raise goes to platform marketing, undocumented; creator gets nothing | Split published arithmetically: 70% liquidity / 20% platform / 10% creator. |
| No deadline — funds can sit forever if the sale never fills | Per-tier deadline + finalize / refundAll fallback. Funds can never strand. |
| BNB paid ≠ tokens distributed, unexplained gap | Tokens 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 undocumented | Clean 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):
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.
1. 一分钟了解规则
METEOR 是面向 Agent ID 代币的无许可发射平台,部署于 BNB Chain。任何持有币安 Agent ID 的人都可以选一个等级、支付 0.01 BNB 创建费来发行代币。每个代币都遵循同一份合约、同一价格、同一规则——没有精选名单,没有白名单,不需要平台签名。
- 固定价格:每份 0.001 BNB,所有等级相同。1 份 = 500 枚代币给铸造者。
- 铸造即到账:代币在铸造交易中直接到你的钱包。开池前不能转账。
- 自动开池:最后一笔铸造在同一笔交易里开启 PancakeSwap V3 底池。
- 截止 + 兜底:每个代币都有截止时间。截止后,筹集超过 1 BNB 就开池,否则每位铸造者拿回退款。
- 不可变:无代理、无管理员、无暂停、无参数修改函数。部署后规则无法更改。
2. 等级
每个等级价格相同,每份代币数相同。等级之间只差规模与截止时间。上层底池分配永远是铸造者分配的 25%,因此每个等级的铸造者/底池供应比例都是 80/20。
| 等级 | 份数 | 售罄筹集 | 铸造者代币 | 上层区间代币 | 总供应 | 截止时间 |
|---|---|---|---|---|---|---|
| Turbo | 5,000 | 5 BNB | 2,500,000 | 625,000 | 3,125,000 | 7 天 |
| Quick | 30,000 | 30 BNB | 15,000,000 | 3,750,000 | 18,750,000 | 14 天 |
| Standard | 300,000 | 300 BNB | 150,000,000 | 37,500,000 | 187,500,000 | 30 天 |
| Supreme | 1,600,000 | 1,600 BNB | 800,000,000 | 200,000,000 | 1,000,000,000 | 60 天 |
开池时,1 份的 500 枚代币按开盘价价值 500 × P = 0.002 BNB——恰好是 0.001 BNB 铸造价的 2 倍。下层底池区间把价格一直支撑到 0.5P,也就是恰好等于铸造价。
3. 铸造
铸造是一次原生 BNB 付款调用:mint(shares, referrerAgentId),value = 份数 × 0.001 BNB,必须精确。多付或少付都会失败。无需代币授权,没有中途费用。
- 额度:每个 Agent ID 在每个代币上 50 份。额度按 Agent ID 计算,不按钱包——同一个身份可以用持有该 Agent ID 的任何钱包铸造。
- 每笔上限:50 份。推荐带来的更大额度需要分多笔交易。
- 推荐 = 只加额度。被邀请人第一次铸造该代币时,推荐人获得该代币 +50 份的额度,无上限。推荐只扩大你的额度——绝不会增发代币,也没有任何奖励。推荐人在铸造者第一次铸造时绑定,之后无法更改。自我推荐会被拒绝。不是已注册 Agent ID 的推荐人按无推荐人处理——填错推荐人永远不会阻断铸造。
- 门槛:铸造钱包必须持有币安 Agent ID。
4. 退款
退款由合约执行,不是由运营方支付。开池前,100% 的铸造付款都留在销售合约里——没有任何提前支付——因此退款永远全额退回本金。
- 开池前退款:任何铸造者都可以调用 refund(shares) 按份退款,拿回 份数 × 0.001 BNB。退款会把铸造者的代币退回销售合约——销售合约从退款人处收回 份数 × 500 枚代币。领取退款前请不要转移你的代币:只有你仍持有代币时才能退款。退回的代币重新加入销售,可以再次铸造。退回的份数重新开放给其他铸造者。
- 退款模式:发行失败时(见 §6),代币进入退款模式。那里的退款只退本金,不需要代币——代币已被冻结且按设计没有价值,要求持有代币只会困住本金。
- 推送退款:退款模式下,refundAll(start, end) 向该区间内的每位铸造者支付本金。任何人都可以调用,并且可以按链上铸造者列表分批执行。铸造者无需逐个手动领取。
- 退款在开池时永久结束。开池后永远没有退款。
5. 开池——V3 底池
当一笔铸造使已售份数达到该等级的总数,同一笔交易开启底池。若任何一步失败,整个最后一笔铸造都会回滚——此前的参与者保留开池前的退款选择。售罄路径上没有手动步骤。
- 底池:PancakeSwap V3 上的 WBNB / TOKEN,0.01% 费率,由工厂以恰好 P 的价格预先创建——没人能先以被操纵的价格创建底池。
- 下层头寸(买方支撑):单边 WBNB,区间 [0.5P, P],由 70% 的筹集资金提供。它能吸收抛售,直到恰好等于铸造价。
- 上层头寸(卖方流动性):单边 TOKEN,区间 [P, 10P],由全部上层区间分配提供。
- LP NFT 直接铸给黑洞地址。两个头寸的接收方都是黑洞地址。流动性在开池时永久锁定,任何人都无法取出——包括平台和创建者。
- 精确核对:除非销售合约的 BNB 余额和代币余额与销售状态精确相符(精确到 wei 和每一枚代币),否则开池会失败。
Tick 参考(WBNB 为 token0):0.5P = tick 131230,P = tick 124298,10P = tick 101271。合约会在链上按两种代币顺序推导 tick;以上数字是算例。
6. 截止与兜底
每个代币都有创建时设定的不可变截止时间。销售资金永远不会被困住:
- 截止后,若筹集达到 1 BNB:任何人都可以调用 finalize()。底池按已售份数开启——下层区间获得实际筹集的 70%,上层区间获得 已售份数 × 125 枚代币,未售代币烧到黑洞地址,资金按比例分配。无论售出多少,开盘价都是 P。
- 截止后,若筹集不足 1 BNB:代币改为进入退款模式。不足 1 BNB 的底池不值得开启;铸造者拿回本金。
- 安全阀:若截止后又过 7 天底池仍未开启,退款模式无论如何都会打开。finalize() 和 enterRefundMode() 都是无许可的——没有运营方,也没有运营窗口。
7. 筹集资金的去向
分配只在开池交易内部执行,此时退款已经永久关闭。开池前没有任何提前支付。
| 部分 | 占筹集比例 | 去向 |
|---|---|---|
| 下层区间流动性(WBNB) | 70% | V3 底池,LP NFT 归黑洞地址 |
| 平台 | 20% | 平台份额,开池时以 BNB 支付 |
| 创建者 | 10% | 创建时记录的创建者地址,开池时以 BNB 支付 |
算例(Supreme 售罄,筹集 1,600 BNB):1,120 BNB 进入流动性,320 BNB 归平台,160 BNB 归创建者。创建者没有其他分配:没有团队代币,没有免费份额,没有未售代币的份额。创建者想要代币,就和所有人一样铸造。代币若未开池,创建者什么也得不到。
8. 交易税
买入税 2%,卖出税 0%,转账税 0%。买入税分为 1% 销毁(打入黑洞地址)+ 1% BNB 分红。税只在开池后从底池买入时收取。铸造、退款、卖出和钱包间转账都不收税。
为什么只有买入税、没有卖出税?卖出税在 V3 底池里无法工作:底池在卖出时核对全部输入金额,收税的卖出每次都会失败。买入税保留了相同的经济设计,也是所有 V3 发射平台采用的方向。给集成者的提示:底池报告的 amountOut 是税前金额,因此 amountOutMinimum 必须留出 2% 的空间。
1% 的分红部分在代币合约里累积。任何人都可以调用 processDividends() 把它换成 WBNB;持币者再用 claimDividend() 按持仓比例领取 BNB。税率和分配比例是不可变常量——没有任何修改函数。
9. 分发时间与验算
代币在铸造时到账——没有领取步骤,没有延迟分发。任何人都可以在任何区块用两道乘法验证一个代币,不需要索引,也不需要信任:
这两道验算也在开池交易内部强制执行。每个代币都有自己的销售合约和自己的余额,因此跨代币的账目泄露不可能发生。每个代币页都实时公布这两道验算,并附区块号。
10. 创建代币
- 门槛:创建者钱包必须持有币安 Agent ID。
- 费用:0.01 BNB,在创建交易中一次性支付。
- 仅固定等级:创建者从 4 个等级中选 1 个。没有自定义参数——没有 1 份的代币,没有荒谬的供应量。
- 名称/符号校验:名称 1–32 个字符,符号 1–12 个字符,不能为空。
- 重名/重符号在链上是允许的——符号不是唯一的。榜单永远按合约地址区分代币;请核对地址,不要只看名字。
- 永久:名称、符号和等级在创建后无法修改。工厂通过 CREATE2 部署代币和销售合约,以 P 价格预先创建 V3 底池,铸造立即开启。
- 销售代码哈希门:createToken 的第四个参数是销售创建代码,工厂只接受与其不可变哈希相符的代码。只有这一份确切公布的销售代码才能在 METEOR 创建代币。
11. METEOR 修复了 Stars AI 的哪些问题
METEOR 采用 Stars AI 的模式——每份 0.001 BNB、等级、开池前退款、最后一笔铸造自动开 V3 底池、LP 归黑洞——并修复了参考设计中的每一个缺点:
| Stars AI 的缺点 | METEOR |
|---|---|
| ERC1967 代理 + 单一所有者 EOA 可以改任何规则 | 不可变合约。无代理、无管理员、无暂停、无参数修改函数。 |
| 没有工厂、没有公开创建流程——“发射平台”是人工筛选的 | 真正的无许可工厂 + 公开创建流程。任何持有 Agent ID 的人都能发行。 |
| 30% 筹集资金归平台营销,未在文档中说明;创建者什么也得不到 | 分配按算术公开:70% 流动性 / 20% 平台 / 10% 创建者。 |
| 没有截止时间——销售填不满时资金可以永远搁置 | 每个等级有截止时间 + finalize / refundAll 兜底。资金永远不会被困住。 |
| 支付的 BNB 与分发的代币对不上,有无法解释的缺口 | 代币在铸造时到账;每个代币的账目都可以用两道乘法验证。 |
| 税的方向自相矛盾(买入税 vs 卖出税,不同来源说法不一) | 已决定并经过测试:买入税 2%,卖出税 0%——这是 V3 上唯一可行的方向。 |
| 上层分配无法解释;开盘价 P 没有文档 | 从第一性原理得出的干净等级数字;P = 2 倍铸造价,公开可查。 |
12. 信任说明
- 不可变,无管理员。无代理、无管理员、无暂停、无参数修改函数,没有任何办法把资金从销售合约里取出来。若部署后发现漏洞,补救办法是部署新的工厂——这一点公开说明,不加隐瞒。
- LP NFT 归黑洞地址。流动性永远无法被任何人取出,包括平台和创建者。
- 退款先于分配。开池前不存在任何分配支付;平台和创建者的份额只在开池交易内部计算和支付。
- 没有任何预言机、价格源或链下依赖支撑核心机制。索引只是发现用的便利工具,不是信任依赖——每个数字都可以通过直接 RPC 读取复核。
- Sourcify 验证覆盖每个合约:工厂在部署时验证,每个代币 + 销售合约在创建后提交。榜单只在 Sourcify 确认后才显示验证徽章——验证状态永远不是自称的。
- v1 没有平台代币。METEOR 没有代币、没有治理、没有质押。范围就是发射平台本身。
- 未经审计。合约未经审计。保证来自测试套件(单元测试 + 针对真实 PancakeSwap V3 合约的主网分叉测试)、公开的源代码和公开的算术。
这些合约没有的东西
- 没有代理,没有管理员,没有暂停,没有参数修改函数。
- 创建后无法增发,没有黑名单,开池后转账不受限制。
- 没有任何运营方能把铸造付款从销售合约里取出来。
- 没有税率修改函数——2% 买入税是不可变常量。
13. 已知风险
- V3 很复杂。开池路径是系统里风险最高的代码;它有针对真实 PancakeSwap V3 合约的主网分叉测试覆盖,但复杂本身就是一种风险。
- 不可变工厂里的漏洞无法修补。补救办法是部署新的工厂。
- 无许可创建意味着诈骗代币可能出现在榜单上。创建费 + Agent ID 门槛 + 地址优先的界面可以缓解,但无法消除。请永远核对合约地址,不要只看名字。
- 低填充开池的底池很浅。以 1 BNB 结算开池的代币底池很小;任何交易的价格冲击都会很大。
14. 给 Agent——如何自己读取合约
本站的每个数字都是直接的链上读取。要自己验证一个代币,可以在它的销售合约上调用这些只读函数(chainId 56):
代币合约上:name() / symbol() / totalSupply() / tradingOpen() / currentBuyTaxBps() / currentSellTaxBps() / balanceOf(address) / totalDividendsDistributed()。工厂上:tokenCount() / getTokenAt(i) / saleOf(token) / tierInfo(tier) / saleInitCodeHash()。
铸造前模拟:发送铸造交易前,先用 eth_call 以相同的 from、value 和调用数据对销售合约模拟一次——模拟中失败意味着链上也会失败。请先检查 mintOpen()、你的 remainingQuota(agentId) 和截止时间。
本站的时间均为 UTC。每个实时数字都附带区块号。