Ricerca verificata da fonti: Coinbase
Il corpo dell'articolo è mostrato nell'originale inglese verificato. La traduzione sarà aggiunta dopo la revisione delle fonti.
Direct answer
Coinbase's September 9 workshop report says Bitcoin developers, cryptographers, institutions and hardware-wallet experts are evaluating post-quantum signature tradeoffs and migration paths. This is preparedness work, not evidence that practical quantum theft is occurring now or that one proposal has been selected. Custodians should inventory address exposure, key-rotation authority, hardware and signer dependencies, upgrade governance and tested recovery paths without making unsupported emergency claims.
Mostra meno
Verified source facts
1. Coinbase says it convened a September 2026 workshop with Bitcoin developers, cryptographers, institutions and hardware-wallet experts. 2. The workshop considered post-quantum signature tradeoffs, lessons from other ecosystems and operational requirements for institutional custody. 3. Coinbase describes the work as advancing preparation and carefully tested solutions, not declaring a selected Bitcoin migration design. 4. NIST publishes post-quantum cryptography standards and migration resources for cryptographic systems generally.
Comparison at a glance
Tabella dell’articolo: scorri in orizzontale oppure porta il focus sull’area della tabella e usa i tasti freccia.
| Decision layer | What to inspect | Minimum safe action |
|---|---|---|
| Threat claim | current evidence versus future capability | separate observed facts from scenarios |
| Address exposure | public-key revelation and address reuse | inventory address classes |
| Signature option | security, size and verification cost | compare measured tradeoffs |
| Consensus path | protocol change and activation | map governance dependencies |
| Custody authority | who can approve key migration | document quorum and emergency powers |
| Hardware | wallet, HSM and signer support | inventory upgradeability |
| Recovery | lost device and failed migration | test non-secret runbooks |
| Legacy funds | inactive or inaccessible outputs | define handling principles |
| Communication | avoiding panic and false certainty | publish evidence-labelled updates |
| Exercise | tabletop and test-environment migration | run a reversible drill |
1. Usage and measurement test: Threat claim
Stablecoin adoption cannot be inferred from a single gross counter. The threat claim dimension concerns current evidence versus future capability. Define the economic job, unit of observation, time window and entities included before counting, then separate observed facts from scenarios. 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 quantum timeline. The dataset and classification method therefore belong beside every headline number.
For threat claim, publish the numerator, denominator and exclusions that support the claim. Make the analyst separate observed facts from scenarios, and compare at least one activity metric with one outcome metric relevant to current evidence versus future capability. Because quantum timeline remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
2. Usage and measurement test: Address exposure
The address exposure dimension concerns public-key revelation and address reuse. Define the economic job, unit of observation, time window and entities included before counting, then inventory address classes.
Official sources can frame the categories, but they do not resolve future attack economics.
For address exposure, publish the numerator, denominator and exclusions that support the claim. Make the analyst inventory address classes, and compare at least one activity metric with one outcome metric relevant to public-key revelation and address reuse. Because future attack economics remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
3. Usage and measurement test: Signature option
The signature option dimension concerns security, size and verification cost. Define the economic job, unit of observation, time window and entities included before counting, then compare measured tradeoffs.
Official sources can frame the categories, but they do not resolve selected Bitcoin design.
For signature option, publish the numerator, denominator and exclusions that support the claim. Make the analyst compare measured tradeoffs, and compare at least one activity metric with one outcome metric relevant to security, size and verification cost. Because selected Bitcoin design remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
4. Usage and measurement test: Consensus path
The consensus path dimension concerns protocol change and activation. Define the economic job, unit of observation, time window and entities included before counting, then map governance dependencies.
Official sources can frame the categories, but they do not resolve activation timing.
For consensus path, publish the numerator, denominator and exclusions that support the claim. Make the analyst map governance dependencies, and compare at least one activity metric with one outcome metric relevant to protocol change and activation. Because activation timing remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
5. Usage and measurement test: Custody authority
The custody authority dimension concerns who can approve key migration. Define the economic job, unit of observation, time window and entities included before counting, then document quorum and emergency powers.
Official sources can frame the categories, but they do not resolve future stakeholder access.
For custody authority, publish the numerator, denominator and exclusions that support the claim. Make the analyst document quorum and emergency powers, and compare at least one activity metric with one outcome metric relevant to who can approve key migration. Because future stakeholder access remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
6. Usage and measurement test: Hardware
The hardware dimension concerns wallet, HSM and signer support. Define the economic job, unit of observation, time window and entities included before counting, then inventory upgradeability.
Official sources can frame the categories, but they do not resolve vendor delivery.
For hardware, publish the numerator, denominator and exclusions that support the claim. Make the analyst inventory upgradeability, and compare at least one activity metric with one outcome metric relevant to wallet, HSM and signer support. Because vendor delivery remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
7. Usage and measurement test: Recovery
The recovery dimension concerns lost device and failed migration. Define the economic job, unit of observation, time window and entities included before counting, then test non-secret runbooks.
Official sources can frame the categories, but they do not resolve exception outcome.
For recovery, publish the numerator, denominator and exclusions that support the claim. Make the analyst test non-secret runbooks, and compare at least one activity metric with one outcome metric relevant to lost device and failed migration. Because exception outcome remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
8. Usage and measurement test: Legacy funds
The legacy funds dimension concerns inactive or inaccessible outputs. Define the economic job, unit of observation, time window and entities included before counting, then define handling principles.
Official sources can frame the categories, but they do not resolve owner participation.
For legacy funds, publish the numerator, denominator and exclusions that support the claim. Make the analyst define handling principles, and compare at least one activity metric with one outcome metric relevant to inactive or inaccessible outputs. Because owner participation remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
9. Usage and measurement test: Communication
The communication dimension concerns avoiding panic and false certainty. Define the economic job, unit of observation, time window and entities included before counting, then publish evidence-labelled updates.
Official sources can frame the categories, but they do not resolve media distortion.
For communication, publish the numerator, denominator and exclusions that support the claim. Make the analyst publish evidence-labelled updates, and compare at least one activity metric with one outcome metric relevant to avoiding panic and false certainty. Because media distortion remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
10. Usage and measurement test: Exercise
The exercise dimension concerns tabletop and test-environment migration. Define the economic job, unit of observation, time window and entities included before counting, then run a reversible drill.
Official sources can frame the categories, but they do not resolve mainnet conditions.
For exercise, publish the numerator, denominator and exclusions that support the claim. Make the analyst run a reversible drill, and compare at least one activity metric with one outcome metric relevant to tabletop and test-environment migration. Because mainnet conditions remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
Decision scenarios
Scenario 1: when threat claim becomes decisive
Consider a reader whose main constraint is current evidence versus future capability. The correct response is not to infer a universal platform or product winner. It is to separate observed facts from scenarios, 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 address exposure becomes decisive
Consider a reader whose main constraint is public-key revelation and address reuse. It is to inventory address classes, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 3: when signature option becomes decisive
Consider a reader whose main constraint is security, size and verification cost. It is to compare measured tradeoffs, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 4: when consensus path becomes decisive
Consider a reader whose main constraint is protocol change and activation. It is to map governance dependencies, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 5: when custody authority becomes decisive
Consider a reader whose main constraint is who can approve key migration. It is to document quorum and emergency powers, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 6: when hardware becomes decisive
Consider a reader whose main constraint is wallet, HSM and signer support. It is to inventory upgradeability, retain the evidence, and define a stop condition before funds or permissions are committed.
Sources and editorial method
- Moving Bitcoin's Post-Quantum Readiness Forward — Coinbase
- Post-Quantum Cryptography — NIST
- Post-Quantum Cryptography Standardization — NIST CSRC