The CFTC published a proposed rule in June 2026 that would create an alternate reporting framework for certain fully collateralized event contracts. It would shift specified reporting obligations for some markets and intermediaries; the notice asks for comment and should not be described as a rule already in force. CFTC: Proposed data-reporting requirements for certain event contracts, 25 June 2026
Follow the evidence
Trace how the event could reach markets, then inspect a competing explanation.
Compare explanations
Switch lenses to see what each account explains—and what remains uncertain.
The proposal would replace some reliance on no-action letters with a specified reporting framework for a defined subset of event contracts.
The proposal would replace some reliance on no-action letters with a specified reporting framework for a defined subset of event contracts.
The measure is open to public comment and could be revised before any final requirements take effect.
The framework would change where certain reports are filed
The CFTC’s June 25 notice proposes amendments to Parts 15, 16 and 17 of its regulations. For certain fully collateralized event contracts, it sets out an alternate data-reporting framework for products that have been the subject of staff no-action letters since 2017. CFTC: Proposed data-reporting requirements for certain event contracts, 25 June 2026
Under the proposal, certain reporting markets, futures commission merchants, clearing members and foreign brokers would report specified contracts under Parts 15 through 18 instead of the reporting rules in certain provisions of Parts 38, 39, 43 and 45. The text describes proposed obligations, not a final legal change. CFTC: Proposed data-reporting requirements for certain event contracts, 25 June 2026
The CFTC framed the proposal as an effort to replace a patchwork of staff no-action letters with clearer rules. That is the agency’s stated rationale. The release alone does not show how commenters responded or whether the final framework will match the proposal. CFTC: Proposed data-reporting requirements for certain event contracts, 25 June 2026
Reporting systems matter even while the rule is under review
If adopted, a changed reporting route could require covered operators and intermediaries to map contracts to the right data fields, submission timelines and responsible entities. Firms may need to update contract identifiers, data lineage, reconciliations and escalation procedures so an event contract is not treated like a different product category by default.
The category does not make every event contract equivalent to an OTC binary option. Product structure, venue, collateral, clearing and governing rules differ. The proposal is narrowly described as covering certain fully collateralized event contracts and specified participants; its scope should not be generalized to every fixed-payout product.
A robust implementation would balance consistent reporting with enough product detail to support surveillance. But the consultation may produce changes or carve-outs, so an operator should not treat the proposed text as a final go-live specification.
Separate the proposal from the obligations already in force
Check the Federal Register notice and subsequent CFTC action for the comment period, any amendments, final-rule date and compliance timetable. The CFTC release labels the measure a Notice of Proposed Rulemaking and says it is seeking public comment. CFTC: Proposed data-reporting requirements for certain event contracts, 25 June 2026
Affected firms should map their current reporting duties against the proposed alternative and identify which products would meet the stated fully collateralized test. Legal and operations teams can document dependencies now without assuming that a future framework will be adopted unchanged.
For customers, the reporting proposal does not itself determine whether a particular event contract is permitted, fair or suitable. Review the venue’s contract specifications, settlement source, collateral arrangements and complaint process separately. A change in data reporting is not the same as a product endorsement or a customer-protection guarantee.