Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Quickly Quantum

Quickly Quantum artwork

IonQ’s 74x qLDPC Speedup: What the Number Actually Shows — October 7, 2026

Oct 7, 202610 minAudio
ShareXLinkedInFacebookWhatsAppEmail

IonQ's qLDPC work reports up-to speedups for logical operations, while Xanadu, Pasqal, Infleqtion, and Cisco announce manufacturing, component, and network developments. We also hear a perspective on open problems in quantum research. Xanadu and GlobalFoundries manufacturing partnership - Quantum Computing Report Pasqal and the Q-PLANET pilot line - The Quantum Insider Chip-scale optical cavity - The Quantum Insider Quantum research problems - @Isaac__kim on X Cisco quantum network software prototypes - The Quantum Insider qLDPC with scheduled error correction - IonQ IonQ announcement - @ionq_inc on X Cisco network control plane - @NetworkWorld on X Chapters 00:00 Today's headlines 00:39 Xanadu photonic hardware heads to GlobalFoundries 01:36 Pasqal leads Q-PLANET neutral-atom pilot line 02:45 Infleqtion prototypes smaller optical cavity 04:01 Cisco quantum network controller 04:52 IonQ logical Clifford operations 06:41 Hype check on IonQ's 74x speedup claim Source links infleqtion.com @infleqtion on X globenewswire.com quantumcomputingreport.com Quickly Quantum is an AI-voiced podcast, built and run by a real person. Nothing in this episode is financial advice. Follow Quickly Quantum: subscribe on YouTube · Apple Podcasts · Spotify More from Brian Lampert: Concrete Compute, the daily AI infrastructure briefing, and Space Stakes, the business of the new space race. Transcripts and every episode: quickly-quantum.kngoworld.chatgpt.site.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show.

Up to 74x faster logical Clifford operations—that's the headline IonQ is putting on a new approach to quantum error correction, and the question is how much of that speedup reaches a useful quantum computation. Before that, Xanadu takes photonic hardware toward commercial chip manufacturing, while Pasqal and Cisco make separate moves on supply chains and quantum networks. Welcome back to Quickly Quantum, your daily brief on the quantum frontier. It's Wednesday, October 7, 2026. Let's get into it.

A photonic quantum component is headed toward a commercial semiconductor production line: Xanadu has announced a multi-year manufacturing partnership with GlobalFoundries, according to Quantum Computing Report. The work will transfer Xanadu's photonic hardware design processes onto GlobalFoundries' 300 mm commercial fabrication facility in Malta, New York. The focus is ultra-low-loss silicon nitride optical circuits, which route photons, and superconducting nanowire single-photon detectors, which read them out. Now, why should you care about a factory partnership? Because a quantum design that only works as a lab prototype has a long road to becoming a repeatable product. Xanadu and GlobalFoundries are aiming to establish manufacturing for components used in Xanadu's fault-tolerant photonic architecture, with future demonstrators and commercial deployments in view. That's an industrialization plan, not evidence of volume shipments today. Still, getting the design onto a commercial 300 mm line is a concrete step toward making photonic hardware at manufacturing scale.

€50 million over three years, with 28 partners from 11 European countries: that's the scale of Q-PLANET, the neutral-atom chip pilot line Pasqal is coordinating, according to The Quantum Insider. The consortium will develop lasers, atom chips, microfabricated vapor cells, and manufacturing design kits. Pasqal will lead development of 1013 nm chip-based laser sources and support testing and validation of components for quantum computing, sensing, and communications. For a newcomer, neutral-atom computers use individual atoms as the building blocks of quantum information. This project is about developing the industrial components those systems need, rather than announcing a new computer. Pasqal's CTO, Loïc Henriet, said, "Three months after our kick-off in Brussels, Q-PLANET has moved from ambition to execution. Together with our 28 partners, we are building a European supply chain for neutral-atom technologies, while bringing quantum industrialization closer to concrete user needs," in The Quantum Insider. The useful test is whether the pilot line produces components that teams can build with; the project's budget and partner list are a commitment to that work, not proof that the supply chain is already operating at scale.

