Double blind entropy using Drand for verifiably fair randomness
Details
- External ID
- 46984083
- Source
- HN
- Company
- —
- Product
- Double blind entropy using Drand for verifiably fair randomness
- Website domain
- blockrand.net
- Launched
- Feb. 12, 2026
- Cohort
- —
- Upvotes
- 21
- Upvotes percentile
- 0.6954177897574124
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:25 p.m.
- Updated at
- Sept. 7, 2026, 9:25 p.m.
Description
The only way to get a trust-less random value is to have it distributed and time-locked three ways, player, server and a future-entropy.In the demo above, the moment you commit (Roll-Dice) a commit with the hash of a player secret is sent to the server and the server accepts that and sends back the hash of its secret back and the "future" drand round number at which the randomness will resolve. The future used in the demo is 10 secsWhen the reveal happens (after drand's particular round) all the secrets are revealed and the random number is generated using "player-seed:server-seed:drand-signature".All the verification is in Math, so truly trust-less, so:1. Player-Seed should matches the player-hash committed2. Server-Seed should matches the server-hash committed3. Drand-Signature can is publicly not available at the time of commit and is available at the time of reveal. (Time-Locked)4. Random number generated is deterministic after the event and unknown and unpredictably before the event.5. No party can influence the final outcome, specially no "last-look" advantange for anyone.I think this should be used in all games, online lottery/gambling and other systems which want to be fair by design not by trust.
Enrichment
- Theme
- niche data tools and novelty websites
- Vertical
- Horizontal
- Function
- Dev tools
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Hobby / open-source project
- Normalized one-liner
- verifiable randomness using drand
- Manually corrected
- False
Could you build this?
Yes This is a clean cryptographic demonstration app that ties together standard commit-reveal schemes with the public Drand API and a simple web frontend.
Discussion
16 comments analyzed.
Competitors mentioned: VDFs (Verifiable Delay Functions), Custom MPCs (Multi-Party Computation), Chuck Norris's two-party commit-reveal protocol
Concerns raised: Last-actor/last-look bias in client-server systems without external entropy, Server can hold result hostage if unfavorable outcome, 10-second UX friction from time-lock delay, JSON parsing errors and unexpected 409 responses on commit
Feature requests: Configurable time-lock delay (shorter than 10 seconds if possible), Fix UI handling for multiple rapid commit requests, Improve error messaging for pending commitments
Competitors
Other products that read as similar to this one — 39 launches clear the similarity bar, closest 8 shown.
Attention rank: #16 of 40 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 99 days after the earliest competitor.
- Nostradamus Intellect · ph · 2026-09-22 · 1 upvotes · similarity 0.43
- Postdate · ph · 2026-09-24 · 3 upvotes · similarity 0.42
- QBEACON · ph · 2026-09-13 · 2 upvotes · similarity 0.42
- OpenEntropy · hn · 2026-02-17 · 6 upvotes · similarity 0.40
- Math Gambling · hn · 2026-09-10 · 9 upvotes · similarity 0.39
- LottoKI Deutschland · ph · 2026-09-07 · 2 upvotes · similarity 0.39
- GeneradorStudio · ph · 2026-09-23 · 2 upvotes · similarity 0.37
- I built a P2P network where AI agents publish formally verified science · hn · 2026-03-19 · 47 upvotes · similarity 0.37
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a dev tools tool for Sales yet.