Protocol, not promises
What the chain enforces.
Randomness and settlement are independently verifiable. The website helps assemble and explain transactions, but it does not get to invent the seed, choose a winner or redirect a payout. Every number here — pool, tickets, winners, amounts — is recomputed from Chia coins rather than kept in a database of ours. There is nothing on our side to adjust. That also means the page can lag: you are looking at a snapshot stamped with the moment it was read, and if the node is unreachable the last good value stays on screen instead of an error. And you never have to take our word for it — the Verify page, the open verifier or the chain itself gives the same answer without this site.
01 / RANDOMNESS
Future randomness, fixed before entry
Before ticket sales close, every table commits to a future drand Quicknet round. After close, CLVM verifies its threshold BLS signature against the public key embedded in the puzzle. The verified signature becomes the seed, and every ticket is ranked by SHA-256(seed ‖ ticket_coin_id ‖ clvm_int(i)), where i numbers the places on a coin that carries several tickets. Neither the raffle operator nor the API can substitute another result, and nobody — not the operator, a player or a bot — can predict that value or put a different one in its place; the single assumption is that a threshold of League of Entropy nodes has not colluded.
02 / SETTLEMENT
Permissionless and transparent settlement
Anyone may submit the valid census and settlement transactions. The puzzles authenticate every ticket, calculate up to three prize ranks and restrict every payout to published destinations.
- Winners receive prizes directly to their wallet addresses
- The payout validator receives the published bounty
- Jackpot reserve and rollover follow fixed on-chain routes
- Ordinary tables pay the operator nothing out of ticket money; the week’s final table pays the published share of its pool to a published reserve address, and sponsor money pays the published share
