Payouts and buybacks

Holder payouts

The holders bucket is paid out in SOL to the coin's top holders (a stock-paired coin pays in its stock). By default the bot pays the top 50 holders weekly, in proportion to what each holds. A bot can also pay daily, or only when holders vote for a payout, or pay by draw instead.

• Fresh snapshot. Right before paying, the bot reads the holder list from the chain. Recipients come only from that snapshot.
• Who never gets paid. Pools, the bonding curve, the bot's own wallet, burn addresses, Bots' wallets, the creator's cut wallet and program accounts.
• One holder can't take it all. By default nobody gets more than 10% of one payout.
• Worth sending. A payout runs only once the bucket holds at least 0.05 SOL by default. Dust is dropped.
• Payouts go out in batches. Each batch is recorded before it is sent and booked once it is final on chain.

Draws

A creator can pay the holders bucket by draw instead: random holders win each payout. It is the rule for a lottery or raffle bot. The creator picks:

• How often. Daily, weekly, or only when holders vote for a payout.
• How many winners. 1 to 10. They split the payout equally, so a single winner takes all of it.
• The odds. Weighted by holding (twice the coins, twice the chance) or equal for every holder in the draw.
• Who is in it. The top holders (the top 50 by default), or everyone holding at least 0.01% to 10% of the supply.

The default draw reads "1 random holder wins daily, weighted by holding". The same wallets as above never take part, and the minimum payout and the bot's limits apply. Holders can vote to switch between pro rata and a draw; that vote changes nothing else.

How a draw is picked

1. 1

   Commit

   The bot reads a fresh holder snapshot and fixes the eligible list, the pot, the number of winners and the odds. It stores their sha256, the commit hash, with a slot about a minute in the future. That block doesn't exist yet, so nobody knows its hash, the bot included.

2. 2

   Seed

   Once that slot is final, the hash of the first block at or after it, followed by the commit hash, is hashed into the seed.

3. 3

   Pick

   Each round draws one holder from those not drawn yet. Round 1 uses the seed, round r uses sha256 of the seed followed by the byte r. A weighted round picks a point below the total balance and walks the list; an equal round picks a position. Every outcome is equally likely.

4. 4

   Pay

   The winners are paid in SOL (a stock-paired coin's in its stock) in one transaction, recorded before it is sent. The chat and Activity show the winner, the amount and the seed slot.

Check a draw

Every draw has its own page: open Check the draw on its Activity row or on its chat receipt. It shows the commit, both slots, the seed, the whole eligible list with each holder's chance, and a short Node script that redoes the draw against the Solana RPC. The same data is public at /api/draws/<id>.

Each draw is also committed on chain before its seed block exists: a memo transaction signed by Bots' platform key carries bots-draw:v1:<draw id>:<hash>, the sha256 of the draw's id, rules, target slot and every entrant. The check page recomputes that hash in your browser and links the memo, which must sit in a slot before the target slot. The target slot only moves while its block is still well in the future; otherwise the draw keeps it and its page says the commitment is not on chain, and why.

Buybacks

The burn and keep buckets buy the coin on the open market: on the bonding curve before graduation, through Jupiter after. Burn buybacks burn exactly what they bought. Keep buybacks hold it in the bot's wallet.

Every buyback is simulated before it is sent. Each one, and each burn, shows in the bot's Activity with its transaction.

Limits

These limits cover payouts, buybacks and hook rewards together. A bot's own limits are on its How this coin works sheet.

Checking the receipts

Every claim, payout, buyback and burn is a Solana transaction. The bot's Activity links each one, so anyone can check it on an explorer. A draw's row opens its check page instead, which links the transaction.