The prototype was fabricated on a silicon nitride chip at Honeywell Aerospace's photonics foundry. An optical cavity helps stabilize laser light, which matters for quantum sensors, clocks, and computers. Infleqtion CTO Pranav Gokhale called it "an important step toward that future" of smaller, more stable, manufacturable quantum systems. UC Santa Barbara Distinguished Professor Daniel J. Blumenthal said the prototype represents "a meaningful step forward." Those are optimistic assessments from the teams involved; the demonstrated result described here is a prototype, and the announcement provides no size-reduction factor or stability measurement. For you, the practical point is straightforward: shrinking a supporting component may make quantum sensors easier to deploy, but the next evidence is performance in a real system.

A post from @Isaac__kim on X takes a different angle, listing problems across quantum information, many-body physics, and quantum computing. The larger point he is making is accessible: even as quantum hardware attracts attention, foundational questions across the field remain difficult. @Isaac__kim posted on X, "Things are changing fast. I cannot even imagine what will happen over the next few months, let alone a year." That's the poster's view of the pace of research, not a measured forecast.

Quantum networks need software to coordinate connections as well as hardware to make them. Cisco has introduced a Quantum Network Controller and an updated Network-Aware Quantum Compiler as research prototypes, according to The Quantum Insider. Cisco says its software coordinated equipment from multiple vendors across about 11 miles of commercial fiber in New York City, achieving greater than 99% polarization fidelity at room temperature. Fidelity is a measure of how closely a delivered quantum state matches the intended one. That result is Cisco's, and the company's announcement describes the software as research prototypes, not commercially available products. @NetworkWorld posted on X: "Cisco readies new control plane for quantum networks." The significant idea is that applications might request a connection and let software handle the underlying equipment. If that works beyond a prototype, you could build network services without manually configuring each link.

IonQ's blog describes work by researchers Mark Webster and Nicolas Delfosse on quantum low-density parity-check codes, or qLDPC codes, a way of protecting quantum information with checks that can reduce the physical-qubit overhead of error correction. Why does that matter? A quantum computer's information is fragile, so error correction uses extra physical qubits and repeated checks to protect a more reliable logical qubit. The familiar surface-code approach uses local checks on a two-dimensional grid; according to IonQ's blog, surface codes often require hundreds or thousands of physical qubits for a single logical qubit. qLDPC codes can reduce that hardware overhead by allowing non-local interactions, but those interactions make operations harder to coordinate. The challenge is to gain the hardware savings without losing time to the correction process. IonQ's proposed answer is to measure multiple commuting logical operators jointly, rather than measuring them one at a time. In plain English, the team groups compatible checks so they can be handled together. Classical scheduler codes—a set of instructions for ordering those measurements—help detect and correct errors across the group while reducing the number of physical measurements required per logical Pauli. Then comes logical CliNR, a version of Clifford Noise Reduction adapted to logical gates. CliNR prepares and verifies a state offline, then uses that state to apply an operation. IonQ describes a hybrid physical/logical strategy: parts of the method run at the physical level and parts at the logical level, and measurement protocols merge resource-state preparation with verification. IonQ achieves up to a 74x speedup for logical Clifford operations and up to 5x for critical Toffoli gates compared to traditional sequential methods. IonQ's X post likewise attributes the up-to figures to its team's strategy.

