IonQ Study: 20,000 Qubits Could Break Bitcoin Encryption Within 26 Days

·1 views

IonQ researchers have published what they call the first complete, end-to-end resource estimate for breaking Bitcoin's secp256k1 elliptic-curve cryptography using a fault-tolerant quantum computer. The study concludes that approximately 19,397 physical qubits — far fewer than previously thought — would be sufficient to crack the encryption in under 26 days using an optimized version of Shor's algorithm. The team's approach, built on the Walking Cat trapped-ion architecture with quantum error-correction codes, maps every operation to actual hardware primitives rather than relying on theoretical approximations. IonQ's own hardware roadmap targets systems of this scale by 2028, pushing earlier 2030s timelines significantly forward and raising urgent concerns for blockchain security. The findings have drawn attention from both private industry and governments, accelerating efforts to develop quantum-resistant cryptographic standards.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Engineer's AWS Lab Experiment Reveals How Easily Threat Analysis Can Go Wrong

A developer deliberately exposed a PostgreSQL database on the public internet within an AWS lab environment to simulate a cyberattack, piping VPC Flow Logs into Splunk for a partner to monitor from a security operations perspective. When reviewing the flow logs months later, the engineer discovered 28 source IP addresses in the dataset but had only documented one in the incident report — and misidentified it. The flagged IP, 10.0.1.179, was actually an internal RFC 1918 private address originating from within the engineer's own network, while a genuine external scanner at 136.35.186.87 conducting multi-port probes was overlooked entirely. Beyond the misidentification, 25 other external addresses had quietly probed 29 distinct ports — including Redis, VNC, Kubernetes, and NetBIOS — within minutes of the public IP going live, none of which were captured in the incident report. The exercise highlighted three common analytical blind spots: misreading IP address context, drawing conclusions flow logs cannot support such as authentication outcomes, and over-focusing on high packet counts while ignoring low-volume background scanning activity.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

SelfCmd Tool Aims to Speed Up Server Threshold and Time-Based Policy Testing

Server administrators and software testers often face delays when validating log retention policies, storage cleanup thresholds, and device lifecycle expiration logic. Traditional methods require engineers to wait days or weeks for real time to pass, or manually adjust system clocks across multiple nodes. SelfCmd is a tool designed to automate time-shifting workflows, eliminating the need for manual clock manipulation. The platform also includes an AI-powered diagnostics engine that analyzes failure logs within seconds. Full features and documentation are available on the SelfCmd official website.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How a 5-stage filter cut NVIDIA's weekly 5,718 news articles down to 161 alerts

A developer experiment tracked all news articles mentioning NVIDIA over seven days from August 30 to September 5, 2026, finding a total of 5,718 pieces — roughly 817 per day. A five-stage filtering pipeline reduced that volume to just 161 relevant alerts, or about 23 per day, by combining headline searches with canonical entity resolution. The analysis revealed that searching headlines alone captures only 29.8% of relevant coverage, while entity recognition alone missed 180 articles that explicitly named NVIDIA in their titles. Additionally, only 31.6% of all articles were in English, and about 12.5% of filtered results were near-duplicate republications of the same story. The findings, published on DEV Community, are aimed at developers and analysts who want to build more reliable, low-noise company news monitoring tools.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

MayFly Tool Keeps Dev Secrets in RAM Only, Built With Go Standard Library

A team built MayFly, a secrets management tool, during the Raptor Zero Dependency Hackathon with a strict 72-hour, no-external-library constraint using only Go's standard library. The tool addresses a widespread vulnerability where plaintext API keys stored in .env files on disk are silently stolen by malicious npm or pip packages during routine installations. Unlike sandboxing approaches, MayFly stores secrets in an encrypted vault and decrypts them directly into volatile memory at runtime, so keys never touch the hard drive in plaintext. When a developer runs a command through MayFly, it captures a master passphrase, decrypts only the relevant project secrets into RAM, and injects them into the child process's environment. The project builds on the team's earlier tool L.I.O.N., a Rust-based sandbox, which highlighted that protecting disk-resident plaintext keys is fundamentally insufficient.

0 comments Read more at DEV Community