This page explains how paid ticket packs, draw hashes, returns, and evidence records can be checked without exposing private member or payment data. 50% goes to Cliff House, 50% goes to prizes.
50%
Supports Cliff House Trust
50%
Is paid as prizes
Together, preserving a local landmark for generations to come
Applications, ticket allocation, payment reconciliation, draw locking, confirmations, draw results, publication, and return creation each write a record event.
Tickets
After payment is reconciled, WordPress assigns tickets at random from the unused Salcombe-prefix pool: SE, CH, WD, SS, NS, FC, SC, and MB, each with 000 to 999. That gives 8,000 possible tickets. Operators cannot choose tickets. Every allocation is written to the record log, and tickets are never silently reused.
Hash chain
Each event stores a payload hash, previous hash, and event hash so the sequence can be checked for unexpected changes.
Draw pack
After the payment cut-off, WordPress locks the paid eligible ticket pack and stores its SHA-256 hash. At the point of no return it creates a 32-byte cryptographic random seed. Each ticket is ranked by HMAC-SHA256(draw_record_id|ticket_number, seed), lowest hash first, with ticket number as the deterministic tie-breaker. The top three ranks win 1st, 2nd, and 3rd prizes. The seed, seed hash, pack hash, and eligible ticket list are published so the result can be reproduced.
Evidence vault
Monthly evidence packs are uploaded to the private 200 Club records vault after an authorised operator presses the Evidence screen save button. The official launch vault is [email protected].
