• Michael Saylor says quantum threat to Bitcoin is more than 10 years away The Strategy CEO downplayed quantum risks on Natalie Brunell’s Coin Stories podcast, saying any credible threat would prompt coordinated software upgrades across global digital systems. • Cointelegraph in your social feed Strategy CEO Michael Saylor dismissed concerns about quantum computing during an appearance on Natalie Brunell’sCoin Storiespodcast, saying the cybersecurity community broadly agrees that any credible quantum threat is likely more than a decade away. • While it remains unclear if or when a quantum risk might materialize, Saylor told thepodcasthost that any credible breakthrough would prompt coordinated software upgrades across global banking systems, internet infrastructure, consumer devices, artificial intelligence networks and crypto protocols, including Bitcoin (BTC). • Saylor said the digital systems underpinning modern digital infrastructure would eventually adoptpost-quantum-resistant cryptographyif necessary, adding that such a shift would not come as a surprise. • “You’ll see it coming. • We’ll all see it coming,” he said, adding that Bitcoin’s software is designed to change over time, with nodes, hardware, and wallets capable of upgrading in response to emerging threats.
Article Summaries:
- Michael Saylor, CEO of Strategy, said on a Coin Stories podcast that a credible quantum‑computing threat to Bitcoin is unlikely to materialize for more than a decade. He noted that if a breakthrough occurred, global banking, internet, AI and crypto systems would coordinate software upgrades to post‑quantum cryptography, and that Bitcoin’s architecture already allows nodes, hardware and wallets to update. Saylor called the crypto sector “the most sophisticated cybersecurity community” and said it would lead the response. In contrast, Ethereum co‑founder Vitalik Buterin has warned of a 20 % chance of quantum computers breaking elliptic‑curve cryptography before 2030, prompting the Ethereum Foundation to begin a post‑quantum roadmap.
Sources: