Independent verification
Win an iPhone 18 Pro Max · Draw #00002
Mon 28 Sept 2026 · 11:45 UTC · Draw ID f2c3f1df-a07f-4c08-a0a6-56569db4bdd1
Verification result
NOT VERIFIED
This draw does not verify. 0 of 5 checks passed. At least one check failed. Treat this result as unverified and contact the operator.
- Checks passed
- 0 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 (2 inclusion proofs) at Mon 28 Sept 2026 · 11:45 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
00002
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.
What was committed before the draw?
Entry set not locked yetThe seed commitment is published before sales open. The entry set is locked and published when sales close.
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
- 2e3d3d55a8a3a166a2ec7964091151ea6f25eefe21f051326d7c288185004f38
- Entries
- 2
- Schema
- merkle v1
- Published
- 2026-09-28T11:40:00.127Z
- Inclusion proofs checked
- 0 of 2
- Not reached
- the verifier stopped at the failed check above
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
- c3168817aa25dc84762981fc122aecf147baec85008fce0250cd933e4ef803c2
When did sales close?
RecordedSales closed at Mon 28 Sept 2026 · 11:40 UTC. The entry set was published after that moment and before any randomness existed.
Timeline
- Sales closed
- 2026-09-28T11:40:00.000Z
- Published
- 2026-09-28T11:40:00.127Z
- Acquired
- 2026-09-28T11:45:01.319Z
What public randomness was used?
Not published yetA public beacon value is taken after sales close. It has not been published for this draw yet.
Public beacon
- Source
- drand Quicknet 52db9ba7…
- Round
- 32597512
- Value
- 341d1a651461167f46b2f8160393543538bdc7eec20461738041371c50a877b9
- Acquired
- 2026-09-28T11:45:01.319Z
- Planned before sales opened
- round 32597512, ≥ 300s after sales close
- Not reached
- the verifier stopped at the failed check above
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
- c3168817aa25dc84762981fc122aecf147baec85008fce0250cd933e4ef803c2
- Revealed seed
- ba53cda936a5e74c920076cf1750e1c38e1573a3c54533fc4dad67ecb7f0b572
- Beacon value
- 341d1a651461167f46b2f8160393543538bdc7eec20461738041371c50a877b9
- Draw context
- D00002 / 2026-09-28
- Entropy
- 08956933e3864b8b8fbdc86301fc36ed5ab1f6d158758f14b90fb22e056a7611
- Rules hash
- 629248890e86e42fd34c06ed39e67bc5fbecdee940daa7f8dd93df7ad6a4043f
- Not reached
- the verifier stopped at the failed check above
What result was signed?
Check failedThe complete result is signed before the first of the winning tickets is shown. No signed result has been published yet.
Signed result
- Winning tickets
- 00002
- Reserves
- 00001
- Recomputed by
- this server · @draw-platform/verifier 0.0.0
- Not reached
- the verifier stopped at the failed check above
Signature
- Algorithm
- Ed25519
- Key ID
- 72f97d392380f67f0131eba9bb159e661d80fb4f5de704e3bb37d98091763086
- Trusted because
- this key id is pinned in the verifier’s own configuration
- Result hash
- 1ed76fb30120b6da5768b6243655c25d070f376ab7426b04ca5cfa614705c01e
- Signature
- 80acf1c292f601b1cec694efbc5ce32c13a7bad55fbf07cb4b211ec2f8a68479faea5a1a7fa54784c82acc0167f92d1e93c35b7eddda36cfeb214606a310c107
- Signed
- 2026-09-28T11:45:01.397Z
- Failed check
- untrusted_key: the result is signed by a key the verifier does not trust
How can inclusion be proven?
How to checkEvery 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
- 2e3d3d55a8a3a166a2ec7964091151ea6f25eefe21f051326d7c288185004f38
- 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.