IonQ CEO Niccolo de Masi gave Cantor Convergence a striking timeline for the quantum threat to today's cryptography. In a November 11 conversation with Fortune's Jeff John Roberts, he linked the company's roadmap to machines that he believes could attack elliptic-curve cryptography around 2028 in the lab and 2029 in real-world use.
That is a forecast from a company building quantum technology, not a demonstrated break of the systems protecting financial networks today. The distinction is central to understanding what investors and technology teams should take from the discussion.
The company-published transcript records de Masi citing a 20,000-qubit resource estimate and suggesting that RSA-2048 could follow approximately a year later on IonQ's roadmap. He also said further algorithmic progress could change the hardware requirements and timing.
Post from @NiccoloDeMasiView the original post on X↗
A roadmap is not a countdown clock
A proposed architecture, an estimate of required resources and a working machine capable of the attack are different things. The Cantor remarks establish what IonQ's chief executive expects; they do not independently validate that the company will reach those dates.
There is another reason to read the comments carefully. IonQ sells quantum computing and security technology. Its CEO has both technical ambitions to explain and a commercial case to make. That does not settle whether his forecast is right or wrong, but it makes independent evidence important.
The practical concern extends beyond any one company's schedule. Some information must remain confidential for years, while replacing cryptography across complicated systems also takes time.
That longer-term concern also runs through Blockster’s interview with Naoris’ Youssef El Maddarsi about post-quantum security. It provides another industry perspective on preparation, rather than independent validation of IonQ’s timetable.
NIST is already telling organizations to prepare
The U.S. National Institute of Standards and Technology has released three post-quantum cryptography standards that organizations can implement now. They cover key establishment and digital signatures designed to resist future quantum attacks.
Its October 27 transition guidance explains why migration cannot wait for a dramatic public demonstration. Attackers can collect encrypted information today with the intention of decrypting it later, when more capable technology becomes available.
NIST also emphasizes that migration involves an organization's broader cryptographic supply chain, not just one piece of software. Providers, products and connected systems have to work together through the change.
The broader operational challenge is familiar from CertiK’s Angus Lee on audits, monitoring and security infrastructure. Post-quantum migration adds another layer to that work; it does not replace existing protections.
IonQ's own recent communications have made quantum-safe migration a commercial focus:
Post from @IonQ_IncView the original post on X↗
The task is identifying what needs to change
NIST's practical explainer advises technology managers to inventory systems that use encryption and work with their technology departments and vendors on the transition. That is a more actionable starting point than treating a forecast date as a guarantee.
Current incident response remains a separate priority. 1inch’s integration of zeroShadow alerts to identify high-risk wallets addresses threats already encountered in crypto markets, not evidence that a quantum attack has occurred.
Different systems have different requirements. A long-lived confidential record, a software-signing process and a communication connection do not necessarily need the same migration sequence. NIST's Dustin Moody put the point plainly:
“We understand there’s not one strategy that fits all use cases”
— Dustin Moody, NIST post-quantum cryptography project lead
For readers following Blockster's Cantor coverage, this is one of the conference's clearest connections between frontier technology and existing financial infrastructure. A future computing capability is already creating present-day planning work.
De Masi's dates remain a claim to track against engineering progress. The need to understand an organization's cryptographic dependencies is already supported by published standards and migration guidance.
Reporting by Lidia Yadlos




