Submit an article
@Eli5defi
@Eli5defi

If you’ve ever said β€œquantum is decades away,” today’s news should make you pause. Google just published a paper suggesting a quantum computer could crack a Bitcoin private key in ~9 minutes, potentially moving the quantum timeline up to 2029. The thing is: that machine doesn’t exist yet. But the distance between β€œtheoretical” and β€œpractical” just shrank fast, and a lot of wallet hygiene that feels fine today is dangerously wrong for where this is going. The threat isn’t quantum mining. It’s quantum signatures. Bitcoin’s Proof-of-Work is fine. SHA-256 is fine. The soft spot is ECDSA, the signature scheme that proves you own your coins. Shor’s algorithm doesn’t brute-force keys. It solves the underlying math. Three realistic attack paths: 1) On-spend Watch a transaction in the public mempool, derive the private key, then front-run it with a forged transaction and a higher fee before confirmation. Some estimates put success around ~41% under current assumptions. 2) At-rest Target dormant wallets where the public key is already exposed. No time pressure. Works with weaker quantum hardware. 3) On-setup Crack setup parameters once, then turn it into a permanent classical exploit. Think Tornado Cash–style setups, and even Ethereum’s KZG data availability layer. Who’s exposed right now: - ~6.9M BTC may already be vulnerable across script types - Any address you’ve spent from has its public key permanently on-chain - Taproot (bc1p) exposes your public key the moment you receive funds And the part that changes the timeline: - Older estimates: ~9M physical qubits to break Bitcoin - Google’s newer circuits: under ~500K (about a 20x reduction) So yes, the computer isn’t here yet. But this is looking less like a physics problem and more like an engineering schedule. What to do now: - Stop reusing addresses - Avoid bc1p for cold storage if you’re optimizing for long-term quantum risk - Audit which wallets have already exposed public keys --- Eli5 Interactive research here: https://claude.ai/public/artifacts/ff56f…

Tweet image
x.com
by rvolz.eth1208 πŸ₯ β€’ 10h β€’ x.com
Helia - A full P2P protocol written entirely in JavaScript
by timdaub.eth11860 πŸ₯ β€’ 1d β€’ helia.io
@drakefjustin
@drakefjustin

Today is a monumentous day for quantum computing and cryptography. Two breakthrough papers just landed (links in next tweet). Both papers improve Shor's algorithm, infamous for cracking RSA and elliptic curve cryptography. The two results compound, optimising separate layers of the quantum stack. The results are shocking. I expect a narrative shift and a further R&D boost toward post-quantum cryptography. The first paper is by Google Quantum AI. They tackle the (logical) Shor algorithm, tailoring it to crack Bitcoin and Ethereum signatures. The algorithm runs on ~1K logical qubits for the 256-bit elliptic curve secp256k1. Due to the low circuit depth, a fast superconducting computer would recover private keys in minutes. I'm grateful to have joined as a late paper co-author, in large part for the chance to interact with experts and the alpha gleaned from internal discussions. The second paper is by a stealthy startup called Oratomic, with ex-Google and prominent Caltech faculty. Their starting point is Google's improvements to the logical quantum circuit. They then apply improvements at the physical layer, with tricks specific to neutral atom quantum computers. The result estimates that 26,000 atomic qubits are sufficient to break 256-bit elliptic curve signatures. This would be roughly a 40x improvement in physical qubit count over previous state-of-the-art. On the flip side, a single Shor run would take ~10 days due to the relatively slow speed of neutral atoms. Below are my key takeaways. As a disclaimer, I am not a quantum expert. Time is needed for the results to be properly vetted. Based on my interactions with the team, I have faith the Google Quantum AI results are conservative. The Oratomic paper is much harder for me to assess, especially because of the use of more exotic qLDPC codes. I will take it with a grain of salt until the dust settles. β†’ q-day: My confidence in q-day by 2032 has shot up significantly. IMO there's at least a 10% chance that by 2032 a quantum computer recovers a secp256k1 ECDSA private key from an exposed public key. While a cryptographically-relevant quantum computer (CRQC) before 2030 still feels unlikely, now is undoubtedly the time to start preparing. β†’ censorship: The Google paper uses a zero-knowledge (ZK) proof to demonstrate the algorithm's existence without leaking actual optimisations. From now on, assume state-of-the-art algorithms will be censored. There may be self-censorship for moral or commercial reasons, or because of government pressure. A blackout in academic publications would be a tell-tale sign. β†’ cracking time: A superconducting quantum computer, the type Google is building, could crack keys in minutes. This is because the optimised quantum circuit is just 100M Toffoli gates, which is surprisingly shallow. (Toffoli gates are hard because they require production of so-called "magic states".) Toffoli gates would consume ~10 microseconds on a superconducting platform, totalling ~1,000 sec of Shor runtime. β†’ latency optimisations: Two latency optimisations bring key cracking time to single-digit minutes. The first parallelises computation across quantum devices. The second involves feeding the pubkey to the quantum computer mid-flight, after a generic setup phase. β†’ fast- and slow-clock: At first approximation there are two families of quantum computers. The fast-clock flavour, which includes superconducting and photonic architectures, runs at roughly 100 kHz. The slow-clock flavour, which includes trapped ion and neutral atom architectures, runs roughly 1,000x slower (~100 Hz, or ~1 week to crack a single key). β†’ qubit count: The size-optimised variant of the algorithm runs on 1,200 logical qubits. On a superconducting computer with surface code error correction that's roughly 500K physical qubits, a 400:1 physical-to-logical ratio. The surface code is conservative, assuming only four-way nearest-neighbour grid connectivity. It was demonstrated last year by Google on a real quantum computer. β†’ future gains: Low-hanging fruit is still being picked, with at least one of the Google optimisations resulting from a surprisingly simple observation. Interestingly, AI was not (yet!) tasked to find optimisations. This was also the first time authors such as Craig Gidney attacked elliptic curves (as opposed to RSA). Shor logical qubit count could plausibly go under 1K soonish. β†’ error correction: The physical-to-logical ratio for superconducting computers could go under 100:1. For superconducting computers that would be mean ~100K physical qubits for a CRQC, two orders of magnitude away from state of the art. Neutral atoms quantum computers are amenable to error correcting codes other than the surface code. While much slower to run, they can bring down the physical to logical qubit ratio closer to 10:1. β†’ Bitcoin PoW: Commercially-viable Bitcoin PoW via Grover's algorithm is not happening any time soon. We're talking decades, possibly centuries away. This observation should help focus the discussion on ECDSA and Schnorr. (Side note: as unofficial Bitcoin security researcher, I still believe Bitcoin PoW is cooked due to the dwindling security budget.) β†’ team quality: The folks at Google Quantum AI are the real deal. Craig Gidney (@CraigGidney) is arguably the world's top quantum circuit optimisooor. Just last year he squeezed 10x out of Shor for RSA, bringing the physical qubit count down from 10M to 1M. Special thanks to the Google team for patiently answering all my newb questions with detailed, fact-based answers. I was expecting some hype, but found none.

x.com
by timdaub.eth11860 πŸ₯ β€’ 1d β€’ x.com
substack.com
We Are All Reviewers Now
by timdaub.eth11860 πŸ₯ β€’ 1d
ethux.design
EthUX | Ethereum UX Pain Points, Solutions & Research
by timdaub.eth11860 πŸ₯ β€’ 1d
aztec.network
Announcing the Alpha Network
by timdaub.eth11860 πŸ₯ β€’ 1d
rivet.dev
agentOS - Everything Agents Need to Run and Operate - Rivet
by timdaub.eth11860 πŸ₯ β€’ 1d