Broadridge announced on October 29 that Kalshi event contracts can now be traded through the front ends and APIs of CQG, its futures and options platform, and will reach buy-side firms on the NYFIX network. I think the interesting part of that announcement is the plumbing. Once event contracts sit in the same screen as futures and equities, the rules for who may trade them become a broker’s job.
Distribution is the story
The release says brokers and futures commission merchants can offer clients direct trading access and market data, and that trading access will extend to more than 1,700 buy-side clients that use NYFIX for connectivity. It describes the aim as bringing prediction markets “directly into established trading workflows”. That is a distribution deal. Kalshi keeps its exchange and Broadridge supplies the places where orders originate.
Ryan Moroney, CEO of CQG, put the pitch plainly: “With Kalshi live on CQG, we’re bringing that opportunity to a platform our clients already trust, alongside the markets they already trade.” I take him at his word about the trust. My argument concerns what the same trust has to cover now.
Advertisement
A front end carries the compliance duties of whatever it lists
A trader who sees an event contract next to a crude oil future will assume it has been vetted by the same desk. The release says as much about eligibility, noting that the launch responds to client demand in the United States and EMEA, “with access subject to applicable eligibility and jurisdictional requirements.” Those two requirements decide who gets the contract on screen, and the broker or FCM enforces both.
That is a harder job than listing a new futures contract. The legal footing of event contracts in the United States is still moving. As we reported when the Commodity Futures Trading Commission proposed naming event contracts as swaps, federal and state authorities disagree about where the line sits, and the question is in rulemaking. A broker that switches event contracts on across all its clients today is deciding, account by account, a question regulators have not finished answering.
What I would want a broker to do
I would want three things in place before a client sees the first event contract. The first is a jurisdiction gate at the account level, so that eligibility is a stored attribute of the client and not a disclaimer on a screen. The second is the same position monitoring, limits and surveillance that a firm applies to its other derivatives, because the release itself promises “portfolio monitoring tools” for these positions and a monitored position needs someone responsible for reading the alerts. The third is a written record of which clients had access and when, because that record is what a regulator is likely to ask for first.
None of this is exotic. It is the ordinary work of onboarding and supervision, applied to a product that arrives with more public attention than most. The release itself notes that prediction markets are attracting “growing attention from investors and policymakers.”
The strongest objection
The best counter-argument is that event contracts are one more instrument. The front end is a neutral pipe. If Kalshi is a regulated exchange and CQG routes to it, the argument goes, the broker’s obligations are the ones it has for any exchange-listed product, and nothing new is needed.
I accept the first half. A routing layer is a routing layer. The second half fails on the release’s own words. Kalshi’s Andy Ross says traders can “precisely hedge their exposure” with these contracts, which makes the product a hedging instrument for some clients and a speculative one for others. A broker has to know which of its clients is which before it describes the contract to them, and that is a suitability question that a neutral pipe does not answer for it.
What buyers of this technology should ask
Trading-platform buyers should press any vendor that adds event contracts on three points. Eligibility by jurisdiction should live in the platform as client data. A compliance officer should be able to switch the product off for a single client or a single state without a code change. The surveillance engine should see event-contract orders with the same fields as futures orders. A vendor that meets the first two with a configuration screen has done the plumbing. A vendor that meets them with a disclaimer has handed the problem to the broker.
Broadridge says the launch expands its multi-asset trading offering. If event contracts keep arriving through established platforms, the firms that win business will be the ones whose compliance tooling arrives with the product, because the front end is now where the supervision happens.
