Why do old quantum claims recirculate as new (and how do you date one)?
Status as of: November 7, 2026. Old quantum results routinely resurface as fresh news, and this week produced two live specimens in a single Radar pass: a preprint dated June 18, 2026 covered as a November 5 news item, and a November 1 digest re-running advantage claims that IBM published on July 30. Rosetta Quantum dates claims for a living — every verdict in our ledger carries a «status as of» line precisely because of this failure mode. This post dates three worked cases and leaves you a five-step checklist for dating any quantum claim yourself.
Did anything new happen in this week's recirculated stories?
No — as far as we could verify, no new measurement sits behind either of this week's specimens.
Specimen 1: the 140-day «news». On November 5, 2026, Quantum Computing Report ran an item on IQM and Volkswagen's quantum-classical AFQMC work for battery chemistry (QCR, 5-Nov-2026). The primary artifact is a preprint dated June 18, 2026 (arXiv:2606.19239) — 140 days earlier. The accompanying vendor whitepaper's file path is dated August 2026 (IQM PDF). To be clear about what the work itself says: the headline «up to 124×» speedup at a 50-orbital benchmark is a reduction in the classical runtime of a hybrid method, measured against the team's own previous implementation, and the «248×» figure at 100 orbitals is an estimate, not a measurement (per the preprint's abstract and QCR's own write-up). The hardware portion is a ground-state calculation of a stretched H8 hydrogen chain on IQM's 54-qubit Emerald; the battery-relevant Li2O4 study — 26 electrons in 20 orbitals, a 40-qubit active space — ran as a classical simulation. None of that is in dispute here. What the November reader is never told is the June date: the coverage is faithful to the preprint and links it, but the only date a skimmer sees is November's. The item also ran the same day IQM reported Q3 2026 results (QCR's news index, consulted November 7, 2026) — a coincidence of dates we can report, not a cause we can establish.
Specimen 2: the 94-day digest item. A weekly digest dated November 1, 2026 (Quantum Zeitgeist) carries the item «IBM, Qedma, and Algorithmiq Demonstrate 70-Qubit Quantum Advantage with Verification», describing a «70-logical-qubit computation with verifiable results» and a spacetime-code embedding that «reduced effective gate error by approximately 10×». No date is given anywhere in the item for when any of this happened. The primary events are IBM's press releases of July 30, 2026 (IBM–UChicago, IBM–Algorithmiq) — 94 days earlier. Rosetta revisited those same claims at the 90-day mark with new, dated evidence: our October 30 re-verdict found none of the three independently adjudicated at that date. Two publications revisited the same 90-day-old claims within 48 hours of each other — one re-measured their status, the other re-ran the headline.
What are the three worked cases, dated?
Three claims, six re-surfacings between them — and zero new measurements behind the re-surfacings, as far as we verified.
| Case | Primary artifact (date) | Re-surfaced as (date) | Gap | New measurement found |
|---|---|---|---|---|
| QC-AFQMC battery study (IQM–VW) | preprint dated 18-Jun-2026 (arXiv:2606.19239) | news item, 5-Nov-2026 (QCR) | 140 days | none |
| IBM «trusted quantum advantage» | announcements of 30-Jul-2026 (IBM newsroom) | digest item, no date, 1-Nov-2026 (Quantum Zeitgeist) | 94 days | none |
| 22-bit RSA on a D-Wave annealer | paper dated May-2024, Chinese Journal of Computers (HSToday, consulted 7-Nov-2026) | headlines Oct-2024 (Gigazine, 15-Oct-2024); «China breaks RSA», 24-Jun-2025 (Earth.com); still circulating, 7-Nov-2026 (Rosetta scan) | 5 to ≈30 months | none |
The third case is the veteran. In May 2024, a Shanghai University team led by Wang Chao published, in the Chinese Journal of Computers, the factoring of the 22-bit RSA integer 2,269,753 on a D-Wave Advantage annealer via a QUBO formulation, plus attacks on the SPN ciphers PRESENT and RECTANGLE. International «military-grade encryption» headlines arrived in October 2024 — roughly five months later. In June 2025 the story returned almost verbatim («China breaks RSA encryption with a quantum computer, threatening global data security», Earth.com, 24-Jun-2025) — about 13 months after the paper. The corrective facts never changed (HSToday): a 22-bit number factors on a laptop in milliseconds, the largest classically factored RSA challenge key is 829 bits (RSA-250, year 2020), the method leaned on heavy classical pre- and post-processing, and no quantum speedup was demonstrated. And it is still circulating: Rosetta's indicator scan of November 7, 2026 — the daily protocol behind our zero-broken-keys dossier — once again found the claims recirculating, now ≈30 months after the paper. The actual record for RSA-style keys broken by any quantum computer remains zero, and the qubit arithmetic for RSA-2048 lives in our RSA-2048 post.
Why do old claims recirculate?
Because every incentive in the pipeline points that way, and no incentive points back at the primary date. Digests and aggregators publish on their own weekly clock, so whatever enters the funnel exits stamped with this week's date. Vendors re-promote measured-once results around corporate calendar events — earnings, launches, anniversaries — and the re-promotion is new marketing, not new science. Syndication and SEO rewrites copy the substance but rarely the timestamp. And quantum claims age invisibly: a reader can check whether a football score is stale, but few readers can check whether «70 logical qubits» happened this week or last quarter. None of this requires bad faith — the November QCR item is accurate and links its primary. The structural failure is that the date of the artifact and the date of the coverage travel separately, and only one of them is visible in a feed. That gap is the reason a dated, neutral ledger needs to exist — it is the gap Rosetta Quantum was built to work.
How do you date a quantum claim in five steps?
- Read the identifier before the headline. arXiv IDs encode year and month: 2606.19239 says June 2026 in its first four digits, whatever the coverage date says. A DOI resolves to a dated record.
- Find the version history. The arXiv /abs/ page lists v1 and every revision with dates. A result's true timeline is its submission history, not its press cycle.
- Separate the event date from the coverage date. A digest's date stamps the digest. A news item's date stamps the item. Neither re-dates the claim — and the two can disagree with each other (the QCR piece shows a November 5 dateline and November 6 page metadata).
- Ask what number changed. New vocabulary around the same numbers is the same claim. «70 logical qubits» plus «≈10× effective gate error» in November matches the July 30 releases; nothing moved.
- Look for the recirculation trigger. Earnings days, conferences, product launches and anniversaries re-surface old results on schedule. If the trigger is a corporate calendar, the science date did not move.
| Artifact | Where its date actually lives | This week's example |
|---|---|---|
| arXiv preprint | the ID encodes YYMM; /abs/ lists v1 and revisions | arXiv:2606.19239 → June 2026 |
| press release | newsroom dateline and URL | IBM newsroom, 30-Jul-2026 |
| vendor whitepaper | often only the file path or PDF metadata | /2026/08/ in the IQM PDF URL |
| news article | visible dateline vs page metadata | QCR item: dateline 5-Nov, metadata 6-Nov-2026 02:46 UTC |
| digest item | only the digest's own date; the result may carry none | Quantum Zeitgeist digest, 1-Nov-2026 |
| journal paper | received / accepted / published lines | Chinese Journal of Computers paper, May-2024 (HSToday) |
What does count as news, then?
Anything that adds a dated piece of evidence: a new arXiv version with new data, a peer-review acceptance, an independent replication, a retraction, a new hardware run with new numbers. Each of those is a new event with its own date, and each can legitimately re-date a claim's status — our checklist for judging advantage claims covers how to weigh them. What does not re-date a claim: a digest item, a whitepaper of an existing preprint, an earnings-day re-promotion, a vocabulary refresh, an anniversary listicle.
The constructive version of recirculation exists, and it has a name: a re-verdict. When Rosetta revisited IBM's July claims on October 30, the post carried new dated evidence (what had been peer-reviewed, replicated or adjudicated by then — in that case, none of it yet) and committed to the next trigger that will re-date the story. Revisiting old claims is good practice; the test is whether the revisit brings a new measurement or just a new timestamp. The same discipline applies to our own work: our roadmap-drift measurement will be re-run before 2029, and that re-run will carry its own date.
What we don't know
- Whether a recent arXiv revision triggered the November coverage. We could not read the submission history of arXiv:2606.19239 in this session (the page served truncated); the paper face says June 18, 2026. If a version revision dated near November exists, the 140-day framing of specimen 1 weakens, and Rosetta will correct this post.
- Whether the August whitepaper added results beyond the June preprint. We did not diff the two documents; the whitepaper date itself comes from a file path, which is weak evidence.
- Why QCR ran the item on November 5. The same-day Q3 earnings release is a coincidence of dates in our data, not an established editorial cause.
- The actual recirculation rate. Three cases are specimens, not a measurement. We have not sampled quantum coverage systematically for recirculation frequency, and we make no claim about how common it is beyond «we found two specimens in one Radar pass this week».
- The full circulation map of the 22-bit RSA story. Our November 7 scan is a spot check under a fixed protocol, not a media census; «≈30 months and counting» dates the span between the paper and our latest sighting, not every wave in between.
Rosetta Quantum publishes verdicts with raw, reproducible data and dates every claim it makes. This is educational content, not a product claim, and not investment advice.