A private cross-operator registry blocks a self-excluded player at every licensed operator without any operator seeing another's customer data. Zero-knowledge proofs confirm a wallet is on the exclusion list while the underlying identity stays sealed, so protection is complete and privacy is preserved.
Turn a set of siloed operator blocklists into one shared, privacy-preserving exclusion check.
01.
Replace isolated per-operator blocklists. The KYC and AML Utility Registry holds one consortium exclusion set, so a self-exclusion at any operator propagates to every licensed venue at once.
02.
Check membership without disclosure. The ZK Proof Verifier confirms that a player is on the exclusion list without revealing who they are, so no operator ever reads a competitor's customer record.
03.
Anchor each exclusion to a decentralized identifier. The DID and VC Ledger binds the block to a verifiable credential, so the same person is caught even when they use a new account or wallet.
04.
Let a player exclude themselves once. A signed enrollment writes the exclusion to the registry, and the player controls the credential rather than trusting a single operator to hold it.
05.
Block at the point of play. Before a wager or deposit is accepted, the operator queries the registry and is denied automatically if the ZK proof shows an active exclusion.
06.
Give the authority provable coverage. Regulators confirm that every licensed operator queries the shared registry, demonstrating that self-exclusion is enforced across the entire market.
Follow a self-exclusion from a single enrollment through a privacy-preserving check at a different operator.
10:02:14
[SYS] Initializing self-exclusion enrollment...
10:02:14
[CMD] enroll { did: "did:cer:0x77a1", period: "PERMANENT" }
10:02:15
[AUTH] Binding exclusion to verifiable credential...
10:02:15
[OK] Exclusion anchored to shared registry.
Cerulea decomposes cross-operator self-exclusion into modular contracts. Each layer enrolls, seals, verifies, and enforces an exclusion so protection is shared while no operator reads another's customer data.
Privacy-preserving exclusion is a horizontal capability. Here is how different actors put the shared registry to work.
Query one shared registry before every deposit, honoring self-exclusions enrolled anywhere in the market while never exposing or ingesting a competitor's customer data.
Key Asset Types
Demonstrate market-wide harm reduction by attesting that every licensee enforces the registry, replacing self-reported compliance with verifiable cross-operator coverage.
Key Asset Types
Offer players a single self-exclusion that follows their identity across every venue, giving support charities a durable protection mechanism that operators cannot quietly ignore.
Key Asset Types
Whether you are bridging a legacy operator KYC platform or enrolling players directly from a self-sovereign wallet, Cerulea routes both into one privacy-preserving registry.
For licensed operators on legacy KYC systems. Existing verified identities are converted into sealed exclusion commitments and registry queries through the API gateway automatically.
Operator KYC Platform
Legacy Identity Systems
Cerulea API Gateway
Commitment & ZK Proving
Cerulea Private Chain
Consortium Exclusion Registry
For players enrolling directly. A wallet holding a verifiable credential signs the self-exclusion and routes it to the registry without an operator acting as custodian.
Player Wallet / VC
Self-Sovereign Identity
Consortium Validators
Exclusion Consensus
Cerulea Registry
Shared Exclusion Ledger
Building a cross-operator registry with zero-knowledge membership proofs, DID-bound credentials, and point-of-play enforcement from scratch requires specialised cryptography engineers and long consortium negotiations. Calculate your exact deployment speed using Cerulea.
Traditional Deployment
Solidity Coding & Audits
~ 13 Months
Visual Compilation
WASM Logical Artifacts
~ 4 Weeks
The legacy timeline reflects multi-operator compliance integration benchmarks. Agreeing a data-sharing standard between competitors, building zero-knowledge membership proofs, and wiring enforcement into each operator's deposit flow takes a baseline of 9 months. Building the same architecture on Cerulea takes a baseline of 2 weeks, because Cerulea Studio visually translates your exclusion and privacy rules into pre-audited WebAssembly binaries and provisions the shared registry and ZK verifier instantly.