Skip to content

Google Research — Safeguarding cryptocurrency by disclosing quantum vulnerabilities responsibly

Summary

Google Research lays out its disclosure philosophy for the 2026 quantum-attack-on-elliptic-curve-crypto result that Cloudflare's 2026-04-07 post cited second-hand. The framing: cryptocurrencies are not just decentralised data-processing systems — their value derives from digital security and public confidence, and both surfaces can be attacked. Naive "Full Disclosure" of a new quantum attack would hand the capability to adversaries; naive "No Disclosure" would deny the community the signal needed to accelerate migration. Worse, on a trust-sensitive substrate like a cryptocurrency, unsubstantiated resource estimates are themselves an attack — a FUD vector that can drain value from a blockchain without breaking its cryptography.

Google's structural answer is a composed disclosure primitive: (1) reduce FUD potential by clarifying the areas where blockchains are already immune to quantum attacks and by highlighting existing post-quantum progress in the blockchain ecosystem; (2) substantiate the new resource estimates without publishing the underlying quantum circuits by releasing a zero-knowledge proof that the improved algorithm exists with the claimed parameters — canonical wiki instance of ZKP-as-capability-disclosure. This is the producer-side counterpart to Cloudflare's consumer-side 2026-04-07 roadmap post: Google publishes the disclosure primitive and the philosophy behind it; Cloudflare shows the community-wide timeline-compression effect. The post names CERT/CC, Project Zero, and ISO/IEC 29147:2018 as prior-art norms and explicitly positions blockchain disclosure as new territory requiring further alignment with the quantum / security / cryptocurrency / policy communities.

The raw capture is the approach / philosophy portion of the post — the section motivating and framing the ZKP-based disclosure. Preceding sections with the actual updated resource estimates + the technical description of what is and isn't quantum-vulnerable on specific chains are not in the raw capture. The ingested content is therefore the disclosure-methodology landmark, not the ECDLP-256 resource-estimate technical paper.

Key takeaways

  1. Disclosure is a controversial, under-settled problem. The industry has converged on Responsible Disclosure / Coordinated Vulnerability Disclosure as a compromise between "No Disclosure" (attackers-instruction- manual risk) and "Full Disclosure" (defender-empowerment-via- transparency). The compromise ships the vulnerability with an embargo and a patch-deployment window. Google cites CERT/CC at Carnegie Mellon and Google's own Project Zero as premier institutions with strict-deadline variants, and ISO/IEC 29147:2018 as the international-standard codification. (Source: this article)

  2. Cryptocurrencies have a two-surface value model. A cryptocurrency's value derives from both the digital security of its network and the public confidence in the system. This is architecturally unlike a data-processing system — a bug in a database loses data; a loss of confidence in a cryptocurrency loses market capitalisation. Disclosure must account for both surfaces. (Source: this article)

  3. FUD is itself an attack primitive on trust-sensitive substrates. "Unscientific and unsubstantiated resource estimates for quantum algorithms breaking ECDLP-256 can themselves represent an attack on the system." On a cryptocurrency, anyone can drain value by eroding confidence without actually breaking any cryptography — publishing a dubious resource estimate is enough. This makes the quality and substantiation of a disclosure part of the responsible-disclosure contract on these substrates, not just its timing. (Source: this article)

  4. Reducing FUD potential is part of the disclosure itself. Google's first explicit FUD-mitigation move: "clarify the areas where blockchains are immune to quantum attacks" and "highlight the progress that has already been achieved towards post-quantum blockchain security." The disclosure is not just "here's a new attack" — it's bracketed by scope clarifications that bound how wide an attack lens should be applied and shows the ecosystem already has defensive motion under way. (Source: this article)

  5. ZKP substantiates without revealing. "We substantiate our resource estimates without sharing the underlying quantum circuits by publishing a state-of-the-art cryptographic construction called a zero-knowledge proof, which allows third parties to verify our claims without us leaking sensitive attack details." This is the producer-side statement of the disclosure primitive that Cloudflare's 2026-04-07 post described from the consumer side ("they did not reveal the algorithm, but instead provided a zero-knowledge proof that they have one"). Canonical wiki instance of patterns/zkp-capability-disclosure. (Source: this article; cross-ref: sources/2026-04-07-cloudflare-targets-2029-for-full-post-quantum-security)

  6. Blockchain disclosure is open territory. "We welcome further discussions with the quantum, security, cryptocurrency, and policy communities to align on responsible disclosure norms going forward." Explicitly declines to claim a finalised norm; positions ZKP-based disclosure as a contribution to an unresolved multi-community policy conversation. Unlike CVE / Project Zero, there is no established disclosure lifecycle for "we've improved the break of a primitive underlying $N trillion in assets". (Source: this article)

  7. Producer-side and consumer-side views are now both in the wiki. Google publishes the disclosure primitive and its philosophy (this post); Cloudflare's 2026-04-07 post shows the operational effect — community-wide Q-Day-timeline compression to 2029 and the resulting migration-roadmap pull-forward. The pair brackets a full production shape: ZKP capability disclosure → trusted signal → industry-wide timeline reassessment → accelerated PQC deployment. (Sources: this article + sources/2026-04-07-cloudflare-targets-2029-for-full-post-quantum-security)

