Run embedded prize campaigns with publicly verifiable randomness, participant snapshots, and portable proof artifacts powered by Chainlink VRF.
01 — Problem
Prize campaigns still rely on opaque admin systems. Participants cannot verify whether the entrant pool changed, brands lack portable proof of fairness, and regulators receive screenshots instead of cryptographic audit trails.
Winner selection often happens in private backend systems where campaign participants cannot independently verify execution integrity.
Without pre-draw snapshots and commitment proofs, it is hard to show the participant set was final before randomness was requested.
Audit trails are frequently vendor-owned exports that cannot be validated outside the same platform that produced them.
Fraud and eligibility decisions are difficult to explain publicly when proof is fragmented across dashboards, spreadsheets, and support logs.
| Typical Campaign Stack | FairDraw |
|---|---|
| Opaque winner selection | Chainlink VRF randomness proof |
| Mutable entrant pools | Participant snapshot + hash commit |
| Platform-controlled logs | Portable FD-PROOF artifacts |
| Manual post-hoc reporting | Downloadable proof package |
| Weak public verification UX | Proof console + verification flow |
02 — Solution
FairDraw turns every campaign into a verifiable draw lifecycle: entrants are snapshotted, the participant set is hashed, Chainlink VRF produces randomness, and the final proof package can be downloaded and independently checked.
Core flow: configure campaign, embed widget, collect entries, snapshot participant set, commit participants hash, execute VRF draw, publish winner and proof artifacts.
Implementation status map: Live — Merchant Dashboard, Embed Widget, Chainlink VRF, FD-PROOF artifacts. Beta — Campaign API facade, allowed origins, key management facade, payment modes. Roadmap — ERC-1155 standard, SDK, public explorer, compliance modules, governance layer.
03 — Architecture
Current stack separates campaign operations, proof commitments, and randomness execution. Roadmap components are tracked explicitly as planned layers.
Product Surfaces
Current and emerging interfaces across the Gateway stack
3.5 — Live VRF Draw Sandbox
SIMULATION MODEStep through the complete Chainlink VRF draw lifecycle — from commitment creation to winner derivation. Every value is cryptographically derived and independently verifiable. No wallet required in simulation mode.
04 — Competitive Positioning
FairDraw is not a gambling operator or consumer lottery app. It is an infrastructure layer for businesses that need publicly verifiable prize campaign execution.
| Category | Traditional Giveaway Tools | RNG APIs | Smart Contract Lotteries | FairDraw |
|---|---|---|---|---|
| Embedded campaign UX | ~ Partial | ✗ | ✗ | ✓ |
| Public randomness proof | ✗ | ~ Partial | ✓ | ✓ |
| Participant snapshot proof | ✗ | ✗ | ~ Partial | ✓ |
| Merchant checkout support | ✓ | ✗ | ✗ | ✓ |
| Portable proof artifacts | ✗ | ✗ | ~ Partial | ✓ |
| Compliance tooling | ~ Partial | ✗ | ✗ | ~ Roadmap |
05 — Business Model
FairDraw can monetize through hosted campaign fees, verified draw execution, enterprise licensing, and future SDK/API usage tiers.
Pilot deployment package for brands and communities running verified prize campaigns.
Usage-based draw execution fee model for campaigns requiring public verification artifacts.
Subscription plan for advanced campaign workflows, team access, and operational controls.
Enterprise licensing for custom embedded campaign deployments and dedicated support needs.
Roadmap modules for compliance workflows, expanded reporting, and regulated deployment support.
Specific fee ranges and long-term economics are being validated through pilots. Any percentage-based fee references are target pricing ranges, not finalized public pricing.
06 — Proof Artifacts & Verification
Finished draws expose /api/draws/:lotteryId/proof and publish a portable FD-PROOF package that operators and third parties can independently validate.
| Capability | Status | Current Path | Roadmap Path |
|---|---|---|---|
| Merchant Dashboard | Live | Campaign setup + branding | Extended workflow templates |
| Campaign API facade | Beta | /api/merchant/campaigns | SDK/webhook integration |
| Proof Explorer | Roadmap | Proof console + downloads | Dedicated public domain |
07 — Risk & Regulatory Framework
FairDraw is designed as infrastructure, not as a prize operator. Merchants configure campaigns, define eligibility, handle payment and prize fulfillment, while FairDraw provides verifiable execution and proof tooling.
| Risk Factor | Level | Mitigation Strategy |
|---|---|---|
| Regulatory ambiguity | MEDIUM | Infrastructure positioning, merchant-controlled campaign terms, ongoing legal review. |
| Smart contract failure | MEDIUM | Testnet-first rollout, limited production scope, and external audit roadmap. |
| Oracle dependency | LOW/MED | Chainlink VRF v2.5 with fallback reconciliation and operational monitoring. |
| Market adoption pace | MEDIUM | Iframe-first integration, merchant dashboard workflow, and pilot campaign execution. |
| Compliance requirements | MEDIUM | Eligibility rules, audit artifacts, and compliance modules roadmap. |
FairDraw does not operate campaigns as principal. Merchants define campaign terms, eligibility, and fulfillment while FairDraw provides verifiable execution infrastructure.
Custody and payout paths differ by payment mode. FairDraw focuses on draw integrity and proof portability, while merchant-side payment and fulfillment controls remain explicit.
Region rollout is staged by merchant profile and legal readiness, with campaign terms and eligibility rules configurable per deployment context.
Formal external smart contract audit remains on roadmap. Current operations prioritize bounded scope, controlled deployment paths, and reproducible proof artifacts.
FairDraw emits verifiable randomness and commitment evidence. Campaign-specific eligibility, business rules, and prize delivery remain merchant-managed.
08 — Moat & Defensibility
Defensibility in infrastructure is built through accumulation: data, integrations, compliance tooling, and switching costs that compound over time. No single moat is claimed — but the combination forms a durable competitive position.
Portable FD-PROOF artifacts create a consistent verification surface that merchants, auditors, and partners can adopt across campaign types.
Proof console and verification flows reduce friction between campaign execution and external trust checks.
Dashboard setup, embed deployment, and draw execution workflow reduce integration overhead and improve repeatability for operators.
Accumulating campaign and draw history improves operational quality, replayability, and proof consistency over time.
Eligibility, fraud signals, and audit workflow improvements compound with each deployment and reduce marginal compliance effort.
Operators that run repeated embedded campaigns build process and data dependencies that increase switching cost over time.
09 — Roadmap
Phase 01 · 2026: Gateway MVP with merchant dashboard, embed widget, VRF proof flow, and FD-PROOF artifacts.
Phase 02 · 2026/2027: Public explorer, SDK, webhooks, compliance modules, and production pilot expansion.
Phase 03 · 2027+: Protocol-grade standard with multi-chain support, third-party builders, and advanced settlement options.
Roadmap modules: ERC-1155 ticket standard, enterprise compliance packs, governance/tokenized fairness options, and cross-chain expansion.
10 — Vision
FairDraw starts as a merchant gateway for verifiable campaigns and evolves into a protocol-grade proof layer for digital prize allocation.
Merchant dashboard, embed widget, Chainlink VRF proof flow, participant snapshot commit, and portable FD-PROOF artifact package.
Public explorer, SDK/webhooks, expanded compliance tooling, and production pilots across multiple merchant environments.
Multi-chain support, third-party builders, and advanced settlement or governance options where legally and operationally appropriate.
Review the current gateway stack, proof flow, and roadmap direction from live capability to protocol-grade verification.