OCSA Certified Draw – The Clock is Running
DCMS Code takes effect 20 May 2026 – 23 days

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 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 one had made a genuine attempt at implementation. The rest have signed a Code they have not 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 is capable of self-regulation. The alternative is legislation written for the sector rather than with it.

3 of 173 signatories referenced the Code – April 2026 OCSA scan
The solution
OCD
OCSA Certified Draw – yes, OCD. Possibly the first time that's been something to aim for.

A basic RNG gives you a number. OCD gives you evidence – a tamper-proof, blockchain-backed, independently certified draw record that holds up to any scrutiny. Forever.

01

Entry list hashing

Your entry 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.

02

Verifiable randomness

Winning numbers are generated by Chainlink VRF – a decentralised oracle network. Neither OCSA nor the operator can influence the result. The number does not exist until the moment of the draw.

03

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.

04

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.

05

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.

06

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.

Entry list hashing – why it matters

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 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.

SHA-256 ENTRY LIST HASH – EXAMPLE
68652aaeff72316b65fa9fd83d59888e37b0c7b4c8de740534f451631de99503

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, it will appear to the world that the entry list was altered after the draw. By you, the operator. There is no innocent explanation for this.

How a certified draw works

Four steps. Permanent proof.

1

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. This freezes the state of your entry list at this exact moment.

2

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.

3

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 visible on Polygonscan.

4

Certificate issued

Your certificate is generated instantly. It includes the winning ticket, entry list hash, Chainlink request ID, transaction hash, block number and a direct link to the blockchain record. Emailed, displayed and archived.

Simple pricing

One draw. One price.
No surprises.

Available to OCSA Certified, Silver and Gold operators. Priced by the draw, not by ticket volume.

50 draws
£125
£2.50 per certified draw
250 draws
£525
£2.10 per certified draw

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 demo
Login: demo / Password: Demo

Online Competition Standards Authority Ltd  ·  Company No: 16883150  ·  167–169 Great Portland Street, London W1W 5PF
OCSA – the small print in the big picture  ·  ocsa.org.uk