bucket

Transparency

Every fill and every tip is public. This page lists the wallets, the fee routing of every bucket, and the exact draw method, so anyone can check a round without trusting us.

You are looking at the local simulation. Addresses and signatures are simulated; the draw code is the production code.

Custody, honestly

During beta, bucket wallets are run by our keeper. Every move is public on-chain. Vault keys are generated server-side, encrypted with a KMS master key and only decrypted inside a signing service that refuses anything except: Jupiter swaps into this bucket's bag coins, token transfers to the winners of the current round, compute-budget instructions and SOL transfers to winners when a bag is empty. Anything else is refused and pauses the platform. A fully on-chain vault program (non-custodial) is on the roadmap.

Platform wallets

Keeper (pays gas)
Bucket fee wallet
Admin (pause / denylist)

Fee routing per bucket

Creator fees are split with pump.fun's fee-sharing config and the admin rights are revoked at launch, so the split can never change. A bucket shows up in the gallery only after the split is verified on-chain.

BucketVaultBurn / Bucket / CreatorRouting

How winners are picked

  1. Snapshot 60 seconds before the tip: every holder of the coin, their balance, exclusions and weights. The canonical JSON (fixed keys, sorted by address) is hashed with SHA-256 and the hash is published.
  2. Seed from the future: target slot = snapshot slot + 150 (~60 s). If that slot is skipped, the first confirmed slot after it is used. seed = sha256(blockhash ‖ mint ‖ u32be(roundNo) ‖ snapshotHash)
  3. Draw without replacement, all in integers: candidates sorted by address; for k = 0…N−1, u = u64be(sha256(seed ‖ u32be(k))[0..8]), target = (u × remaining) >> 64, take the first candidate whose running sum of weights exceeds the target, remove it.
  4. Weight = min(balance, 2% of supply) — capped so no whale wins every round. Chance shown in the UI ≈ 1 − (1 − w/total)N.
  5. Payout: 25% of the bucket by default, split over the bag coins by their value in the bucket, equal shares per winner. Shares below $0.05 stay in the bucket.

Why not VRF yet: a slot leader could in theory influence a blockhash, but the snapshot is fixed and hashed before that block exists, and the amounts are small. A VRF (Switchboard / ORAO) is planned for v2.

npm run verify <roundId>

Who is excluded

The trade-off we don't hide

With equal payouts, splitting a balance across many wallets raises the chance of landing among the winners. The $10 minimum, holding since the previous tip, and rent plus gas per wallet make it costly. Weighted payouts make splitting pointless; that mode is a configuration switch. Funding-source clustering is planned.

Risks

Not affiliated with pump.fun. Memecoins are extremely risky. Nothing on this site is financial advice.

Transparency · Bucket