> **Prelaunch.** The contracts are not deployed yet, so there is no address
> to send a transaction to. The figures below are the launch configuration;
> they become live and verifiable the moment `mint` is set.

# TOAST — mint guide for AI agents

TOAST is a fixed-supply token on BNB Smart Chain. Every share is bought with
BNB directly from the sale contract — there is no approve step and no custody.
A wallet holding a Binance `.ai` Agent ID gets its first share free.

- chain id      : 56
- mint contract : (not deployed yet)
- token         : (not deployed yet)
- agent registry: 0x60B9262456dE011F7d15a54CdD8c48bAaa8B022F
- site          : https://toastbsc.fun

## Who may mint

A wallet must own a Binance `.ai` Agent ID. The sale reads the registry at
mint time and reverts with `NoIdentity` otherwise.

## Price

- 0.0012 BNB per share
- 100000 TOAST per share
- 10000 shares total
- the first share is free — one per Agent ID, 5000 left
- at most 10 shares per transaction, 10 per Agent ID

## Referrals

Pass a referrer as an Agent ID handle. The referrer is minted 5% of
whatever you mint, in the same transaction.

    ?ref=yourhandle   ->   resolves via registry.ownerOf(keccak256("yourhandle"))

Check the target exists before you rely on it:

    GET https://toastbsc.fun/api/ref?handle=yourhandle

## Steps for an agent

1. GET /api/stats
2. GET /api/verify?address=<your wallet>
3. GET /api/quote?cards=<n>&who=<your wallet>
4. Send the transaction yourself:

       to      <mint contract>
       value   the BNB amount from /api/quote
       data    one of:

         mint(uint256 cards, uint256 maxCost)
         mintWithRef(uint256 cards, uint256 maxCost, address referrer)
         mintWithRefHandle(uint256 cards, uint256 maxCost, string handle)

   `maxCost` is your slippage guard: the call reverts if the price moved above
   it, so pass the quote you received.

## Supply

Total supply is fixed at 2050000000 TOAST, minted across three buckets:

- 1000000000 to buyers — paid out only against a purchase
- 50000000 as the referral reserve — paid out only as bonuses
- the reserve — team, marketing and liquidity

The reserve is minted at deploy, so it is visible on-chain from block 0, and the
owner has no mint function. It does not sit in a wallet: it is held by a vesting
vault with no owner and no admin.

Release is permissionless and the only possible destination is each bucket's
immutable beneficiary, so nothing here depends on trusting an operator. Read the
schedule yourself:

    GET /api/reserve

## What this contract cannot do

- the supply is capped and the cap has no setter
- the minter slot is write-once, so the sale can never be repointed
- the owner has no mint function — the reserve is minted, not mintable
- transfers are unrestricted: no tax, no blacklist, no pause on selling
- the vault has no owner, no admin and no upgrade path, and its beneficiaries
  are immutable — no key can redirect the reserve
- there is no proxy and no upgrade path anywhere in the system