Urgent.News

What's breaking now, across thousands of outlets.

Tech

Quantum Computers Won't Break Your Wallet Tomorrow. Here's Why You Should Still Care Today

The quantum threat to blockchain is not a single event arriving on a known date. It is two separate clocks running simultaneously, and most engineers building wallet infrastructure are only watching one of them. On March 30, 2026, a team at Google Quantum AI published a paper that should have reshaped crypto security conversations for months. The paper co-authored by Ryan Babbush, Craig Gidney,…

The article discusses the two-pronged threat quantum computers pose to blockchain security, emphasizing the need for immediate action despite the long-term timeline. The first component, referred to as "Q-day," is the point when a cryptographically relevant quantum computer capable of running Shor's algorithm against real elliptic curve keys at scale becomes available.

However, current quantum hardware is still far from achieving this milestone, and estimates for when this gap will close remain uncertain. The second component, known as the "harvest-now-decrypt-later" problem, is already active and can be exploited by attackers without the need for a quantum computer. This issue arises when an attacker gathers encrypted data today and uses future quantum computing power to decrypt it later.

The article highlights that while the first component remains a future concern, the second component necessitates immediate engineering decisions from wallet builders to protect against potential quantum threats in the present and near future.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

How I built a trade analytics dashboard with Streamlit and Plotly — and turned it into a product

I'm an AI/ML student and I build Streamlit dashboards as a freelancer on the side. A few weeks ago I was working on a trade analytics project and realized I was writing the same landed cost logic…

  • Author built LandedIQ dashboard to calculate trade unit economics
  • Uses Streamlit, Plotly, Pandas, and Requests for development
  • Deployed on Railway with manual Streamlit server configuration

AWS Lambda Durable Functions and the Replay Bug in Human-in-the-Loop Agents

Ciao 👋 Here is a sentence that should not be possible: my workflow executed an action a human explicitly did not approve.

  • AWS Lambda durable functions enable long-running workflows with human input.
  • Replay bug causes unexpected behavior when agent proposal is outside a step.
  • Properly structuring code within steps prevents replay bug issues.

More from Sunday 27 September →