




A 2022 @MSFTQuantum study estimates that finishing in a month or less on about a million physical qubits needs each operation to take under a microsecond, per arXiv 2211.07629. That's a published estimate. Which qubit types can already run that fast?


The @IBMResearch blueprint for quantum-centric supercomputing splits the classical side in two, per IBM: big CPU and GPU pools to clean up noisy results, and fast computers near the qubits to fix errors live. We think the second is harder to build. Which would you pick?


The updated @Alice__Bob roadmap aims for 200 error-corrected qubits built from 3,600 physical ones by 2030, then 2,048 from 89,600 by 2034, per alice-bob.com/roadmap. Neither machine exists yet. These are company goals. What has to go right for the 2030 date to hold?


Some quantum operations need special "magic" states. A @qctrlHQ team prepared one on an IBM Nighthawk chip that held 99.1% fidelity after ten stabilizer rounds in a distance-5 surface code, per arXiv 2611.22035. Only 4.6% of shots were kept. Can this work at higher distance?


Error correction eats qubits. Origin Quantum and USTC designed codes that keep over 1 usable qubit per 2 data qubits, about 6 times IBM's Gross-code rate at the same distances, per arXiv 2611.20410. Simulation only, on 5 or 6 stacked chip layers. Who builds that chip?


A GPU decoder from @nvidia, software that finds errors so they can be fixed, is aimed at ion trap and neutral atom machines, whose cycles last milliseconds. It averaged 0.64 to 4.97 ms per run at a 0.2% error rate on one GPU, per arXiv 2611.21321. Is that fast enough?


A code's distance is the fewest errors that can slip past it unnoticed. One 360-qubit code from @IBMResearch was listed as distance 24 or less because solvers timed out. A machine-checked proof now shows it is 24, per arXiv 2611.21236. Which code claims need proofs next?


A 250 MHz register-transfer-level simulation of a real-time decoder for quantum low-density parity-check codes gave a 173.8 ns mean and a 732 ns 99th-percentile latency, per arXiv 2611.19130, at a 0.5% physical error rate. Do we budget the 732 ns tail for the correction cycle?