Skip to content
SANDBOXPlay money only (XPL)
DrawsResultsLiveMy ticketsHow it works

Independent verification

Win an iPhone 18 Pro Max · Draw #00002

Fri 25 Sept 2026 · 12:51 UTC · Draw ID 379475d3-4fa6-4aff-b9d5-4ff1a7ee2d4e

Verification result

VERIFIED

This draw verifies. All 5 checks passed. The published result can be reproduced from the inputs that were fixed before and at the draw.

Checks passed
5 of 5
Verifier
0.0.0

Who computed this verdict

This website's server, by re-running the open verifier over the public record it fetched from the draw API: the plan, the rules document, every committed entry, the revealed seed, the beacon and the signed result. It did not ask the draw engine whether the draw is valid.

The platform's own gate

Before this draw could be marked complete, the platform ran @draw-platform/verifier 0.1.0 over the same public record (1 inclusion proofs) at Fri 25 Sept 2026 · 12:53 UTC and recorded PASSED. A failed gate holds the draw for review; nothing about it is rewritten. This is a fact about the platform's check — the verdict above is this page's own.

Winning tickets, as recomputed

00001

The public record

Five questions, answered from what was published for this draw. Open any item to see the exact values and copy them into your own tools.

  1. What was committed before the draw?

    Confirmed

    Two things were fixed in advance: the operator's secret seed (published as a commitment before sales opened) and the complete entry set of 1 entries, locked and published when sales closed.

    Entry set commitment

    A Merkle root over every accepted entry. It prevents entries being added, removed or changed after sales close. It is not an input to the draw randomness.

    Merkle root
    6743d91a84807c135dfd6211ee94daebedbaf34d2df097cfc1b33a799e4a8e10
    Entries
    1
    Schema
    merkle v1
    Published
    2026-09-25T12:48:00.130Z
    Inclusion proofs checked
    1 of 1
    Seed commitment

    A hash of the operator’s secret seed, published before sales opened. The seed itself is revealed only after the draw, so it could not be chosen to fit the entries.

    Seed commitment
    b296ba898b2509b93b43b97849f0ca9c54b374338d550eed0c9ef727b86414d6

  2. When did sales close?

    Recorded

    Sales closed at Fri 25 Sept 2026 · 12:48 UTC. The entry set was published after that moment and before any randomness existed.

    Timeline
    Sales closed
    2026-09-25T12:48:00.000Z
    Published
    2026-09-25T12:48:00.130Z
    Acquired
    2026-09-25T12:53:01.586Z

  3. What public randomness was used?

    Confirmed

    A value from a public randomness beacon, taken after sales closed. Nobody — including the operator — could know it while entries were still being accepted.

    Public beacon
    Source
    drand Quicknet 52db9ba7…
    Round
    32512472
    Value
    2971a2196b09e590977b5d3a08fdc9a08cbb82bc150ab3bf4d8754b6e09a8af3
    Acquired
    2026-09-25T12:53:01.586Z
    Planned before sales opened
    round 32512472, ≥ 300s after sales close
    Entropy context

    Draw entropy is derived from the revealed seed, the beacon value and the draw context. Anyone can recompute it from these published values.

    Algorithm
    dp-draw/1 (HMAC-SHA256 over seed ‖ beacon ‖ context)
    Seed commitment
    b296ba898b2509b93b43b97849f0ca9c54b374338d550eed0c9ef727b86414d6
    Revealed seed
    6782c6538598dd127ddf1a26329f23f95a9b4e1b2c6f3b9a1a764f35bfdfa1c1
    Beacon value
    2971a2196b09e590977b5d3a08fdc9a08cbb82bc150ab3bf4d8754b6e09a8af3
    Draw context
    D00002 / 2026-09-25
    Entropy
    6f422b11aecb028a9a4aff3a5035577fc7c1850dcfb598152b3508ea99ecaead
    Rules hash
    629248890e86e42fd34c06ed39e67bc5fbecdee940daa7f8dd93df7ad6a4043f

  4. What result was signed?

    Confirmed

    The complete result — the winning tickets in order — was signed before the first one was shown publicly. The signature matches the published result.

    Signed result
    Winning tickets
    00001
    Recomputed by
    this server · @draw-platform/verifier 0.0.0
    Signature
    Algorithm
    Ed25519
    Key ID
    733c9a9e4e76ecebe1fcbef701867f47d167911043632639ea6238f657e0ded7
    Trusted because
    this key id is pinned in the verifier’s own configuration
    Result hash
    386d5e93eaeb15f3a29efdd68fec9d17e5a2682f6e2ea094781528d238396e13
    Signature
    5600723faed96dbc495b74c25708ba0a672baea93b0d86e74c51eb29c90a0b0bda2092a032a14556ebe6e30ac1045bfca83a43becd73029bcbf8d94d3350da08
    Signed
    2026-09-25T12:53:01.663Z

  5. How can inclusion be proven?

    How to check

    Every accepted entry is a leaf of the published Merkle root. Open one of your tickets to see its inclusion proof: a short chain of hashes that leads from your entry to this root. It proves your entry was in the locked set — it has no part in selecting the winner.

    Root to check against
    Merkle root
    6743d91a84807c135dfd6211ee94daebedbaf34d2df097cfc1b33a799e4a8e10
    Schema
    merkle v1

Check it yourself

Re-run this verification in your browser

Your browser downloads the published record — the plan, the rules, every committed entry, the revealed seed, the beacon and the signed result — and recomputes the draw with the same open verifier. Nothing is sent anywhere; the server's verdict is not consulted. The signature is checked against 1 key id pinned in this deployment.

Check your own entry

Each of your tickets carries its own inclusion proof against the entry set published above.

My tickets for this drawFull result