Verification

Check it yourself.

Every Hit Engine draw publishes the inputs it used. This page recomputes the result from those inputs — in your browser, with nothing uploaded anywhere — and tells you whether the published winners actually follow.

Loaded below: Demonstration round. Paste any other round's proof.json URL, or open a file you downloaded earlier.

This checker needs JavaScript — it runs the whole verification in your browser, which is the point of it.

You do not have to enable it. verify-draw.mjs performs the same checks from a terminal, has no dependencies to install, and is written independently of this page so that it disagrees if this page is wrong:

node verify-draw.mjs https://hitenginegaming.com/raffle/demonstration-round/proof.json

The proof itself is plain JSON: /raffle/demonstration-round/proof.json

What is being checked

The claim is narrow, and that is deliberate — a narrow claim is one you can actually test:

The winners were determined by randomness that did not exist when the entry list was frozen, and the entry list cannot have been altered afterwards.

The revealed seed hashes to the value committed before entries opened.
That commitment was published somewhere Hit Engine does not control, before entries opened.
The published entry list hashes to the commitment recorded at the seal.
The ticket count matches the list, with no gaps or duplicate indices.
The seal precedes the beacon. This is the one that matters — it is what makes the draw unsteerable, and the one an attacker would have to defeat.
The drand signature verifies under quicknet's group public key. Anyone can fabricate a randomness/signature pair where one is the hash of the other; only the drand network can produce one that passes this.
The published winners and reserves recompute from those inputs.

Why you can trust this page less than you think — and why that is fine

This page is served by Hit Engine, so in principle we could ship a verifier that always says PASS. Three things make that not worth attempting:

There is a second implementation. verify-draw.mjs is a separate program, written against Node's own crypto library, with no dependencies to install. Download it, read it — it is about 250 lines — and run it against the same proof. If it disagrees with this page, something is wrong.
node verify-draw.mjs https://hitenginegaming.com/raffle/demonstration-round/proof.json
The algorithm is published in full. It is on the rules page, written so a third party can reimplement it from scratch. Standard SHA-256 and HMAC throughout — nothing exotic, nothing of ours.
The beacon comes from somewhere else entirely. Fetch the drand round yourself and compare it to what the proof claims. We have no part in producing it and cannot influence it.

If a check ever fails on a real round, say so publicly. A verifier that nobody acts on is decoration.