Quellengeprüfte Recherche: Coinbase Derivatives CASH Settled
Der Artikeltext wird im geprüften englischen Original angezeigt. Die Übersetzung folgt nach der Quellenprüfung.
Direct answer
Coinbase Derivatives filed proposed rules on September 18, 2026 for cash-settled futures on individual equities and ETF shares, including perpetual single-stock futures. The SEC notice says the proposal was filed concurrently with the CFTC and that the CFTC had not yet approved it. This is a rule filing, not evidence that every product is live or available in every jurisdiction. Decision-makers should separate filing status, regulatory approval, contract launch, customer eligibility, settlement methodology, margin, trading hours and underlying corporate-action treatment.
Weniger anzeigen
Verified source facts
1. Coinbase Derivatives filed SR-COIN-2026-002 on September 18, 2026. 2. The filing concerns cash-settled futures on individual equity securities and ETF shares, including perpetual single-stock futures. 3. The SEC notice says the filing was made concurrently with the CFTC and that CFTC approval had not yet occurred. 4. The SEC rulemaking page states that comments are due 21 days after Federal Register publication.
Comparison at a glance
Artikeltabelle: horizontal scrollen oder den Tabellenbereich fokussieren und die Pfeiltasten verwenden.
| 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. Rights analysis: Status
Tokenization analysis must follow the legal and operational chain, not the visual token. The status question asks about announced, filed or live. Identify the issuer, tokenization sponsor, recordkeeper, custodian, broker or platform, and every agreement connecting them. Then verify milestone. A wallet balance alone cannot answer which person or system has the enforceable obligation.
Test the arrangement under a disagreement. If the chain record and master securityholder file diverge, which one controls? If an intermediary fails, is the holder a customer, beneficial owner, secured claimant, or unsecured creditor? If a transfer is technically possible but legally restricted, what process reverses or freezes it? The available sources frame these questions, while premature conclusion remains outside the evidence set.
Turn the status finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Verify milestone before comparing yield, speed, or interface quality. Because premature conclusion is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
2. Rights analysis: Time
The time question asks about official UTC timestamp. Then convert locally.
The available sources frame these questions, while missed cutoff remains outside the evidence set.
Turn the time finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Convert locally before comparing yield, speed, or interface quality. Because missed cutoff is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
3. Rights analysis: Eligibility
The eligibility question asks about jurisdiction and account type. Then check access.
The available sources frame these questions, while blocked action remains outside the evidence set.
Turn the eligibility finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Check access before comparing yield, speed, or interface quality. Because blocked action is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
4. Rights analysis: Instrument
The instrument question asks about spot, future or tokenized claim. Then identify legal form.
The available sources frame these questions, while category error remains outside the evidence set.
Turn the instrument finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Identify legal form before comparing yield, speed, or interface quality. Because category error is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
5. Rights analysis: Execution
The execution question asks about book, pool or matching mode. Then inspect mechanism.
The available sources frame these questions, while fill surprise remains outside the evidence set.
Turn the execution finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Inspect mechanism before comparing yield, speed, or interface quality. Because fill surprise is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
6. Rights analysis: Fees
The fees question asks about published schedule. Then calculate total cost.
The available sources frame these questions, while cost overrun remains outside the evidence set.
Turn the fees finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Calculate total cost before comparing yield, speed, or interface quality. Because cost overrun is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
7. Rights analysis: Liquidity
The liquidity question asks about venue and symbol specific. Then check depth.
The available sources frame these questions, while slippage remains outside the evidence set.
Turn the liquidity finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Check depth before comparing yield, speed, or interface quality. Because slippage is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
8. Rights analysis: Operations
The operations question asks about deposit, withdrawal or settlement. Then verify live status.
The available sources frame these questions, while stuck funds remains outside the evidence set.
Turn the operations finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Verify live status before comparing yield, speed, or interface quality. Because stuck funds is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
9. Rights analysis: Evidence
The evidence question asks about primary notice and file number. Then retain source.
The available sources frame these questions, while audit gap remains outside the evidence set.
Turn the evidence finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Retain source before comparing yield, speed, or interface quality. Because audit gap is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
10. Rights analysis: Stop rule
The stop rule question asks about material fact remains unverified. Then pause and confirm.
The available sources frame these questions, while unsupported decision remains outside the evidence set.
Turn the stop rule finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Pause and confirm before comparing yield, speed, or interface quality. Because unsupported decision is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
Sources and editorial method
Themen und Tools:Funding Rates für Perpetuals