BaseBall jackpot token
BaseBall · Jackpot Token
NEXT DRAW IN
0
0
0
0
5
5
5
5
3
3
3
3
2
2
2
2
PRIZE POOL
Ξ
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
—
TOTAL PAID OUT
Ξ
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
—
LATEST WINNER
Waiting for the first draw…

HOW IT DRAWS

Four steps. Every fifteen minutes. Forever.

1

Buy $BBALL

Pick up your ticket on Uniswap or Matcha. Any amount counts toward your stack.

2

Hold ≥ 0.1% supply

100,000,000 BBALL gets you in the draw. More tokens = more tickets, no upper limit.

3

Every swap fuels the jackpot

5% of every trade routes straight into the on-chain prize pool. No team take, no rug.

★

Every 15 min — someone wins it all

Pyth Entropy picks a random eligible holder. 100% of the prize pool gets paid out. Then the next round begins.

RECENT DRAWS

Last 25 winners — every payout verifiable on Base.

No draws yet — first jackpot pending.

BUY $BBALL

Three places. Same token. Same draw. Pick whatever you trust.

Uniswap

Direct swap on the V4 pool that funds the jackpot. Same liquidity, lowest hops.

open ↗

Matcha

0x aggregator routing — usually best price for size, splits across DEXes.

open ↗

DexScreener

Live chart, holders, recent trades. Watch the pool fill between draws.

open ↗

TOKENOMICS & FAQ

Supply
100,000,000,000 BBALL (100B). Fixed at launch by Clanker V4 — no minting, no burning.
Fee
5% on every swap (both sides of the V4 pool), applied at the Clanker V4 hook level. Not a transfer tax — wallets are vanilla ERC-20.
Eligibility
Holders with ≥ 0.1% of supply (100,000,000 BBALL) qualify for the draw.
Whale cap
Each holder's draw weight is capped at 10% of total eligibility, regardless of balance.
Payout
100% of each prize pool goes to the winner. Every fifteen minutes.
Randomness
Pyth Entropy V2 — commit-reveal protocol. Fair as long as either party (us or Pyth) is honest.
Trust model
Phase 2 Merkle-trustless from day one. Snapshot root committed before randomness; on-chain Merkle-proof verification at payout.
Team allocation
Zero. No founder LP, no presale, no vesting.
+How do I know the draw is fair?

Two parts. The random number comes from Pyth Entropy via a commit-reveal protocol — neither the contract nor the entropy provider can predict it. And the holder snapshot is committed as a Merkle root on-chain before randomness is requested; the winning leaf is then proved against that root at payout. Anyone can replay the indexer against the committed snapshot block to verify the root is honest.

+What if I sell my BBALL right after I'm in the snapshot?

You're still eligible for that draw. The snapshot at commit time is your lottery ticket. The contract pays in ETH, not BBALL — there's no lock-in.

+Where do the swap fees actually go?

Straight to the LotteryTreasury contract via Clanker V4's FeeLocker. The keeper sweeps any accrued fees into the contract at the start of each draw — verifiable on BaseScan. There's no admin wallet that can divert them.

+What if there are no eligible holders?

The draw is postponed and the prize rolls into the next 15-minute cycle. No-op for that round, prize accumulates, next draw still fires on schedule.

+Can the contract be paused or upgraded?

There's a pause lever controlled by a 2-of-3 multisig — used only in true emergencies (a critical bug). It cannot redirect funds, only halt draws. The contract is not upgradeable; a replacement would require a fresh deploy and explicit token-holder migration.

+What if a draw gets stuck?

If Pyth's callback never arrives (unusual but possible), emergencyResetDraw() lets the owner void the in-flight draw after 1 hour. The prize pool stays in the contract and rolls into the next round — funds are never lost.