Running a raffle onchain sounds trivial until you ask who picks the winner. Block hashes are influenceable by whoever proposes the block. A random number generated by the organizer is just a number the organizer chose. Participants have no way to tell the difference between a fair draw and a rigged one after the fact. Drawbook, presented at a Rialo Builders Hub, solves this with commit reveal. Entries get committed first, bound to wallets. The reveal happens afterward, verified through smart contracts, and anyone can check the outcome onchain. The organizer cannot see what they are drawing against while the entries are still open, and cannot change the result once the reveal begins. That two phase structure is the entire point. Separating commitment from revelation removes the window where someone with privileged timing could act on information nobody else has. It's the same logic behind sealed bid auctions, applied to a problem most onchain raffles still handle on trust. What makes this straightforward to build on @RialoHQ is that the reveal does not need an external trigger. A reveal phase opening at a defined block, or when entries close, is a predicate the network evaluates itself. No organizer pressing a button at the right moment, which is exactly the moment you would want removed from a fair draw. Verifiable randomness has been a solved problem in cryptography for years. Getting it into products people actually use is the part that keeps not happening.