<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[New breakthrough results for quantum attack resource estimates against 256-bit elliptic curves: most ECC-based applications including ECDSA and Bitcoin could be at risk way sooner than expected:]]></title><description><![CDATA[<p>New breakthrough results for quantum attack resource estimates against 256-bit elliptic curves: most ECC-based applications including ECDSA and Bitcoin could be at risk way sooner than expected:</p><p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://research.google/blog/safeguarding-cryptocurrency-by-disclosing-quantum-vulnerabilities-responsibly/" title="Safeguarding cryptocurrency by disclosing quantum vulnerabilities responsibly">
<img src="https://storage.googleapis.com/gweb-research2023-media/images/Open_Graph.width-800.format-jpeg.jpg" class="card-img-top not-responsive" style="max-height: 15rem;" alt="Link Preview Image" />
</a>



<div class="card-body">
<h5 class="card-title">
<a href="https://research.google/blog/safeguarding-cryptocurrency-by-disclosing-quantum-vulnerabilities-responsibly/">
Safeguarding cryptocurrency by disclosing quantum vulnerabilities responsibly
</a>
</h5>
<p class="card-text line-clamp-3"></p>
</div>
<a href="https://research.google/blog/safeguarding-cryptocurrency-by-disclosing-quantum-vulnerabilities-responsibly/" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://www.gstatic.com/images/branding/googleg_gradient/1x/googleg_gradient_standard_20dp.png" alt="favicon" class="not-responsive overflow-hiddden" style="max-width: 21px; max-height: 21px;" />



<p class="d-inline-block text-truncate mb-0"> <span class="text-secondary">(research.google)</span></p>
</a>
</div></p><p>"We estimate that these circuits can be executed on a superconducting qubit CRQC with fewer than 500,000 physical qubits in a few minutes [...] This is an approximately 20-fold reduction in the number of physical qubits required to solve ECDLP-256"</p><p>I have been saying this since the 2010s: quantum cryptanalysis is one of those non-linear technology progresses that <em>will</em> take everyone by surprise when it arrives. Qubits quality and numbers go up, error-correction and attacks improve, investments scale up accordingly. It's a perfect storm of compound factors. Folks didn't listen, now time is ticking.</p><p><a href="https://infosec.exchange/tags/quantum" rel="tag">#<span>quantum</span></a> <a href="https://infosec.exchange/tags/quantumcomputing" rel="tag">#<span>quantumcomputing</span></a> <a href="https://infosec.exchange/tags/cryptography" rel="tag">#<span>cryptography</span></a> <a href="https://infosec.exchange/tags/security" rel="tag">#<span>security</span></a> <a href="https://infosec.exchange/tags/cybersecurity" rel="tag">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/infosec" rel="tag">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/google" rel="tag">#<span>google</span></a> <a href="https://infosec.exchange/tags/bitcoin" rel="tag">#<span>bitcoin</span></a> <a href="https://infosec.exchange/tags/blockchain" rel="tag">#<span>blockchain</span></a> <a href="https://infosec.exchange/tags/ethereum" rel="tag">#<span>ethereum</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/fefc9381-138d-455b-bc62-a5111c1b4cd5/new-breakthrough-results-for-quantum-attack-resource-estimates-against-256-bit-elliptic-curves-most-ecc-based-applications-including-ecdsa-and-bitcoin-could-be-at-risk-way-sooner-than-expected</link><generator>RSS for Node</generator><lastBuildDate>Thu, 16 Apr 2026 23:06:55 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/fefc9381-138d-455b-bc62-a5111c1b4cd5.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 31 Mar 2026 08:21:15 GMT</pubDate><ttl>60</ttl></channel></rss>