Daily Receipt #13 · 02 Sept 2026
revealedPublished sequence
1925858
- Entries opened
- 2026-09-02 00:00:00 UTC
- Entries closed
- 2026-09-02 23:30:00 UTC
- Result published
- 2026-09-02 23:35:00 UTC
- Valid entries
- 1
- Exact-match sequences
- 0
- Lunch money paid
- €100
- Bitcoin amount
- 0.00150215 BTC
- Rate source
- Coinbase BTC-EUR spot · 2026-09-02 23:35:01 UTC
- Commitment algorithm version
- dlm.daily-seven.commitment.v1
- Commitment hash (sealed before entries opened)
- de71531eb850e685270f04276949926b8dac380973cbe7e11ccf6a6bf0fd7bc8
- Bound record id
- 7c6532ed-eec3-4d4a-a079-7dfb411a814c
- Bound record date
- 2026-09-02
- Rules version sealed into this record
- 1.1
- Bound rules content hash
- 9ba4660c3bff2aeb6ed6de65f40db4d115cca11d4e226af9410985a382eb7e97
- Revealed seed
- 825e3e02431889e4daadc3a0d2f864096234d97324f9b9a6f2f6355e69876939
The published commitment does not reveal the sequence because it commits to a cryptographically random 256-bit secret seed. Reversing that commitment is considered computationally infeasible.
After the reveal, the seed above and the bound record context are recomputed with the published algorithm. Matching values could not have been altered after entries were seen.
canonical = {"domain":"dlm.daily-seven.commitment.v1","recordId":<record id>,"drawDate":<YYYY-MM-DD>,"rulesContentHash":<rules hash>,"seedHex":<revealed seed>}
commitment_hash = SHA-256(canonical) (full 64 hex characters, never truncated)
message(i, r) = "dlm.daily-seven.derivation.v1|" + recordId + "|" + drawDate + "|" + rulesContentHash + "|" + i + "|" + r
tag(i, r) = HMAC-SHA-256(key = seed bytes, message(i, r))
accept the first r where tag(i, r)[0] < 252, then value_i = (tag(i, r)[0] mod 9) + 1
winning_values = value_0 .. value_6 in position order (digits may repeat)