Your draw process
is about to be
examined.
From 20 May, DCMS expects operators to evidence fair, transparent draws. Screenshots, screen recordings and basic online RNGs are not evidence. OCSA Certified Draw is.
The sector thinks it is compliant. It isn't.
OCSA ran a surface scan of all 173 current DCMS Code signatories in Februray, March, and April 2026. The result was unambiguous.
Of 173 operators who signed the Code, only 3 made any reference to it in their terms and conditions. Of those 3, only 1 had made a genuine attempt at full code implementation. The rest have signed up to comply with a Code they appear not to have read, and believe they are compliant when they are not.
The 20 May deadline is not a suggestion. It is the point at which DCMS will assess whether the sector was capable of self-regulation - we all had 6 months to get our pages and practices in order. To show, in good faith, that we didn't need new laws or more stringent rules. There are 22 code points that all must comply with - how many can we honestly say we have hit today? The alternative to voluntary change is sweeping legislation written for the sector rather than with it.
only 3 of 173 signatories referenced the Code at all – April 2026 OCSA scanA basic RNG gives you a number and nothing else. OCD gives you evidence – a tamper-proof, blockchain-backed, independently certified draw record that holds up to any scrutiny. Forever.
Entry list hashing
Your entry list must be fingerprinted before the draw starts. A SHA-256 hash is embedded in the certificate. If the entry list is ever changed by anyone – even a single letter, for any reason – the hash no longer matches and your draw was tampered with. Provably.
Verifiable randomness
Winning numbers are generated by Chainlink VRF – a decentralised oracle network. Neither OCSA nor the operator or any 3rd party can influence the result. The number does not exist until the moment of the draw.
On-chain permanent record
The result is written to the Polygon blockchain instantly. No-one can alter it. Anyone can verify it. The certificate links directly to the blockchain record – forever.
Certificate every draw
A formatted certificate is issued instantly, emailed to the operator and publicly viewable in a searchable archive by OCSA. Share it with your players. Post it publicly. It stands on its own.
DCMS Code compliant
The DCMS Voluntary Code requires verifiably random and auditable draw processes. OCD satisfies clauses 2.1, 2.2 and 2.3 directly – with evidence, not assertions.
Player confidence
Winners, entrants and sceptics can verify any draw result independently. No login required. No request needed. No trust in OCSA required. The blockchain is the proof – permanently accessible to anyone who wants to check it, at any time, for any reason.
Your entry list is your word.
The hash is the proof.
Before your draw runs, drop your complete, final entry list into the console. A SHA-256 fingerprint is generated in your browser – the file never leaves your computer. That fingerprint is embedded permanently in your blockchain draw certificate.
Your players can take your published entry list, hash it independently using any SHA-256 tool, and compare it to the certificate. If the hashes match, the list is exactly what it was when the draw fired. If they don't match, it wasn't.
Any change to the entry list after hashing – adding a row, removing a ticket, correcting a single character – produces a completely different hash. If your published list does not match the certificate hash, it will appear to the world that the entry list was altered before, during or after the draw. By you, the operator. There are very few easily explained or innocent reasons for this.
Four steps. Permanent proof.
Hash your entry list
Drop your complete, final entry list into the console before the draw. A SHA-256 fingerprint is generated in your browser – the file is never uploaded, OCSA does not need a copy of your list. This initial hash is written to your draw certificate and is a permanent record of your entry list at this exact moment.
Launch the draw
A request is sent to the Chainlink VRF oracle network on the Polygon blockchain. The winning number does not exist yet. It will be generated by a decentralised network that neither OCSA nor the operator can influence.
Result recorded on-chain
Chainlink writes the result back to the OCSA smart contract. This is the exact moment the winning number comes into existence. It is permanently and publicly recorded and visible on Polygonscan.
Certificate issued
Your certificate is generated instantly. It includes the winning ticket, your original entry list hash, Chainlink request ID, transaction hash, block number and a direct link to the blockchain record. Emailed, displayed on the OCSA public draw register and archived - effectively for eternity.
One draw. One price.
No surprises.
Available to OCSA Certified, Silver and Gold operators. Priced by the draw, not by ticket volume.
A winning ticket miss debits only £1. A small draw and a high-volume draw cost the same to certify. The current certificate format supports ticket ranges up to 999,999,999.
Draw it live.
Prove it forever.
See the full certified draw process in action. Request submitted. Oracle randomness. Result on-chain. Certificate issued.
Try the live demoLogin: demo / Password: Demo