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

Bitcoin’s Quantum Risk Is a Migration Question — November 15, 2026

Nov 15, 202610 minAudio

Note: The Bitcoin exposure estimate discussed in this episode is Glassnode's: about 7.12 million BTC, or 35.4% of Bitcoin's supply, sits in addresses whose public keys are already visible on-chain. An editing step removed the sentence that gave the figure. A Sunday think piece on what crypto quantum-exposure estimates do - and do not - tell us about readiness. We separate plans, demonstrations and custody offerings from completed network migrations. Ethlabs Drops Quick Slots Push to Chase a Post-Quantum Ethereum by 2027 - Bankless The First Post-Quantum sBTC Transfer on Stacks Mainnet - Stacks Labs Introducing Strongpoint MPC: Post-Quantum MPC, Without the Compromises - Project Eleven Chapters 00:00 Today's headlines 00:30 What exposed means for public keys 02:12 The case for moving early 03:31 The caution about rushing 04:48 The Stacks post-quantum sBTC transfer 06:04 Project Eleven's Strongpoint MPC custody 07:16 Here is my read on readiness Source links analyticsinsight.net blog.mexc.com ccn.com crowdfundinsider.com cryptobriefing.com quantumzeitgeist.com theblock.co tradingview.com tradingview.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.

So how much weight should each kind of evidence carry? Today is our Sunday think piece in four parts, pulling together pieces we covered as quick hits into one migration question. Welcome back to Quickly Quantum, your daily brief on the quantum frontier. It's Sunday, November 15, 2026. Let's get into it.

Part one: what does “exposed” mean here? A public key is information used to verify a digital signature, and a private key is the secret that authorizes control. The concern is that a sufficiently capable quantum computer might derive a private key from an exposed public key. That describes a possible future attack path. It does not mean those coins have been stolen, and it does not mean such a machine exists today. That distinction matters because the debate can slide from a measurable property of addresses into a claim about immediate losses, and for you those are different things. Exposure identifies a condition that could matter if the relevant computing capability arrives, while migration means changing the cryptographic machinery and getting users, wallets, custodians and network rules to work with it. The first can be counted. The second is coordination across a live system. We have also covered, in separate quick hits, an Ethlabs proposal for a post-quantum Ethereum target in 2027, a Stacks post-quantum sBTC transfer, an XRP Ledger plan for quantum-resistant accounts, and a custody offering described by Project Eleven on its company blog. That is the shape of the debate today: a risk estimate alongside proposals, a demonstration and a product. Those categories should not be blurred. A proposal sets an intended direction; a demonstration shows a particular operation; a product describes what its maker offers. None of those descriptions alone says an entire network has migrated. So the question for this Sunday is not whether the word quantum belongs in a crypto headline. It is how much weight we should put on the different kinds of evidence, and what each one leaves for the next stage of work.

Part two: the case for moving early. Ethlabs’ proposal, which we covered as a quick hit, points toward a 2027 post-quantum target for Ethereum. Post-quantum cryptography means methods designed to resist attacks from quantum computers. The appeal of acting early is straightforward: changing cryptography in a live network takes planning, and waiting until a threat is immediate would leave less room to coordinate. But a target date is a plan, not a completed migration. Ethereum’s transition would involve more than selecting a new signature method; accounts and the software around them would have to support the change, while the network continues to operate. The details available for today’s episode do not let me responsibly say how much of that work is finished or that the proposed date is assured. Here is where I agree with the early-action argument: preparation can be valuable before a threat is imminent, especially when the change touches users and infrastructure rather than one isolated machine. Where I am less persuaded is any leap from we should prepare to this particular deadline proves the transition is ready. A date can focus engineering effort. It cannot substitute for the engineering. And that is why the Bitcoin number, on its own, does not settle the schedule for Ethereum or anyone else. It concerns a different network, and the practical response depends on the system being changed. The shared issue is urgency; the actual work is network-specific.

