# BNBS relaunch / 新一轮 Mint

BSC mainnet: chainId 56. Token and Mint share NEW contract:
`0x2838c17f11e68cb2e3e800ccf608b35c2247caf6`.

## New-round rules
- Total supply: 1,000,000,000 BNBS, 18 decimals.
- Mint allocation: 700,000,000 BNBS / 7,000 shares.
- LP allocation: 100,000,000 BNBS; migration allocation: 200,000,000 BNBS.
- Per share: 0.01 BNB = 100,000 BNBS.
- Wallet maximum: 10 shares = 0.1 BNB + Gas = 1,000,000 BNBS.
- Maximum Mint principal: 70 BNB.
- Migration eligibility, ratio and execution records are pending. Migration is not included in Mint totals.
- New trading target has not been supplied. Do not reuse the old 10,000-share goal.

## Verification status
Read-only RPC confirms name/symbol, decimals, supply, price, token quantity, wallet cap, NFT and treasury addresses. Runtime review identifies the EOA/NFT receive checks and the new receive path lacks the previous startTime early return. Full verified Solidity source is not yet obtained; interface ABI is compatible but is not an audit or a source-verification claim.
Creation block: 130514157. Creation transaction: 0x07b199b6aa83a59142a647570a4df2eaab6d2fde57a44e483d73f78e96d3f0ad.

## Before any payment
1. Read same-origin /agent.json. Use only the new shared contract on chain 56.
2. Query purchased(sender), MAX_SHARES(), balanceOf(contract), PRESALE_BNB(), PRESALE_TOKEN(), NFT() and BNB balance at the same confirmed block.
3. NFT() is SPACE ID Agent ID at 0x60b9262456de011f7d15a54cdd8c48baaa8b022f. Check balanceOf(sender)>0. A typed .ai name is not proof.
4. Use a direct EOA sender. Contract-wallet calls can return without tokens. Verify EIP-7702 paths individually. Do not infer post-launch Mint behavior from the OLD contract.
5. Prepare ONE transfer: to=new shared contract, value=selectedShares * 10000000000000000 wei, data=0x, selectedShares 1–10. Require sufficient remaining quota and stock. Expected tokens: selectedShares * 100000 BNBS. Gas is extra.
6. Simulate from the exact sender using live state, including expected Transfer(contract→sender). Stop if simulation fails or expected tokens differ. Do not substitute another contract, automatically reduce the amount or retry.
7. Show network, recipient, value, data, Gas and expected tokens. Wait for explicit wallet confirmation. Website never connects a wallet, signs or broadcasts. Native BNB needs no ERC20 approval.
8. Verify receipt AND actual token event after confirmation. BNB payment success alone is not Mint success.

## Accounting
Use only this round's contract events and purchased counters. Ignore all previous-round caches, balances and historical Mint counts. Confirm new Mint through native payment and matching token Transfer; exclude funding deposits, migration distributions and ordinary transfers. Failed reads stay unknown rather than zero. Treasury holds project-designated LP/migration reserves; treasury BNB balance does not prove cumulative Mint proceeds or LP. Do not claim LP addition or locking without actual records.

## Read interfaces
purchased(address) 0x522fe98e; startTime() 0x78e97925; PRESALE_BNB() 0xadff13db; PRESALE_TOKEN() 0x8f847c9c; MAX_SHARES() 0x3e8ff57b; NFT() 0x7c0b8de2; treasury() 0x61d027b3; balanceOf(address) 0x70a08231.