Riset terverifikasi sumber: Coinbase Bitnomial Kalshi Security
Isi artikel ditampilkan dalam bahasa Inggris asli yang telah diverifikasi. Terjemahan ditambahkan setelah tinjauan sumber.
Direct answer
The SEC's September 18 what's-new feed lists separate security-futures filings from Coinbase Derivatives, Bitnomial Exchange and KalshiEX. The filings address different rule sets, including product rules, listing standards and customer margin, so they should not be collapsed into a claim that one uniform market has launched. Investors and operators should track each file number, regulatory pathway, effective or approval status, product specifications, margin model, eligible participants and actual launch notice before drawing conclusions about access or liquidity.
Tampilkan lebih sedikit
Verified source facts
1. The SEC what's-new feed lists three security-futures-related filings dated September 18, 2026. 2. The listed organizations are Coinbase Derivatives, Bitnomial Exchange and KalshiEX. 3. The Coinbase filing includes cash-settled individual-equity and ETF futures, including perpetual single-stock futures. 4. Filing publication, regulatory approval, product launch and customer availability are distinct milestones.
Comparison at a glance
Tabel artikel: gulir secara horizontal atau fokuskan area tabel dan gunakan tombol panah.
| Decision layer | What to inspect | Minimum safe action |
|---|---|---|
| Status | announced, filed or live | verify milestone |
| Time | official UTC timestamp | convert locally |
| Eligibility | jurisdiction and account type | check access |
| Instrument | spot, future or tokenized claim | identify legal form |
| Execution | book, pool or matching mode | inspect mechanism |
| Fees | published schedule | calculate total cost |
| Liquidity | venue and symbol specific | check depth |
| Operations | deposit, withdrawal or settlement | verify live status |
| Evidence | primary notice and file number | retain source |
| Stop rule | material fact remains unverified | pause and confirm |
1. Usage and measurement test: Status
Stablecoin adoption cannot be inferred from a single gross counter. The status dimension concerns announced, filed or live. Define the economic job, unit of observation, time window and entities included before counting, then verify milestone. Otherwise one routed transaction, exchange rebalance or contract hop may be mistaken for several independent users or payments.
Separate ledger events from economic outcomes. A transfer can be real on-chain yet still represent internal treasury movement, automated arbitrage, bridge routing, collateral management or redemption rather than a purchase. Official sources can frame the categories, but they do not resolve premature conclusion. The dataset and classification method therefore belong beside every headline number.
For status, publish the numerator, denominator and exclusions that support the claim. Make the analyst verify milestone, and compare at least one activity metric with one outcome metric relevant to announced, filed or live. Because premature conclusion remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
2. Usage and measurement test: Time
The time dimension concerns official UTC timestamp. Define the economic job, unit of observation, time window and entities included before counting, then convert locally.
Official sources can frame the categories, but they do not resolve missed cutoff.
For time, publish the numerator, denominator and exclusions that support the claim. Make the analyst convert locally, and compare at least one activity metric with one outcome metric relevant to official UTC timestamp. Because missed cutoff remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
3. Usage and measurement test: Eligibility
The eligibility dimension concerns jurisdiction and account type. Define the economic job, unit of observation, time window and entities included before counting, then check access.
Official sources can frame the categories, but they do not resolve blocked action.
For eligibility, publish the numerator, denominator and exclusions that support the claim. Make the analyst check access, and compare at least one activity metric with one outcome metric relevant to jurisdiction and account type. Because blocked action remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
4. Usage and measurement test: Instrument
The instrument dimension concerns spot, future or tokenized claim. Define the economic job, unit of observation, time window and entities included before counting, then identify legal form.
Official sources can frame the categories, but they do not resolve category error.
For instrument, publish the numerator, denominator and exclusions that support the claim. Make the analyst identify legal form, and compare at least one activity metric with one outcome metric relevant to spot, future or tokenized claim. Because category error remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
5. Usage and measurement test: Execution
The execution dimension concerns book, pool or matching mode. Define the economic job, unit of observation, time window and entities included before counting, then inspect mechanism.
Official sources can frame the categories, but they do not resolve fill surprise.
For execution, publish the numerator, denominator and exclusions that support the claim. Make the analyst inspect mechanism, and compare at least one activity metric with one outcome metric relevant to book, pool or matching mode. Because fill surprise remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
6. Usage and measurement test: Fees
The fees dimension concerns published schedule. Define the economic job, unit of observation, time window and entities included before counting, then calculate total cost.
Official sources can frame the categories, but they do not resolve cost overrun.
For fees, publish the numerator, denominator and exclusions that support the claim. Make the analyst calculate total cost, and compare at least one activity metric with one outcome metric relevant to published schedule. Because cost overrun remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
7. Usage and measurement test: Liquidity
The liquidity dimension concerns venue and symbol specific. Define the economic job, unit of observation, time window and entities included before counting, then check depth.
Official sources can frame the categories, but they do not resolve slippage.
For liquidity, publish the numerator, denominator and exclusions that support the claim. Make the analyst check depth, and compare at least one activity metric with one outcome metric relevant to venue and symbol specific. Because slippage remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
8. Usage and measurement test: Operations
The operations dimension concerns deposit, withdrawal or settlement. Define the economic job, unit of observation, time window and entities included before counting, then verify live status.
Official sources can frame the categories, but they do not resolve stuck funds.
For operations, publish the numerator, denominator and exclusions that support the claim. Make the analyst verify live status, and compare at least one activity metric with one outcome metric relevant to deposit, withdrawal or settlement. Because stuck funds remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
9. Usage and measurement test: Evidence
The evidence dimension concerns primary notice and file number. Define the economic job, unit of observation, time window and entities included before counting, then retain source.
Official sources can frame the categories, but they do not resolve audit gap.
For evidence, publish the numerator, denominator and exclusions that support the claim. Make the analyst retain source, and compare at least one activity metric with one outcome metric relevant to primary notice and file number. Because audit gap remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
10. Usage and measurement test: Stop rule
The stop rule dimension concerns material fact remains unverified. Define the economic job, unit of observation, time window and entities included before counting, then pause and confirm.
Official sources can frame the categories, but they do not resolve unsupported decision.
For stop rule, publish the numerator, denominator and exclusions that support the claim. Make the analyst pause and confirm, and compare at least one activity metric with one outcome metric relevant to material fact remains unverified. Because unsupported decision remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.