Systems / concepts / patterns surfaced

Systems: (none — this post is about a disclosure methodology rather than a specific system; the underlying algorithm + its resource estimate are deliberately not published)

Concepts:

  • concepts/coordinated-disclosure — the baseline norm Google extends from the computer-security variant to the blockchain setting; the post explicitly re-derives why the compromise exists between No Disclosure and Full Disclosure.
  • concepts/zero-knowledge-proof — the mechanism of the disclosure primitive; producer-side framing complementing the consumer-side framing in the Cloudflare 2026-04-07 post.
  • concepts/post-quantum-cryptography — the defensive posture the disclosure aims to accelerate on blockchain substrates.
  • concepts/cryptographically-relevant-quantum-computer — the adversary capability the underlying resource estimates bound.
  • concepts/q-day — the operational threshold this disclosure influences the community's estimate of; same-arc timeline-compression move as the Cloudflare post.
  • concepts/fud-attack-surface — new concept introduced by this article: unsubstantiated claims as a trust-draining attack on systems whose value depends on public confidence.

Patterns:

  • patterns/zkp-capability-disclosure — new pattern made canonical by this post (producer side) and Cloudflare's 2026-04-07 post (consumer side): prove possession of a dangerous capability using a zero-knowledge proof instead of publishing the capability itself, so defenders update their threat models while adversaries gain no technical information.

Operational numbers

The raw capture is a methodology / philosophy section. The actual ECDLP-256 resource estimates the post produces (the substantiation the ZKP supports) are not present in the captured portion — the raw article appears to cover only the "Our approach to vulnerability disclosure" framing, not the numeric claims. Numbers cited elsewhere in the 2026 literature for context:

  • 2026-04-07 Cloudflare post (third-party summary): Oratomic estimate 10,000 qubits on neutral-atom hardware to break P-256, with 3-4 physical qubits per logical qubit under reconfigurable-code error correction vs ~1,000 on nearest-neighbour superconducting hardware. The algorithmic speed-up Google proves possession of via ZKP in this disclosure is a compounding factor on top of those hardware / error- correction improvements. (Source: sources/2026-04-07-cloudflare-targets-2029-for-full-post-quantum-security)
  • This post names the attack target as ECDLP-256 (the elliptic-curve discrete-log problem at the 256-bit parameter used by P-256 / secp256k1). secp256k1 is Bitcoin's curve; P-256 (aka secp256r1 / prime256v1) is the TLS / WebPKI default curve — so a practical break of ECDLP-256 impacts both blockchain assets and the classical web-PKI authentication substrate.

Caveats

  • Raw capture is partial. Only the "Our approach to vulnerability disclosure" section appears in the raw file. The preceding post-body content — updated resource estimates, the technical scope of blockchain quantum-immunity claims, specifics of the PQC progress in the blockchain ecosystem Google names — is not ingested. Future readers wanting the numbers should consult the original post.
  • ZKP construction not specified. The post states "state-of-the-art cryptographic construction called a zero-knowledge proof" without naming the specific proof system (SNARK / STARK / Bulletproofs / Halo / Plonk). Verifier parameters, proof size, verification cost, and soundness assumptions are not disclosed in the raw capture — important for third parties evaluating whether the proof is independently auditable.
  • Verification requires trusting what was proven. Per the ZKP-as- disclosure-primitive trust analysis on the zero-knowledge proof page: observers can mathematically verify the proof object, but the choice of what statement was proved, at what granularity, and with what calibration assumptions is Google's choice. This is explicitly acknowledged as "new territory" at the end of the captured portion.
  • Policy outcome open. The post ends with an open invitation for further discussion to align on norms, not with a proposed specification. No governance body, publication venue, or embargo window is claimed.
  • No operational incidents cited. The post frames the disclosure as pre-emptive — no specific cryptocurrency is named as having been attacked or compromised; no Bitcoin / Ethereum / other chain is called out as most-affected in the captured portion. Practitioners should not read a specific threat-to-a-specific-chain claim into this post.
  • The wiki's prior Google-Research tags around ML / scheduling / space infra are not extended here — this is a security-policy post from Google Research, which is a genre the wiki has not previously captured from this source.

Source

Last updated · 200 distilled / 1,178 read