The primary record is CFTC: Designated Contract Market product filings from CFTC, published 31 August 2026. It confirms this specific point: CFTC's certified-product listing showed event contracts tied to passenger counts at airports including Las Vegas, Los Angeles, Miami, Denver, O'Hare, San Francisco, Orlando and Dallas/Fort Worth, with filings dated 31 August. The CFTC listing identifies a designated-contract-market product record and its stated status. It should not be described as an agency endorsement or proof that every related market is open to trade. A regulated venue's binary-payoff swap is also not automatically the same product as an offshore retail binary-options app; legal status and protections depend on the instrument, venue and jurisdiction. CFTC: Designated Contract Market product filings
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.
Passenger-count contracts depend on the data source, reporting period, revisions and threshold rule. Their market price can reflect both event probability and liquidity or contract-design effects. The yes-or-no payoff is only the surface of the contract. Reference data, cutoff time, revisions, cancellations, fees, liquidity and early exit rules determine how a market behaves. A price may reflect both beliefs and market structure. Contract-by-contract diligence is more reliable than inferring risk or legality from labels such as event contract, prediction market or binary option. Airport passenger totals can be published with a lag and may be revised or defined differently by each airport authority. A threshold market therefore depends on the exact reporting source and the period in the contract, not on a general view of air travel. The listing itself shows the product record; traders would need the underlying rule document and an independent check of the named data series to understand settlement exposure.
Passenger-count contracts depend on the data source, reporting period, revisions and threshold rule. Their market price can reflect both event probability and liquidity or contract-design effects. The yes-or-no payoff is only the surface of the contract. Reference data, cutoff time, revisions, cancellations, fees, liquidity and early exit rules determine how a market behaves. A price may reflect both beliefs and market structure. Contract-by-contract diligence is more reliable than inferring risk or legality from labels such as event contract, prediction market or binary option. Airport passenger totals can be published with a lag and may be revised or defined differently by each airport authority. A threshold market therefore depends on the exact reporting source and the period in the contract, not on a general view of air travel. The listing itself shows the product record; traders would need the underlying rule document and an independent check of the named data series to understand settlement exposure.
Read the individual rule submission for the airport, measurement window, official data source, rounding convention and treatment of delayed or revised reports. Before interpreting a listing, open its rule submission and identify the exact event, data source, threshold, measurement window and fallback for missing or corrected information. Then verify venue registration and customer protections independently. These checks explain what a contract means; they do not make the outcome predictable or remove the possibility of a total stake loss. These are CFTC-listed event-contract records, not evidence that offshore fixed-payout apps are regulated. Certification is not an agency endorsement or a guarantee of settlement accuracy. Certification status is a procedural fact, not an investment recommendation or guarantee of fair settlement. This article describes the filing record available on the stated date. It does not say an offshore provider is authorised, and it is not legal advice for a particular user's jurisdiction. For a practical contract review, save the exact rule version and write down the event, reference source, cutoff time, threshold and payout before considering a position. Confirm the venue and its regulator independently, and do not rely on a marketing label. If any settlement term is unclear, the payoff cannot be evaluated reliably, regardless of how simple the interface looks. A regulator's listing is a status check, not a determination of expected value.
What the latest source actually confirms
CFTC's certified-product listing showed event contracts tied to passenger counts at airports including Las Vegas, Los Angeles, Miami, Denver, O'Hare, San Francisco, Orlando and Dallas/Fort Worth, with filings dated 31 August. CFTC: Designated Contract Market product filings
The entries are listed as swaps with a binary-option payoff. A filing status and contract description identify the product record; they do not establish that every contract is open, liquid or suitable for retail users. The primary record is CFTC: Designated Contract Market product filings, dated 31 August 2026. It establishes the stated data point or announcement, while interpretation beyond that scope remains analysis.
Why the development matters—and what it cannot prove
Passenger-count contracts depend on the data source, reporting period, revisions and threshold rule. Their market price can reflect both event probability and liquidity or contract-design effects. The yes-or-no payoff is only the surface of the contract. Reference data, cutoff time, revisions, cancellations, fees, liquidity and early exit rules determine how a market behaves. A price may reflect both beliefs and market structure. Contract-by-contract diligence is more reliable than inferring risk or legality from labels such as event contract, prediction market or binary option. Airport passenger totals can be published with a lag and may be revised or defined differently by each airport authority. A threshold market therefore depends on the exact reporting source and the period in the contract, not on a general view of air travel. The listing itself shows the product record; traders would need the underlying rule document and an independent check of the named data series to understand settlement exposure.
The follow-up evidence that would change the picture
Read the individual rule submission for the airport, measurement window, official data source, rounding convention and treatment of delayed or revised reports. Before interpreting a listing, open its rule submission and identify the exact event, data source, threshold, measurement window and fallback for missing or corrected information. Then verify venue registration and customer protections independently. These checks explain what a contract means; they do not make the outcome predictable or remove the possibility of a total stake loss.
These are CFTC-listed event-contract records, not evidence that offshore fixed-payout apps are regulated. Certification is not an agency endorsement or a guarantee of settlement accuracy. Certification status is a procedural fact, not an investment recommendation or guarantee of fair settlement. This article describes the filing record available on the stated date. It does not say an offshore provider is authorised, and it is not legal advice for a particular user's jurisdiction.
For a practical contract review, save the exact rule version and write down the event, reference source, cutoff time, threshold and payout before considering a position. Confirm the venue and its regulator independently, and do not rely on a marketing label. If any settlement term is unclear, the payoff cannot be evaluated reliably, regardless of how simple the interface looks. A regulator's listing is a status check, not a determination of expected value.