Pot opens
Carries the last winner's 80%.
Fees stack
Every buy and sell feeds it.
Round shuts
Entries lock. Winner not yet decided.
Paid out
20% lands in a wallet.
The draw is run by a script, not by hand: clock, snapshot, tickets, seed, winner. The questions you are already asking, answered straight.
Type how many you hold. Every 250,000 is one ticket in every draw.
Every round we have drawn, including the quiet ones. Click any wallet to check it on the explorer.
A script runs the round end to end: it watches the clock, rebuilds every holder straight from the chain the moment the round shuts, works out the tickets, draws a seed and picks the winner. The only human step is approving the payment, and every number it used is published so you can run the same maths yourself.
The clock runs itself
A round is a fixed slot on the wall clock, not a button someone remembers to press. The countdown you are watching is computed from the same schedule everywhere, so your screen and ours cannot disagree.
The snapshot is the chain
When the round shuts, every transfer of $PBALL since launch is replayed to rebuild who held what. No list is kept on a server, nothing is typed in. The block it read is published with the result, so you can rebuild the same list yourself.
Tickets are arithmetic
Every 250,000 tokens is one ticket, rounded down. The pool, the curve and the jackpot wallet are excluded: they hold supply but they are not people.
The seed decides, not us
A 32 byte seed comes from the browser's cryptographic random source.
The winning ticket is
keccak256(seed, totalTickets) % totalTickets, the same hash
Ethereum uses. Same seed, same total, same winner, every time, on any
machine.
Every payout publishes its seed, the block it read, and the ticket that won. Paste them in and this recomputes the winning ticket in your own browser. If the number that comes out is not the number we published, we cooked it.
That proves the ticket number came from that seed. To go all the way to the wallet, rebuild the holder list at the published block, lay the tickets out in address order, and count to that index. The numbers to do it are all in the table above.