Builders want to skip this chapter; traders cannot afford to. Compliance sits across everything you designed: resolution wording is a contract, liquidity subsidies can look like inducements, and oracle disputes touch commodities, gaming, and securities frames depending on jurisdiction. This lesson is structured risk mapping, not legal advice—hire counsel before you hold customer funds or list real-money events. Regulation was introduced as a payoff state in foundations; platform comparisons showed Kalshi’s CFTC lane versus crypto hybrids. Here you budget legal work like liquidity.
Legal access gates for traders apply symmetrically to builders: if your counsel says stop, marketing must stop too—no growth hack overrides a no.
Three questions counsel asks first
Who is the customer and where? Geo rules dominate; hand-waving buys freezes and fines. What is the product economically? Derivative, wager, research tool, or sweepstakes changes license path. Who holds funds and settles? Custody and dispute liability follow the entity that actually moves money.
Mechanism and oracle choices fit inside those answers—not the other way around.
Regulatory frames (US-centric, not exhaustive)
CFTC event contracts and designated contract market paths imply long lead times and heavy ongoing compliance—Kalshi is the familiar example. No-action or letter-limited experiments cap scale. State gaming law varies event by event for sportsbook-adjacent skins. Securities analysis hits tokenized shares with profit expectation. Sweepstakes and play-money lanes need prize limits and disclosures. Offshore crypto global stacks move fast but live under policy and banking fragility.
Labels shift when you add real USD, yield tokens, or election-only marketing—one feature change can move categories. This is why marketing and product must be reviewed together.
Product choices and sensitivity
Real USD custody is high sensitivity: money transmission and segregated customer funds. Crypto collateral is high sensitivity: sanctions, securities, and bridge risk. Play-money is medium: sweepstakes and youth policy. Internal corporate markets are medium: employment gambling rules. Free research APIs are lower but still carry misquote liability. Liquidity mining tokens and referral programs sit in high or medium-high buckets for promotions and broker-like optics. Political lists draw election-integrity scrutiny.
Geo and access as a product surface
Map allowed and blocked regions. Match KYC tier to product. Block VPN-only bypass if counsel requires it. Publish restricted-persons policy. Train support on consistent “why blocked” macros. Version terms of service when rules change. If legal access fails, stop—no growth spend fixes it.
Geo is not a back-office spreadsheet. It is part of the trader experience the same way fees are.
Resolution design is legal risk
“Wins election” without office and date invites disputes and media defamation risk. Subjective “consensus” is a litigation magnet. Cross-border offices include wrong electorates. Early resolution on non-final states enables trading on leaks. Ambiguous invalid forces refunds and anger. Counsel should review templates, not individual tweets—dispute chapters assumed tight text; builders supply it.
Marketing collisions
“Guaranteed profit” triggers enforcement and chargebacks. “Better than polls” without context misleads. “No risk first trade” sounds like gaming inducement. “Beat Vegas” reframes you as sportsbook. Anonymous whale stories signal AML gaps. Token “yield” promos raise securities optics. Safer copy teaches event probabilities, fees, and rule PDFs. Manipulation enforcement often starts with marketing screenshots.
AML and sanctions minimums
Know-your-customer and customer identification programs, sanctions screening, transaction monitoring especially during promo weeks, withdrawal holds with published policy, suspicious-activity reporting processes, and immutable audit trails for exams. On-chain labels do not end AML when fiat ramps exist.
Launch path illustration (hypothetical US builder)
Partnering on a licensed DCM might take eighteen to thirty-six months and serious capital but scales if approved. White-label regulated APIs take six to twelve months with rev share. Play-money plus sweepstakes can ship faster with promo counsel. Offshore crypto global can be weeks with geo-block discipline. Internal B2B pilots can be months with employment counsel. Launching on a platform buys time; it does not replace your license if you are the entity holding USD.
Same CPI headline across postures is not the same contract: US KYC’d USD segregated ops determination versus global USDC wallet with optimistic bonds versus play-money mana versus employee points under HR policy.
Data, privacy, and research use
KYC data touches privacy regimes; minimize retention. Trading logs face surveillance and subpoena. Public APIs create media liability if resolution strings are stripped. On-chain addresses are permanent; sanctions tooling still applies. Employee internal trades need HR confidentiality—aggregate reporting beats gossip dashboards.
Researchers want datasets with rule version IDs, not scraped mids divorced from PDFs.
Tail events and compliance budget
Oracle hacks, contract bugs, insolvency, and regulatory cease-fires are not theoretical—they are who pays questions. Segregation, templates, pause buttons, and wind-down playbooks belong beside maker rebates. Underfunded legal shows up as frozen withdrawals, not savings.
Trader-facing checklist
Am I legally allowed to trade here? Do I understand the resolution PDF? How are wins taxed and reported? What withdrawal holds exist? What happens on invalid? Does this promo change my edge net of fees? Treat access and rules as part of edge, not as paperwork after the fun part.
Wind-down and stress scenarios
Plan customer comms if the host pauses withdrawals, if stablecoin depegs, or if regulators inquire. A one-page wind-down script is cheaper than improvising during a crisis. Segregation and honest status pages reduce run risk.
Employment and insider policies
If employees trade internal or public political markets, publish who may trade what and when. HR and compliance should agree before internal pilots go live. Leaked positions are both legal and cultural failures.
Not legal advice, still mandatory
This chapter maps risks so you ask counsel better questions. Retain counsel before customer funds flow. Re-review when you add USD, change oracle type, or launch referral tokens. Law moves; your ToS version log should move with it.
Record-keeping for exams and subpoenas
Immutable trade logs, ToS version history, and marketing archive copies are boring until they are not. Build retention policy with counsel, not with Discord exports.
Key ideas
Answer who, what product, and who holds funds before scaling growth spend. Templates and geo policy are compliance products. Marketing can reclassify you—align copy with frames. Budget legal like liquidity; traders should treat access and PDFs as edge.
What comes next
Risk maps meet a scaling story: how a venue most traders already know moved from experiment to headline hybrid—and what to copy as phase pattern, not as license to ignore live terms.
Schedule a quarterly compliance review when product, oracle, or access changes. Treat it like patching production, not like optional paperwork. when product, oracle, or access changes—treat it like a security patch cadence, not a one-time memo.
Next: Case Study: How Polymarket Launched and Scaled