Part three: the caution about rushing. A hurried cryptographic change can create its own problems if the protocol, wallets and users do not move together. That concern is especially relevant when a proposal is described in terms of a target year: the calendar is easy to understand, while the work behind it is less visible. I agree with the caution that a post-quantum label should not be treated as proof that a system is ready. A secure design still has to be implemented and adopted. At the same time, caution cannot become a reason to leave preparation until the danger is close. The Bitcoin exposure estimate gives the conversation a concrete condition to examine, but it does not tell us when a capable quantum attacker will exist or when any particular migration must finish. That leaves two uncertainties in the same frame. We do not have a present-day quantum break of these systems in the reporting for this episode, and we do not have a completed migration to point to. That is not a contradiction, it is the actual planning problem. Teams have to decide how to build resilience under uncertainty without presenting a proposal as a finished safeguard. For you, the useful distinction is between evidence of exposure and evidence of readiness. A figure about public keys speaks to the first. A working change, adopted across the relevant network, would speak to the second. Keep those claims separate when the headlines compress them.

Part four, first half: the Stacks demonstration. We have previously covered its post-quantum sBTC transfer as a quick hit. The important distinction is what a demonstration can establish: it can show that a particular kind of operation has been carried out using a different cryptographic approach. It does not, by itself, establish that a whole network has changed its rules or that every user’s assets have moved to a new form of protection. That makes demonstrations useful, even when they are bounded. They can put an abstract proposal into a concrete technical setting and expose the practical questions that a roadmap can leave unanswered. But the scope matters. A single transfer and a network-wide migration are different claims, and the language around each should preserve that difference. I find this kind of evidence more informative than a promise alone, because it points to an operation someone says they performed. I still would not treat it as a verdict on broader readiness. The question is what the demonstration covers and what remains outside it, not whether post-quantum appears in the announcement. This also gives us a way to read the wider collection of responses without forcing them into a single race. A transfer demonstration, an account plan, a target date and a custody product each address a different part of the problem. They may all matter, but they do not answer the same question.

Part four, second half: the custody approach is another distinct piece. Project Eleven says on its company blog that its Strongpoint MPC offers post-quantum custody. MPC, or multi-party computation, is a way for multiple participants to contribute to a signing process without relying on one participant to hold the complete secret. Custody is only one layer of the broader migration picture. It does not establish that the underlying networks have changed their cryptography, or that every asset held elsewhere has the same protection. I think it is sensible to distinguish a product is offered from the ecosystem has transitioned. That is not a knock on the product, it is a boundary around what the claim tells us. The same discipline applies to the XRP Ledger account plan we have covered: a plan for quantum-resistant accounts is evidence of planning, while implementation and adoption are separate milestones. The most useful point in this set of approaches may be their variety. Some work is aimed at network protocols, some at account design, some at a specific transaction, and some at custody. Variety can be a sign that people are approaching the problem from the layers they control. It also means there is not one announcement that resolves the whole question.

Here is my read. I am fairly confident that the conversation has become more concrete, because we have an exposure estimate alongside multiple kinds of proposed, demonstrated and offered responses. I am much less confident about treating that as proof that the systems are close to safe, or close to broken. Those are stronger conclusions than these categories support. The distinction I want to keep is between a warning that can guide preparation and a claim that a transition has happened. An exposed public key is relevant to a possible future capability; it is not a report of a present theft. A proposed deadline can help organize work; it is not the finished work. A demonstration can show a bounded operation; it is not the same as changing an entire network. And a custody product can address custody without settling what the networks themselves will do. I am glad the discussion is moving beyond a vague argument over whether quantum risk deserves attention. The different approaches give us concrete things to evaluate, but I would change my view about readiness only with evidence that clearly shows what has been implemented, where it operates, and how broadly it has been adopted. The estimate alone cannot answer how quickly Bitcoin should move, and an Ethereum target alone cannot establish that a full transition is achievable on that schedule. The open questions are therefore practical ones: how quickly can networks change without disrupting their users; who carries the work of adapting wallets, custodians and other services; and how should a system respond if the threat develops faster than its migration? Today leaves those questions unresolved. When you see the next quantum headline, ask which piece it actually documents, and whether it describes exposure, a plan, a demonstration or a completed change. That habit will serve you better than any single forecast about quantum computing timelines. Time for the Hype Check. I would give this discussion a six out of ten for substance: the exposure estimate and the distinct response paths are meaningful, while the strongest limit is that none of the items described here establishes a completed network-wide migration.

If you value this kind of careful separation between a risk estimate and a finished transition, follow Quickly Quantum wherever you listen. 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 Space Stakes: the business of the new space race, every day. What actually flew, what the contract is really worth, and who has customers. 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