Nothing. It searches.
Declared for this mission and copied when its deposit arrived. Nothing on file records what the session actually ran under — an environment is selected by name in the runner's own account, and a name that matches nothing falls through to their default without saying so.
# MAP-001 — D-Wave quantum supremacy claim
Paste this whole thing. Nothing to fill in.
**Environment:** `night-shift-map`. The exact settings are on this mission's
page — the env file is the only place they live, so they cannot drift out of
sync with a copy written here.
---
## The job
D-Wave published a claim that its quantum annealer performed a simulation
beyond the reach of classical computers. Other groups disputed it. That
argument is public and unresolved.
Your job is not to decide who is right. It is to lay out the dispute so that
a reader can decide for themselves, and check you while doing it.
## What to produce
A document a smart non-specialist can follow. Assume no background in quantum
computing. Explain what needs explaining, briefly, where it comes up.
Cover:
**The claim.** What exactly was asserted — the specific problem, the specific
comparison, the specific sense in which classical methods were said to fall
short. Precision matters here: "quantum supremacy" is a headline, not a claim.
Find the actual sentence.
**Each challenge.** For every group that disputed it: who, what specifically
they showed, and what they did *not* claim to show. A paper that shows one
classical method matches the result is making a narrower claim than "the
original was wrong" — keep those distinct.
**Each response.** What D-Wave or its authors said back, and whether the reply
engaged the specific objection or reframed it.
**Stakes.** Who is employed by, funded by, or competing with whom. State it
factually and without insinuation — a stake is context, not an accusation, and
a paper is not wrong because its author has one.
**Where it stands now.** Has anything been settled? Did the exchange stop, or
is it live? Note the date of the most recent substantive contribution you can
find.
**What would settle it.** One paragraph. A specific benchmark, a specific
simulation, a specific comparison nobody has run. If nothing clean would
settle it, say so and explain why.
**What an outsider can and cannot check.** Which parts rest on public code and
data, and which rest on hardware, proprietary data, or resources a third party
cannot access. Be blunt — this is the most useful section for me.
## Sourcing rules
- Every claim about what someone said needs a citation: title, authors, year,
link, and where in the document it appears (section, figure, page).
- **Open the page.** Do not cite from a search-result snippet. If a page will
not load, say so explicitly and mark that citation as unverified rather than
quietly using the snippet.
- Quote the sentence where each party states its position. One sentence is
enough — do not reproduce passages.
- Where two sources conflict on a matter of fact (a date, a number, who did
what), show both and say they conflict. Do not pick silently.
- If you cannot find a source for something you believe is true, leave it out.
- **"Blocked" and "paywalled" are different facts — say which.** A domain
outside this environment's allowlist means you could not try. A domain that
let you connect and then returned a paywall, login wall, or bot check means
you tried and were refused. Both leave a gap in the record, but only the
second tells the reader the source exists and is readable by someone else.
For every source you could not read, the notes must say which of the two it
was. Where a paywalled paper has a preprint, use the preprint and say you
did.
## Tone
Neutral, and neutral is not mushy. "Both sides make good points" is a failure.
Say precisely what each side established, and precisely where the disagreement
actually sits — usually it is narrower than the public argument suggests.
If one side's position is substantially better supported by the public record,
say that plainly and show why. Neutrality means no stake in the outcome, not
refusing to report what the evidence shows.
## Output — two files, and both are required
**1. `output.md`** — the prose, as described above. Write it for a reader.
Structure it however reads best.
Then a section called **Notes on this run** — for me, not for a reader:
what you searched, what failed to load, which citations are unverified, what
you are unsure about, and anything that surprised you. Blunt.
**2. `positions.yaml`** — the same positions as structured data. One entry per
party per claim: a group that disputes two separate things gets two entries,
and two groups making the same claim get one entry each.
```yaml
positions_file:
mission: MAP-001
source: output.md
count: <number of entries below>
positions:
- id: P01
party: <named person or group, as the source names them>
claim: <one line, no hedging>
stake: <employment, funding, or competition — factual, or "none found">
sources:
- url: <url>
read: yes # you opened this page and read the text you cite
- url: <url>
read: no # you know it exists; you did not open it
```
**`read` is not a formality.** A URL you opened and a URL you merely know
exists are the same string, and listing one under `sources` implies you read
it. Say which. `read: yes` is checkable — an opened page leaves a fetch in
this session's transcript, which you do not write — so a `read: yes` with no
fetch behind it is a false record, and worth more scrutiny than an honest
`read: no`. Prefer citing what you read; where you must cite unread, say so
and the reader can weigh it.
**These must agree.** Every position in the prose appears in the YAML and vice
versa. The board counts entries in `positions.yaml` — it never parses your
prose, because a count derived from headings is a count that can silently be
wrong. If you can only produce one of the two files, produce neither and
deposit a finding explaining why.
An unmappable position is still a position: record it with the claim as stated
and `sources: []`, and say in the prose exactly what is missing.
## Where to put them
Push a branch to **`night-shift-network/inbox`** with both files inside a
directory named for this mission:
```
MAP-001/output.md
MAP-001/positions.yaml
```
The directory is what matters. A file at the root of the branch is not a
deposit and will not be collected — it will sit there looking delivered while
nothing has been.
The branch name does not matter and is deliberately not specified: the relay
reads every branch, so whichever branch your session is already on is fine.
Never delete or force-push a branch, yours or anyone else's; cleanup is
maintainer-side only.
# The D-Wave quantum supremacy dispute
## What this is about, in one paragraph
In March 2025, D-Wave Systems (a publicly traded company that sells quantum
annealing computers) published a peer-reviewed paper in *Science* stating that
its hardware had simulated the behavior of a class of magnetic materials
faster than any classical computer could, for a problem with genuine physical
meaning rather than a contrived benchmark. Within days, two independent
academic groups posted preprints showing that classical software — run on
ordinary computing hardware, in one case starting on a laptop — could
reproduce large parts of what D-Wave's quantum processor had done. D-Wave
disputed that the classical work covered the same ground. A third academic
group published a further, narrower objection in July 2026. The exchange is
still open as of this writing (16 August 2026).
Some background before the specifics: a **quantum annealer** is a special-purpose
quantum computer built to settle into low-energy configurations of a physical
system, rather than to run general-purpose algorithms. A **spin glass** is a
model magnetic material made of many small magnets ("spins") whose interactions
are randomly frustrated, so the system has no simple, orderly resting state —
predicting how it evolves over time is a genuinely hard computational problem
that also describes real disordered magnetic materials. The dispute below is
about whether classical (ordinary, non-quantum) software can predict that
evolution as accurately as D-Wave's hardware did, and if not, by how much and
in which cases.
---
## The claim
D-Wave's paper is **"Beyond-classical computation in quantum simulation,"**
by Andrew D. King and 62 coauthors (D-Wave Quantum Inc., with academic
collaborators including Anders W. Sandvik, Roger G. Melko, Juan Carrasquilla
and Marcel Franz), published in *Science* **388**, 199–204 (2025).
Preprint: [arXiv:2403.00910](https://arxiv.org/abs/2403.00910) (submitted 1
March 2024; revised 14 October 2025).
The specific problem: simulating the real-time quantum dynamics of
programmable Ising spin glasses — random magnetic interactions laid out on
square, cylindrical, dimerized-cubic, diamond, and dimerized-biclique lattice
geometries — as the system is driven from a simple starting state toward a
disordered target ("quenched" dynamics), on systems up to 576 qubits.
The specific comparison: D-Wave benchmarked its quantum annealer's output
against three families of classical simulation method — matrix product states
(MPS), projected entangled-pair states (PEPS), and neural quantum states
(NQS) — and against an estimate of what the largest of those methods would
cost on the Frontier supercomputer at Oak Ridge National Laboratory. The
paper's own words:
> "We show that several leading approximate methods based on tensor networks
> and neural networks cannot achieve the same accuracy as the quantum
> annealer within a reasonable time frame. Thus, quantum annealers can
> answer questions of practical importance that may remain out of reach for
> classical computation."
> — abstract, arXiv:2403.00910
The headline number, on the largest instances:
> "MPS would take millions of years on the Frontier supercomputer per input
> to match QPU quality. Memory requirements would exceed its 700 PB storage,
> and electricity requirements would exceed annual global consumption."
> — arXiv:2403.00910
**Important nuance:** that figure is an *extrapolation*. D-Wave ran MPS
simulations at smaller, tractable sizes, measured how their cost scaled as
system size grew, and projected that scaling out to the full problem size —
it is not the record of an actual multi-million-year computation. The paper
is explicit that the extrapolation, not a completed run, is what licenses the
"beyond classical" claim; the entire dispute that follows is about whether
that extrapolation, and the general conclusion drawn from it, holds up.
---
## Challenge 1: EPFL — a narrower classical method, a narrower claim
**Who:** Linda Mauron and Giuseppe Carleo, École Polytechnique Fédérale de
Lausanne (EPFL).
**Paper:** "Challenging the Quantum Advantage Frontier with Large-Scale
Classical Simulations of Annealing Dynamics,"
[arXiv:2503.08247](https://arxiv.org/abs/2503.08247) (submitted 11 March
2025 — two days before D-Wave's press conference; still an arXiv preprint,
not published in a peer-reviewed journal as of this writing).
**What they showed:** using a classical algorithm called time-dependent
variational Monte Carlo (t-VMC) with a "Jastrow-Feenberg" trial wavefunction —
a different classical method from the ones D-Wave tested — they simulated
spin-glass annealing dynamics on lattices up to 128 spins (three-dimensional
diamond lattice), with correlation errors below 7%, using computational
resources that scale polynomially rather than exponentially with system size.
> "Our approach achieves accuracy comparable to that of quantum processing
> units while requiring only polynomially scaling computational resources."
> — arXiv:2503.08247, abstract
Their framing of what this means:
> "Our findings call for a significant shift in the computational 'advantage'
> frontier identified in Ref. [King et al. 2024]."
> — arXiv:2503.08247
**What they did *not* claim:** their largest simulated system (128 spins) is
smaller than D-Wave's largest (576 spins); they tested one lattice geometry
(3D diamond), not the full set D-Wave used; and they did not claim that MPS,
PEPS, or NQS — the specific methods D-Wave benchmarked against — were
mischaracterized. Their claim is that a *different* classical method, not
tried by D-Wave, closes the gap in the regime they tested. It is a claim
about where the frontier sits, not a claim that D-Wave's specific
comparisons were wrong.
**Funding:** the paper's acknowledgments state it "was supported by SEFRI
[Switzerland's State Secretariat for Education, Research and Innovation]
through Grant No. MB22.00051 (NEQS – Neural Quantum Simulation)" — a grant
explicitly aimed at developing classical neural/variational simulation
methods as alternatives to specialized hardware.
---
## Challenge 2: Flatiron Institute — the one that made it back into *Science*
**Who:** Joseph Tindall, Antonio Mello, Matt Fishman, E. Miles Stoudenmire,
and Dries Sels (Center for Computational Quantum Physics, Flatiron
Institute; Sels is also affiliated with New York University).
**Paper:** "Dynamics of disordered quantum systems with two- and
three-dimensional tensor networks,"
[arXiv:2503.05693](https://arxiv.org/abs/2503.05693) (v1 submitted 7 March
2025, five days before D-Wave's announcement — meaning this work was
independently underway before the *Science* paper's public unveiling).
**This paper was itself later published in *Science* 392, 868–872 (21 May
2026), DOI 10.1126/science.adx2728** — meaning a classical rebuttal to a
*Science* quantum-supremacy claim was, fourteen months later, itself
peer-reviewed and printed in the same journal.
**What they showed:** a "belief propagation" (BP) algorithm from 1982,
combined with lattice-specific tensor networks, tracking entanglement growth
during time evolution. Their own summary:
> "We find that state-of-the-art accuracies can be achieved with modest
> computational resources."
> — arXiv:2503.05693, abstract
Their result is uneven by design, not uniformly better everywhere — this
matters for reading the claim precisely:
> "In the case of cylindrical and diamond lattices our simulations reach
> accuracies which are well beyond those of the quantum annealer... in the
> case of the dimerized cubic lattice the accuracies we reach are comparable
> to the annealer."
> — arXiv:2503.05693
They also state their own method's limitation directly, rather than leaving
it implicit:
> "This is likely because on the 36 and 54 qubit dimerized cubic lattices a
> periodic boundary is present... which creates a loop of size 3 in the
> tensor network. This small loop increases the error in our methods."
> — arXiv:2503.05693
**What they did *not* claim:** their paper covers square/cylindrical,
diamond, and dimerized-cubic lattices. It does not address the
dimerized-biclique lattice that also appears in D-Wave's original problem
set (King et al. tested "dimerized biclique graphs" among their lattice
types) — a geometry Tindall et al. simply do not attempt. They also do not
claim to reproduce D-Wave's highest-order correlator measurements. Their
paper does not contain a sentence declaring D-Wave's overall conclusion
false; it demonstrates that one specific classical method, in specific
regimes, matches or beats the quantum result, and is candid about where it
does not.
**Funding:** "ongoing support through the Flatiron Institute, a division of
the Simons Foundation" (a private non-profit research foundation, not a
D-Wave competitor); Sels separately acknowledges AFOSR (U.S. Air Force
Office of Scientific Research) Grant FA9550-21-1-0236.
**A media detail worth being precise about:** press coverage widely described
early calculations as having been run "on a laptop." That detail traces to
reporting about how Tindall initially prototyped the method using the
Flatiron-built ITensor software library, not a claim inside the paper itself
that the *published*, full-scale results were laptop-generated. I was unable
to independently verify the laptop detail against a primary source (see Notes
below) and flag it here rather than assert it as established.
---
## D-Wave's response
D-Wave engaged the Flatiron paper with a full technical counter-paper, not
just a statement:
**Paper:** Alberto Nocera (University of British Columbia — also a coauthor
of D-Wave's original *Science* paper), Jack Raymond, William Bernoudy,
Mohammad H. Amin, and Andrew D. King (all D-Wave Quantum Inc., Amin also at
Simon Fraser University), "Evaluating classical simulations with a quantum
processor,"
[arXiv:2508.15759](https://arxiv.org/abs/2508.15759) (submitted 21 August
2025; still an arXiv preprint, not journal-published as of this writing).
This paper's method is itself notable: rather than arguing from theory, the
authors used D-Wave's *own quantum processor* as a source of "ground truth"
data to test whether Tindall et al.'s predicted error-scaling behavior for
their BP-based tensor network method actually holds up in regimes too large
for classical methods to cross-check independently.
> "Our observations run contrary to previous scaling predictions,
> demonstrating the need for caution when extrapolating the accuracy of
> classical simulations of quantum dynamics."
> — arXiv:2508.15759, abstract
> "Our findings contradict a recent prediction about error scaling in a
> novel classical algorithm based on belief-propagation-gauged tensor-network
> states (BP-TNS)."
> — arXiv:2508.15759
**Does this engage the specific objection, or reframe it?** In substance, it
engages: it targets Tindall et al.'s specific error-scaling predictions with
new data, rather than rebutting the general "quantum supremacy is disputed"
narrative. Its own conclusion is notably cooperative in tone rather than
declaring victory:
> "Our results demonstrate that the virtuous cycle of competition between
> classical and quantum simulations can lend insight in both directions."
> — arXiv:2508.15759
Separately, D-Wave issued public statements — reported by multiple technology
and trade outlets — under headlines including "D-Wave's Quantum Supremacy
Result Stands," reportedly arguing that the Flatiron work "does not reproduce
the full scope" of the original result and does not reach "the hardest
problem instances." **I was not able to open D-Wave's own press release
directly** (see Notes below); I can confirm from independent secondary
reporting that D-Wave made public statements to this effect, but I cannot
verify the exact wording against the primary source, so I am not quoting it
as a direct citation. This public-statement register is broader and more
categorical than the arXiv technical paper's narrower, data-specific rebuttal
— worth noting as a real difference in register between D-Wave's peer-facing
science and its public-facing communication, even though I could not verify
the exact public language.
**One relevant fact I *could* verify:** none of Mauron, Carleo, Tindall,
Mello, Fishman, Stoudenmire, or Sels appear anywhere in the 63-author list
of D-Wave's original *Science* paper. The classical challengers are
independent of the original claim's authorship. Nocera, by contrast, is a
repeat collaborator — a coauthor of both the original claim and D-Wave's
rebuttal to Flatiron.
---
## Challenge 3: a narrower, more recent objection — Neural Quantum States
**Who:** Wladislaw Krinitsin, Nikita Alert, Matteo Rizzi, and Markus Schmitt
(Forschungszentrum Jülich, with joint appointments at the Universities of
Regensburg and Cologne).
**Paper:** "Comment on 'Beyond-classical computation in quantum
simulation,'" [arXiv:2607.08811](https://arxiv.org/abs/2607.08811)
(submitted 9 July 2026 — the most recent substantive contribution to this
dispute that I could find).
This is the narrowest of the three challenges — it does not touch the
tensor-network comparisons at all, only D-Wave's specific claim about neural
quantum states (NQS):
> "One of the findings indicates that Neural Quantum States... fail to reach
> the same accuracy as the quantum processor. In this comment we revisit
> these concerns, demonstrating that NQS can provide competitive results in
> some of the cases when accounting for the Monte-Carlo noise and large
> autocorrelation times between samples obtained from the final state."
> — arXiv:2607.08811, abstract
Their technical point is about how error was measured, not about the physics:
D-Wave's NQS comparison, they argue, mixed genuine method error with
statistical sampling noise, making NQS look worse than it is.
> "The estimated values of the comparison metric do not fully correspond to
> method-specific limitations, but include significant contributions from
> statistical noise."
> — arXiv:2607.08811
**What they did *not* claim:** their own conclusion is scoped to "some of
the cases" and to "the considered instance of the disorder realization" —
singular, not a general claim that NQS matches the quantum annealer across
the board. Their acknowledgments note "insightful comments on the results
by A. King and R. Wiersema" — i.e., a collegial exchange with D-Wave authors
during preparation, not an adversarial one. No funding source is listed in
the paper. I found no published D-Wave response to this specific comment as
of 16 August 2026.
---
## Stakes
Stated factually; a stake is context, not an accusation.
- **D-Wave Quantum Inc.** is a publicly traded company (Nasdaq/NYSE: QBTS).
Quantum supremacy/advantage claims are central to its investor narrative;
independent reporting found via search (not independently opened — see
Notes) describes a sharp single-day stock decline around the time Tindall
et al.'s paper appeared in *Science* in May 2026, which I mention as
context for the claim's commercial weight but do not cite as a verified
figure. D-Wave also announced a $550 million acquisition of Quantum
Circuits Inc. in January 2026 to expand into gate-model quantum computing,
indicating the company's broader competitive positioning in the field
beyond annealing.
- **Mauron and Carleo (EPFL)** are funded, per their own paper, by a Swiss
government grant specifically for developing classical neural/variational
quantum simulation methods (SEFRI Grant MB22.00051, "Neural Quantum
Simulation") — an institutional and research interest in demonstrating
that classical variational methods can match specialized quantum hardware.
- **Tindall, Mello, Fishman, Stoudenmire, and Sels (Flatiron Institute /
NYU)** are supported by the Flatiron Institute (a division of the Simons
Foundation, a private non-profit) and, for Sels, a U.S. Air Force Office
of Scientific Research grant. Flatiron does not sell competing hardware
and has no commercial stake in D-Wave's stock performance; its
Center for Computational Quantum Physics has an institutional interest in
advancing tensor-network methods generally.
- **Krinitsin, Alert, Rizzi, and Schmitt (Forschungszentrum Jülich)** work
in variational/neural quantum simulation, the same research area as the
method (NQS) they are defending — a direct research-reputation stake in
showing NQS was undersold, comparable in kind to Carleo's stake in t-VMC.
No funding section is disclosed in their paper.
- **Nocera** is affiliated with the University of British Columbia (not a
D-Wave employee) but has coauthored both D-Wave's original claim and its
rebuttal to Flatiron — an ongoing research collaboration with D-Wave.
- None of the classical-side authors (Mauron, Carleo, Tindall, Mello,
Fishman, Stoudenmire, Sels, Krinitsin, Alert, Rizzi, Schmitt) appear as
coauthors on D-Wave's original paper; I checked the full 63-name author
list directly.
---
## Where it stands now
| Date | Event |
|---|---|
| 1 Mar 2024 | D-Wave posts first arXiv preprint of the claim (v1) |
| 7 Mar 2025 | Tindall et al. (Flatiron) post their preprint |
| 11 Mar 2025 | Mauron & Carleo (EPFL) post their preprint |
| ~12–14 Mar 2025 | D-Wave's *Science* paper publishes and is publicized; D-Wave responds publicly to both preprints (exact wording unverified — see Notes) |
| 21 Aug 2025 | D-Wave (Nocera, Raymond, Bernoudy, Amin, King) posts its technical rebuttal to Tindall et al.'s error-scaling predictions |
| 21 May 2026 | Tindall et al.'s paper is published, peer-reviewed, in *Science* 392, 868–872 |
| 18 Jun 2026 | Sels posts a related but distinct solo preprint on classical simulation of biclique-lattice spin glasses (arXiv:2606.20187) — it does not explicitly engage or dispute D-Wave's claim in its own text, so I have not treated it as a formal challenge here, only as adjacent context |
| 9 Jul 2026 | Krinitsin, Alert, Rizzi & Schmitt post their Comment narrowing the dispute to neural quantum states specifically |
| 16 Aug 2026 (today) | No further public reply from D-Wave to the Krinitsin comment found |
**Has anything been settled?** No single point has been conceded by either
side in a way that ends the dispute, but the *scope* of disagreement has
narrowed considerably since March 2025. Nobody in this exchange now disputes
that classical tensor-network and variational methods can match D-Wave's
quantum annealer on *some* lattice geometries and system sizes — that much
is empirically demonstrated and, in Tindall et al.'s case, itself
peer-reviewed in *Science*. What remains contested is narrower and more
specific: whether any classical method reaches the *hardest* instances
D-Wave tested (particularly the dimerized-biclique geometry and
highest-order correlators), and whether Tindall et al.'s predicted
error-scaling trend, once extrapolated further, would eventually catch up —
a question Nocera et al.'s August 2025 paper argues the current evidence
does not support. The exchange is live, not concluded: the most recent
substantive contribution is the July 2026 Krinitsin comment, and I found no
sign either side considers the matter closed.
---
## What would settle it
A pre-registered, adversarial joint benchmark would go furthest: before
running anything, D-Wave and a classical team (or several, since different
methods have different strengths) would publicly agree on a fixed set of
problem instances — including the dimerized-biclique lattice and the
highest-order correlators that classical work has not yet addressed — a
fixed error tolerance, and a fixed compute/time budget, all specified in
advance so neither side can adjust the target after seeing results. D-Wave
would need to publish full raw correlator data for those instances in an
open, versioned repository (not just summary statistics), so classical
methods could be scored without requiring access to D-Wave's proprietary
hardware. If a classical method met the pre-registered target within the
pre-registered budget, that would resolve the specific empirical question
for that instance class. It would not, however, settle the underlying
theoretical question — whether classical simulation of these dynamics is
fundamentally exponential in system size, or merely difficult with today's
best algorithms — because that is a computational-complexity claim, and no
one has a mathematical hardness proof for this problem. Empirical
benchmarks, however carefully designed, can narrow that question but cannot
close it the way a proof would.
---
## What an outsider can and cannot check
**Can check, without special access:**
- Both classical challenges are built on open-source software: the Flatiron
team's tensor-network work uses ITensor (a Flatiron-developed, publicly
available Julia library); the EPFL work uses NetKet (an open-source,
JAX-based library). Anyone with a standard workstation or modest cluster
can, in principle, rerun these classical simulations and check the
reported accuracies against the methods' own descriptions.
- The papers' stated error metrics, lattice sizes, and scaling arguments are
laid out in the preprints/publication text and can be checked
mathematically or reproduced computationally without needing D-Wave's
cooperation.
- D-Wave's original "millions of years on Frontier" figure is explicitly an
extrapolation from smaller, actually-run MPS simulations — the
extrapolation's assumptions are described in the paper and can be
scrutinized, though (see below) the underlying quantum comparison data
cannot be independently regenerated by most readers.
**Cannot check without D-Wave's hardware or cooperation:**
- The actual quantum annealer output — the primary experimental data this
entire dispute is about — comes from D-Wave's proprietary Advantage2
processor. Cloud access to D-Wave hardware exists commercially, but an
independent party cannot freely rerun D-Wave's exact experiment,
calibration, and gauge choices at will the way they can rerun open-source
classical code.
- D-Wave's own rebuttal to Flatiron (Nocera et al., arXiv:2508.15759) uses
the quantum processor's output *as the ground truth* against which
Tindall et al.'s classical predictions are tested — meaning the specific
evidence D-Wave offers against the classical challenge is itself only
regenerable by someone with access to D-Wave's hardware. This is a real
asymmetry: the classical side's work is fully open and independently
reproducible; part of D-Wave's counter-evidence is not.
- Any claims in D-Wave's press statements that I could not open directly
(see Notes) cannot be checked by me or, easily, by a general reader —
press releases are not data.
- The stock-price and financial context mentioned under Stakes comes from
search-engine summaries of pages I could not open; I flag it as
unverified rather than presenting it as confirmed fact.
---
## Notes on this run
Blunt, for whoever reads this next, not for the report's audience.
**What I could actually open and verify:** all five arXiv papers central to
this dispute — the original D-Wave claim (arXiv:2403.00910), the EPFL
challenge (arXiv:2503.08247), the Flatiron challenge (arXiv:2503.05693, both
abstract-page metadata and full HTML text), D-Wave's technical rebuttal to
Flatiron (arXiv:2508.15759), and the July 2026 NQS comment
(arXiv:2607.08811). I fetched these via arxiv.org, which was reachable, and
quote from verified full text in every case above.
**What failed to load, and why:** this sandbox's network egress policy
blocked essentially every non-arXiv domain I tried, including
dwavequantum.com (D-Wave's own press releases), quantumcomputingreport.com,
thequantuminsider.com, hpcwire.com, phys.org, datacenterdynamics.com,
techtimes.com, sciencedaily.com, stocktitan.net, sec.gov, osti.gov, and
en.wikipedia.org (all returned "EGRESS_BLOCKED" from the proxy — an
organizational policy block, not a site-specific failure). science.org and
nature.com returned their own 403/login-wall responses (paywall/bot
protection), independent of the egress policy. I also could not get
poppler-utils or a Python PDF library installed (both pip and apt access
were themselves blocked by the same egress policy) to extract text from
downloaded PDFs directly; I worked around this by using arXiv's HTML
rendering (`arxiv.org/html/...`) instead of the PDF, which worked.
**What this means for sourcing:** every direct quotation in this document
comes from a page I actually opened. Anywhere I report something D-Wave is
said to have stated in a press release (the "Quantum Supremacy Result
Stands" headline, the "does not reproduce the full scope... nor the hardest
problem instances" language, CEO statements, the stock-price reaction), I
have explicitly marked it as coming from search-engine summaries of pages I
could not open, not as a verified direct quotation, and I have avoided
quoting exact sentences from those sources. If you have a way to reach
dwavequantum.com or a news aggregator from this environment, re-verifying
those press statements against the primary source would strengthen this
report the most.
**What surprised me:** that the Flatiron paper was itself later published,
peer-reviewed, in *Science* — the same journal as the original claim — over
a year after it first appeared as a preprint. That is a stronger and more
checkable fact than most of what circulates in press coverage of this
dispute, and I think it deserves more weight than it usually gets in
summaries that treat this as "D-Wave vs. bloggers with a laptop." I was also
struck by how narrow the actual surviving disagreement is compared to the
public framing: nobody disputes that classical methods now match the
quantum annealer on several lattice geometries; the live argument is about
a specific, named remainder (the biclique lattice, the highest-order
correlators, and the long-run behavior of BP-TNS error scaling).
**What I'm unsure about:** (1) the exact calendar date of D-Wave's *Science*
publication — I have the month (March 2025) and full journal citation
(*Science* 388, 199–204) verified via a direct quote inside the Krinitsin
comment's own abstract, but not an exact day, since the specific-day sources
I found were all on blocked domains; (2) whether the "ran it on a laptop"
detail is accurate to the published Flatiron result or only to Tindall's
earliest prototyping, since I could not open the outlets reporting that
detail; (3) whether D-Wave has issued any private or non-press-release
technical response to the July 2026 Krinitsin comment that simply isn't
indexed yet — five weeks is not very long in journal-response timescales,
and my searches are not proof of absence.