Legal & Regulatory Analysis

analysis_l.md

Legal & Regulatory Analysis — Commercializing KalshiTrader

Research memo, 2026-08. Not legal advice. This summarizes public sources to frame a conversation with a fintech/derivatives lawyer before charging money.

1. The regulatory frame

Kalshi is a CFTC-designated contract market (DCM); its event contracts are federally regulated derivatives ("commodity interests" under the Commodity Exchange Act). Two consequences:

Anyone giving advice about trading them for compensation is presumptively a Commodity Trading Advisor (CTA) under the CEA — the CFTC/NFA regime, not the SEC one.
The space is in active jurisdictional flux (see §5): several states are litigating whether event contracts are actually gambling under state law. Product decisions should assume the federal frame but avoid building anything that only works if the state fights all resolve Kalshi's way.

2. What we can sell WITHOUT registration (the safe lane)

CFTC Rule 4.14(a)(9) exempts from CTA registration those who provide standardized commodity trading advice through media — newsletters, web sites, and non-customized computer software — provided they:

do not tailor advice to any particular client's positions or circumstances, and
do not direct client accounts (no authority to effect transactions for a client).

This maps cleanly onto the products we discussed:

Product	Registration posture
Discovery feed / novel-market alerts (Discord, push, API)	Pure market information, not even advice — safest tier
Analytics pages, volatility stats, backtest tooling	Standardized software/data — squarely 4.14(a)(9) territory
Signal tape ("our paper strategy bought X at 8¢"), same to every subscriber	Standardized advice — 4.14(a)(9), keep it identical for all users
Software users run on their own Kalshi keys, configured by them	Non-customized software — defensible under 4.14(a)(9); the user directs their own account

Supporting exemption: 4.14(a)(10) (advice to ≤15 persons in 12 months and no holding out as a CTA) — useful during a private beta phase.

Practical obligations even in the safe lane:

File the NFA exemption notice electronically if relying on a Part 4 exemption (NFA Exemptions System).
Prominent, honest disclaimers: informational only, not tailored advice, performance shown includes fees, past performance ≠ future results. The CFTC has a long enforcement history around hypothetical performance claims — every backtest/paper number we publish should be labeled hypothetical/simulated and fee-inclusive (which is exactly why the fee modeling work matters commercially, not just analytically).
No cherry-picking: publish the whole signal record, not winners.

3. What CROSSES the line (registration territory)

Auto-trading other people's accounts ("give us your API key, our engine trades for you"): that is directing client accounts — the exact thing 4.14(a)(9) excludes. Presumptively requires CTA registration (NFA membership, Series 3, disclosure documents, recordkeeping) once past the de-minimis exemptions.
Pooling customer money to trade (a fund): Commodity Pool Operator (CPO) territory — heavier still.
Tailored advice (adjusting signals per-user based on their positions, bankroll, risk tolerance): breaks the "standardized" prong.

If autopilot-on-user-funds ever becomes the product, budget for registration or structure it so the user's own software instance executes with the user's own key under the user's own configuration — the further the platform is from touching keys/orders on a user's behalf, the stronger the posture. (A hosted multi-tenant service that holds users' API keys and fires their orders sits in a gray zone that needs real counsel — this is the #1 question to bring to a lawyer.)

4. Kalshi-side rules

Kalshi explicitly supports API/automated trading (documented REST/FIX, signed requests, official SDKs); third-party tools and bots exist openly.
Standard conduct rules apply: no manipulation, wash trading, spoofing, self-matching; respect rate limits; account holders must meet jurisdiction/eligibility rules.
Terms evolve — re-review Kalshi's ToS before launching anything commercial, and particularly before anything resembling shared/managed account access (Kalshi's terms govern per-account API key usage).

5. Background risk: the state-law fight (2026 status)

CFTC asserts exclusive jurisdiction over event contracts and in June 2026 proposed new rules (Rule 40.11 changes + a public-interest review framework) that will reshape which contracts are listable.
Mixed litigation outcomes: Third Circuit (Apr 2026) upheld an injunction blocking New Jersey from enforcing gambling law against Kalshi's sports contracts; a federal court blocked Arizona's criminal prosecution on preemption grounds; but a Nevada state court enjoined Kalshi and Polymarket from offering sports/election/entertainment contracts to Nevada residents.
Implication for us: market availability can change by state and by category. Sports/election categories carry the most regulatory volatility; crypto/economics categories the least. A signals business should not be existentially dependent on the contested categories, and any user-facing product should geo-disclaim rather than promise availability.

6. Recommended posture (pending counsel)

Ship: discovery alerts, analytics, standardized signal feed, self-hosted/self-keyed software. Identical content to every subscriber.
File the NFA exemption notice when the signal product takes money.
Label all performance as simulated/hypothetical where applicable, always fee-inclusive, full history visible.
Defer: hosted autopilot on customer keys and anything pooled until a derivatives lawyer scopes CTA registration (~the one paid consult worth doing early).
Monitor: the CFTC's 2026 rulemaking and the state cases — mostly a product-category risk, not an existential one for a crypto-centric tool.

Sources

← Signals Feed API