Fill the treasury
A portion of $LUCKY token activity is directed to the jackpot system.

Every eligible $LUCKY token increases your share of the daily draw. Six holders split the jackpot every 24 hours.
Paste any wallet to estimate its share of the next drawing.
This is an estimate based on the latest indexed balances. Final odds are calculated using the official snapshot block.
A portion of $LUCKY token activity is directed to the jackpot system.
Your share of the eligible supply determines your share of the drawing odds.
Every 24 hours, six unique eligible wallets are selected using the published drawing process.
The distributable jackpot is split between the winners and sent directly to their wallets.
Six arrows found their mark in Round #184.
0x7A15…4372
1.457 ETHVIEW PAYOUT0x34C9…d383
1.457 ETHVIEW PAYOUT0xA1b4…926B
1.457 ETHVIEW PAYOUT0x91D6…019a
1.457 ETHVIEW PAYOUT0xE812…EAc4
1.457 ETHVIEW PAYOUT0x4E54…6755
1.457 ETHVIEW PAYOUT| Round | Date | Wallet | ETH won | Status | Transaction |
|---|---|---|---|---|---|
Each finalized round publishes its snapshot block, eligible supply, exclusion-list version, randomness commitment and reveal, final seed, exact weighted selection inputs, winner calculation hash, and payout transactions.
2,842,048ALGORITHMweighted-without-replacement-v1STATUS✓ FINALIZED
Your eligible token balance is divided by the total eligible supply at the official snapshot block. Winners are then selected one at a time with exact integer-weighted ranges.
Known system addresses such as the zero address, burn address, treasury, jackpot, payout, liquidity pool, routers, bridge and operational wallets are excluded through a published versioned list. Contracts are not excluded merely for being contracts.
The winners remain fixed. The worker records the obligation and retries the same payout idempotently; it never redraws because a transaction reverted or timed out.
No. The displayed distributable jackpot subtracts gas reserve, pending prior obligations and the configured reserve before estimating each prize.
Production only proceeds with a configured verifiable provider: supported VRF, a public randomness beacon, or the documented public commit-reveal process. There is no silent pseudo-random fallback.