Kaynak doğrulamalı araştırma: Coinbase
Gövde metni doğrulanmış İngilizce kaynak dilinde gösteriliyor. Çeviri kaynak incelemesinden sonra eklenecek.
Direct answer
Coinbase's September 9 workshop report says Bitcoin post-quantum work is early: no precise threat date is known, no perfect solution has emerged, and migration would involve protocol, wallet, custody and hardware constraints. Draft BIPs discuss possible output and migration paths, while NIST has finalized general-purpose post-quantum standards. None of this proves Bitcoin is under an immediate quantum attack or that a specific proposal will be adopted.
Analizi kapat
Verified source facts
1. Coinbase says its September 2026 workshop produced no consensus on one post-quantum approach and did not identify an immediate crisis. 2. The workshop framed migration as a staged ecosystem process involving protocol design, wallets, custodians and hardware. 3. BIP 360 and BIP 361 are draft proposals, not deployed Bitcoin consensus rules. 4. NIST has finalized three general post-quantum cryptography standards, but Bitcoin adoption requires separate protocol and ecosystem decisions.
Comparison at a glance
Makale tablosu: yatay kaydırın veya tablo alanına odaklanıp ok tuşlarını kullanın.
| Decision layer | What to inspect | Minimum safe action |
|---|---|---|
| Threat timing | unknown date for a cryptographically relevant quantum computer | avoid countdown claims |
| Public-key exposure | outputs whose public keys are visible | inventory wallet practices without moving funds impulsively |
| Signature choice | security, size and performance tradeoffs | compare candidates under reproducible tests |
| Output design | draft quantum-resistant spending paths | label every BIP by current status |
| Legacy migration | handling vulnerable historical outputs | separate proposal from policy |
| Hardware wallets | memory, bandwidth and signing constraints | require device-vendor test evidence |
| Custody | institutional key generation and asset movement | design staged recovery drills |
| Standards | NIST algorithms versus Bitcoin-specific use | avoid equating standardization with integration |
| Governance | open review and broad coordination | track proposals and implementations separately |
| User action | preparation without panic | maintain good wallet hygiene and wait for validated guidance |
1. Control test: Threat timing
A trading-control disclosure is meaningful only when converted into a testable rule. For threat timing, inspect unknown date for a cryptographically relevant quantum computer. Use a sandbox, non-production context, or the smallest reversible test available, then avoid countdown claims. Capture configuration and event evidence without recording credentials, and verify the documented cancel, reject, decrement, or history behavior.
Model the failure path, not just the setup path. Ask which strategy owns the maker and taker orders, which account boundary the venue evaluates, which message reveals intervention, and how reconciliation behaves after a partial fill or disconnect. Platform documentation describes supported settings; it cannot prove that an operator configured them correctly. In this dimension, hardware progress is therefore an explicit audit gap.
The threat timing row should end with a concrete monitoring rule tied to unknown date for a cryptographically relevant quantum computer. Make the operator avoid countdown claims, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; hardware progress remains a separate production risk until observed.
2. Control test: Public-key exposure
For public-key exposure, inspect outputs whose public keys are visible. Use a sandbox, non-production context, or the smallest reversible test available, then inventory wallet practices without moving funds impulsively.
In this dimension, future attack capability is therefore an explicit audit gap.
The public-key exposure row should end with a concrete monitoring rule tied to outputs whose public keys are visible. Make the operator inventory wallet practices without moving funds impulsively, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; future attack capability remains a separate production risk until observed.
3. Control test: Signature choice
For signature choice, inspect security, size and performance tradeoffs. Use a sandbox, non-production context, or the smallest reversible test available, then compare candidates under reproducible tests.
In this dimension, eventual community preference is therefore an explicit audit gap.
The signature choice row should end with a concrete monitoring rule tied to security, size and performance tradeoffs. Make the operator compare candidates under reproducible tests, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; eventual community preference remains a separate production risk until observed.
4. Control test: Output design
For output design, inspect draft quantum-resistant spending paths. Use a sandbox, non-production context, or the smallest reversible test available, then label every BIP by current status.
In this dimension, consensus activation is therefore an explicit audit gap.
The output design row should end with a concrete monitoring rule tied to draft quantum-resistant spending paths. Make the operator label every BIP by current status, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; consensus activation remains a separate production risk until observed.
5. Control test: Legacy migration
For legacy migration, inspect handling vulnerable historical outputs. Use a sandbox, non-production context, or the smallest reversible test available, then separate proposal from policy.
In this dimension, treatment of unmigrated coins is therefore an explicit audit gap.
The legacy migration row should end with a concrete monitoring rule tied to handling vulnerable historical outputs. Make the operator separate proposal from policy, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; treatment of unmigrated coins remains a separate production risk until observed.
6. Control test: Hardware wallets
For hardware wallets, inspect memory, bandwidth and signing constraints. Use a sandbox, non-production context, or the smallest reversible test available, then require device-vendor test evidence.
In this dimension, upgrade coverage is therefore an explicit audit gap.
The hardware wallets row should end with a concrete monitoring rule tied to memory, bandwidth and signing constraints. Make the operator require device-vendor test evidence, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; upgrade coverage remains a separate production risk until observed.
7. Control test: Custody
For custody, inspect institutional key generation and asset movement. Use a sandbox, non-production context, or the smallest reversible test available, then design staged recovery drills.
In this dimension, operational migration capacity is therefore an explicit audit gap.
The custody row should end with a concrete monitoring rule tied to institutional key generation and asset movement. Make the operator design staged recovery drills, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; operational migration capacity remains a separate production risk until observed.
8. Control test: Standards
For standards, inspect NIST algorithms versus Bitcoin-specific use. Use a sandbox, non-production context, or the smallest reversible test available, then avoid equating standardization with integration.
In this dimension, Bitcoin implementation choice is therefore an explicit audit gap.
The standards row should end with a concrete monitoring rule tied to NIST algorithms versus Bitcoin-specific use. Make the operator avoid equating standardization with integration, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; Bitcoin implementation choice remains a separate production risk until observed.
9. Control test: Governance
For governance, inspect open review and broad coordination. Use a sandbox, non-production context, or the smallest reversible test available, then track proposals and implementations separately.
In this dimension, community consensus is therefore an explicit audit gap.
The governance row should end with a concrete monitoring rule tied to open review and broad coordination. Make the operator track proposals and implementations separately, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; community consensus remains a separate production risk until observed.
10. Control test: User action
For user action, inspect preparation without panic. Use a sandbox, non-production context, or the smallest reversible test available, then maintain good wallet hygiene and wait for validated guidance.
In this dimension, future official migration instructions is therefore an explicit audit gap.
The user action row should end with a concrete monitoring rule tied to preparation without panic. Make the operator maintain good wallet hygiene and wait for validated guidance, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; future official migration instructions remains a separate production risk until observed.
Decision scenarios
Scenario 1: when threat timing becomes decisive
Consider a reader whose main constraint is unknown date for a cryptographically relevant quantum computer. The correct response is not to infer a universal platform or product winner. It is to avoid countdown claims, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.
Scenario 2: when public-key exposure becomes decisive
Consider a reader whose main constraint is outputs whose public keys are visible. It is to inventory wallet practices without moving funds impulsively, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 3: when signature choice becomes decisive
Consider a reader whose main constraint is security, size and performance tradeoffs. It is to compare candidates under reproducible tests, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 4: when output design becomes decisive
Consider a reader whose main constraint is draft quantum-resistant spending paths. It is to label every BIP by current status, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 5: when legacy migration becomes decisive
Consider a reader whose main constraint is handling vulnerable historical outputs. It is to separate proposal from policy, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 6: when hardware wallets becomes decisive
Consider a reader whose main constraint is memory, bandwidth and signing constraints. It is to require device-vendor test evidence, retain the evidence, and define a stop condition before funds or permissions are committed.