Daily Receipt #14 · 03 Sep 2026
revealedPublished sequence
9527393
- Entries opened
- 2026-09-03 00:00:00 UTC
- Entries closed
- 2026-09-03 23:30:00 UTC
- Result published
- 2026-09-03 23:35:00 UTC
- Valid entries
- 1
- Exact-match sequences
- 0
- Lunch money paid
- €100
- Bitcoin amount
- 0.00143228 BTC
- Rate source
- Coinbase BTC-EUR spot · 2026-09-03 23:35:01 UTC
- Commitment algorithm version
- dlm.daily-seven.commitment.v1
- Commitment hash (sealed before entries opened)
- 92a72424d7b66a7cd31ea24c9b6ad5be02e6253b7f21ac92cf6903ab08097f4b
- Bound record id
- 7d731819-c04c-44ea-a8f9-c81db9370a53
- Bound record date
- 2026-09-03
- Rules version sealed into this record
- 1.1
- Bound rules content hash
- 9ba4660c3bff2aeb6ed6de65f40db4d115cca11d4e226af9410985a382eb7e97
- Revealed seed
- 01a46905248b078497f12ae69e5e010ddd0bba176ae4a853d555cb4ea2d73bc2
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)