Updated：2026-09

How to Verify a LE59 Lucky Draw Result

A draw result is only convincing if people do not have to take "the system picked it randomly" on faith. A verifiable draw works by sealing the basis of the draw first and revealing it afterwards, so anyone can check independently. LE59 Luck uses a commitment–reveal mechanism to achieve this. This article explains the principle, where to verify, and the parts that still require human review.

Commit and reveal: seal first, publish later

When a draw is created, the server generates a random seed and immediately stores its SHA-256 hash as the commitment. At this point only the commitment is public, not the seed — like locking the answer in a safe and showing everyone the safe. When the draw is executed, the server reveals the seed, and anyone can compute SHA-256 of it and compare: if the hash matches the commitment, the seed was fixed before the draw and could not have been swapped afterwards; if it does not match, the commitment was tampered with and the result is not trustworthy.

Result hash: binding the seed to this draw

A seed alone is not enough — to produce "which draw, which participants" output, it needs draw context such as the list snapshot and the round. LE59 Luck computes a result hash from the draw context and the revealed seed, binding the seed to that specific draw. Verification therefore checks not only the commitment but also recomputes the result hash, confirming that the displayed winners were actually produced by that seed in that draw.

Where to verify and how to check

Every public result page provides a verification entry at a URL of the form /public/results/:publicID/verify, where publicID is the result's public ID. For a self-check, follow three steps:

• Compare the commitment: compute SHA-256 of the revealed seed and compare it bit by bit with the commitment hash published at creation;
• Recompute the result hash: recalculate it from the displayed draw context and the seed, and confirm it matches the published result hash;
• Check the list snapshot: confirm the draw was based on the same list participants saw, and that the winners are actually on it.

These steps can be done by hand or with a public hash checker; the point is that nothing depends on any internal claim.

Verification does not judge your rules

One boundary deserves emphasis: the tool guarantees that the randomness is verifiable and the process cannot be tampered with — it does not judge whether your rules are reasonable. Whether the list is correct, whether prize quotas match the event rules, and whether the winner assignment is as it should be are all things organizers must confirm manually. The verifiable mechanism answers "was there any manipulation", while rule-level disputes still rely on rule text and human review. Similarly, a supplementary draw is a separate event that keeps the original winners, so verify its own seed and commitment separately.

Verification is not an afterthought to a draw; it is part of a verifiable draw. Open the LE59 Luck draw tool and run a verifiable draw end to end to see the commit–reveal flow yourself.