So what does the 74x tell you? It's a striking result for the operations and comparison IonQ describes, and it points directly at a real engineering bottleneck: error correction can consume time as well as hardware. But the figure is an up-to speedup, and the available description doesn't give the baseline, code distance, or error regime behind it. That makes the number a reason to examine the protocol, not a general promise that every fault-tolerant computation will run 74 times faster. The distinctions matter. IonQ reports up to 3x speedup for state preparation and logical gates from protocols that allow multiple logical measurements to be performed jointly, compared with sequential logical measurements. It separately reports up to 74x for logical Clifford operations and up to 5x for Toffoli gates with logical CliNR. Those are different results and comparisons within the company's description; they shouldn't be blended into one all-purpose speed figure. That is the company's characterization of its work. The blog argues that faster Clifford and Toffoli operations could support deeper fault-tolerant algorithms sooner, and that higher shot output could increase computational value per dollar of machine runtime. Those are potential enterprise benefits, not measured customer outcomes in this announcement. Here's my read: the most interesting part isn't the largest multiplier; it's the attempt to make qLDPC's lower hardware overhead useful without allowing scheduling and error correction to become the new bottleneck. That is exactly the kind of systems problem a fault-tolerant machine has to solve. And a result tied to specific operations is more informative than a vague claim of faster quantum computing. The caution is equally specific. IonQ's announcement supplies up-to speedups, while the benchmark conditions needed to judge how broadly they apply aren't given in the description we have. A strong next step would be seeing the method and its comparison conditions in enough detail to assess how the performance changes across workloads and error regimes. Until then, this strengthens the case that qLDPC operations can be accelerated through scheduling and hybrid execution; it doesn't settle how much faster a useful end-to-end algorithm becomes. Time for the Hype Check. My substance rating is 6 out of 10: the technique and the reported up-to speedups are concrete, but the headline number needs its benchmark conditions before it can carry a claim about real workloads. If those details hold up, IonQ has a meaningful route around qLDPC latency; if they don't, the 74x stays a narrow result. The teams building fault-tolerant machines gain if the speedup generalizes, while customers lose time and money if an impressive gate-level result never translates into faster workloads.

Follow Quickly Quantum wherever you listen, and you'll get the next step in this story without needing to decode the whole field alone. This has been Quickly Quantum, an AI-voiced podcast, created and built by a real human using today's cutting-edge technology. Nothing you heard on this show is financial advice. I'm Brian Lampert, and I'll catch you all tomorrow — take care!

Watching on YouTube? Hit subscribe, and tomorrow's briefing will be waiting for you. I also host Concrete Compute: a daily briefing on the AI buildout. The datacenters, the megawatts, and who actually pays for them. Find it wherever you get your podcasts.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Willow Tests Measurement Contextuality at 72- and 105-Qubit Scale — November 20, 2026

    Nov 20, 202618 minAudio

    Explainer: harvest now, decrypt later - Wikipedia memQ and Infleqtion Sign MoU to Advance Networked Quantum Computing - Infleqtion SEALSQ Signs LOI to Acquire QuintessenceLabs - The Quantum Insider Chapters 00:00...

    Credit the people on this episode

  2. Finance Gets an Immediate Quantum Warning — November 19, 2026

    Nov 19, 202617 minAudio

    A global securities regulator has urged the financial sector to act on quantum risk, with blockchain systems singled out as potentially exposed. We also cover hardware roadmaps, location verification, quantum...

    Credit the people on this episode

  3. IQM’s 150-Qubit Start Comes With an Upgrade Promise — November 18, 2026

    Nov 18, 202617 minAudio

    IQM’s Halocene programme promises continuity through hardware upgrades, while today’s other stories examine quantum-safe telecom, national-security concerns, funding and emerging computing systems. The episode separates...

    Credit the people on this episode

  4. Can Quantum Chips Fit the Supercomputer? — November 17, 2026

    Nov 17, 202619 minAudio

    IBM, NVIDIA and Fermilab plan a modular quantum-classical platform, while new announcements address scheduling, error correction and quantum-safe communications. We also cover DOE testbed planning, U.S. chip-access...

    Credit the people on this episode

  5. Moth's 1,568-Value Test Takes On Quantum Data Loading — November 16, 2026

    Nov 16, 202616 minAudio

    Moth Quantum reports a larger data-loading and recovery demonstration on IBM processors, while the episode examines readout costs and the distance between device specifications and useful workloads. Other stories cover...

    Credit the people on this episode