h hoge.gg
Subscribe
BTC$67,432.18+2.34%ETH$3,521.44+1.08%SOL$178.62-0.62%BNB$612.30+0.41%XRP$0.6234-0.18%ADA$0.4521+3.12%DOGE$0.1623+1.86%AVAX$38.71-1.24%LINK$17.84+0.92%HOGE$0.00004120+4.21%
BTC$67,432.18+2.34%ETH$3,521.44+1.08%SOL$178.62-0.62%BNB$612.30+0.41%XRP$0.6234-0.18%ADA$0.4521+3.12%DOGE$0.1623+1.86%AVAX$38.71-1.24%LINK$17.84+0.92%HOGE$0.00004120+4.21%
● Bitcoin & Layer-1s

IOSCO Flagged Quantum Risk. Taproot Shows Bitcoin’s Exposure.

On 19 November 2026 IOSCO, the global body of securities regulators, told finance to prepare for quantum computing. The hardest case it describes is the one Taproot made Bitcoin's own.

The Quantum Memo Finally Crossed Into Wall Street

For most of the five years since Bitcoin activated Taproot, the question of whether a quantum computer could one day steal coins lived inside a small world: cryptographers on mailing lists, a handful of Bitcoin Improvement Proposals, and the occasional research paper that spiked the price of worry for a week before fading. It was a developer problem, argued in developer language, on developer timelines. Nobody at a pension fund lost sleep over it.

On 19 November 2026 that changed. The International Organization of Securities Commissions, the global umbrella body that sets the standards national market regulators follow, published its Final Report on the Implications of Quantum Computing on Financial Markets, a 63-page document telling banks, exchanges and asset managers to start preparing now. CoinDesk caught the mood in the one word the report kept circling: procrastination.

IOSCO members include the U.S. Securities and Exchange Commission, the U.K. Financial Conduct Authority and essentially every securities regulator that matters. When a body like that labels something a supervisory priority for 2027, it stops being a mailing-list argument and becomes an agenda item for the people who approve Bitcoin exchange-traded funds and license custodians. The report named Ethereum, Solana and Tron. It did not name Bitcoin. Yet the single hardest case it describes, a network whose exposed public keys cannot be forced to migrate and whose community is split on whether to freeze the coins sitting on them, is Bitcoin’s alone, and the reason traces straight back to the upgrade Taproot shipped in 2021.

What IOSCO Actually Put on the Record

The report, filed under reference FR/07/2026 and produced by IOSCO’s Fintech Task Force through a Quantum Computing Working Group stood up earlier in the year, is careful not to cry fire. It states plainly that no quantum computer capable of breaking the cryptography underpinning modern finance exists today, and that no member jurisdiction has reported one in operational use. The concern is timing. A sufficiently powerful machine, the report warns, “could have the ability to undermine critical financial market functions, like secure communications, within the next five years,” a window short enough that preparation cannot wait for proof.

IOSCO frames quantum as a “significant medium to long-term cybersecurity challenge” and leans on a phrase the security industry has used for years: “harvest now, decrypt later.” An adversary does not need a working quantum computer today to benefit from one tomorrow; it can record encrypted traffic or, in the case of a public blockchain, simply read data that is already permanent and wait. The recommendations are less about panic than hygiene: begin migrating to post-quantum cryptography, build what the report calls “crypto-agility” (the ability to swap one cryptographic scheme for another without rebuilding a system from scratch), and watch vendors for “quantum washing,” the practice of overstating what a quantum product can actually do.

The survey underneath the report is its most revealing part. Among IOSCO’s own members, roughly 55% have stood up cross-functional working groups or task forces on quantum, and only about 25% have dedicated teams, per the breakdown reported by Opalesque. In other words, the regulators writing the warning are themselves roughly half-ready. IOSCO Board chair Jean-Paul Servais, re-elected in May 2026 to a term running through 2028, has made digital-finance risk a throughline of his tenure, and the quantum report reads as an attempt to get ahead of a problem the sector has been content to file under later.

Why Blockchains Are the Report’s Hard Case

Most of the financial system can, in principle, be upgraded quietly. A bank can re-key its servers; a clearing house can roll out new certificates; a messaging network can negotiate a new cipher between two endpoints. Public blockchains cannot do any of that quietly, and IOSCO singled them out for exactly that reason. In the report’s description, “cryptography is embedded in core transaction structures and consensus rules, migration requires hard forks and the voluntary coordination of thousands of independent validators and node operators.” There is no administrator to push the update. There is only rough consensus, and rough consensus is slow.

Then there is the cost of the new cryptography itself. The elliptic-curve signatures Bitcoin and most chains use today run about 64 bytes. The post-quantum replacement NIST standardized as ML-DSA-44, the smallest parameter set of the FIPS 204 signature standard finalized in 2024, is roughly 2,420 bytes, something like 35 to 40 times larger. Bigger signatures mean fewer transactions per block, more bandwidth, more storage and higher fees. IOSCO cited a test on a quantum-resistant Solana testnet where throughput fell by about 90% once post-quantum signatures replaced the classical ones. For a network already fighting about block space, that is not a footnote.

Signature schemeTypeApprox. sizeWhat it means on-chain
ECDSA / Schnorr (secp256k1)Classical, quantum-vulnerable~64 to 72 bytesToday’s Bitcoin default; small, cheap, breakable by Shor
ML-DSA-44 (FIPS 204)Lattice, post-quantum~2,420 bytesBIP-360 working baseline; 35 to 40x larger, heavier blocks
SLH-DSA (FIPS 205)Hash-based, post-quantumSeveral kilobytesConservative fallback; very large, very well understood
Observed throughput impactSolana PQ testnetAbout -90%The figure IOSCO cited for blockchains

The Asset IOSCO Did Not Name

The report’s worked examples are Ethereum, Solana and Tron, as Bitcoin Magazine noted, and the omission is understandable: those are the smart-contract and high-throughput chains where regulators increasingly see tokenized funds and stablecoins settling. But the specific failure mode IOSCO spends the most words on is not really a smart-contract problem. The report warns that if an attacker could recover a private key from an exposed public key, the attacker could use it to authorize a transfer, and that older holdings may need to migrate to new address types or stay vulnerable indefinitely. That is a description of coins sitting in the open, with no one able to compel their owners to move them.

No major network fits that description like Bitcoin. Roughly 6.9 million BTC, about a third of the circulating supply, already sit on addresses whose public keys are visible on-chain, according to analysis compiled by AMINA Bank. Some of that is the earliest mining era, when coins were paid directly to raw public keys. Some is ordinary address reuse. And a growing slice is structural, baked into the address format Bitcoin adopted in 2021. The regulator described the disease in careful, chain-agnostic language and declined to name the most obvious patient.

Taproot and the Reveal-the-Key Problem

Taproot activated at block 709,632 on 14 November 2021, after roughly 90% of miners signaled support, the last soft fork Bitcoin has managed to ship. It bundled three Bitcoin Improvement Proposals: BIP 340 brought Schnorr signatures, BIP 341 defined the Pay-to-Taproot output and its MAST script trees, and BIP 342 updated the scripting language. Together they let multisignature and complex spending conditions look, on-chain, like an ordinary single-key payment. That privacy and efficiency win is real, and it is why wallets and protocols kept adopting bc1p addresses long after the Ordinals boom that first drove Taproot usage had cooled.

But Taproot made one trade that matters enormously in a quantum frame. A legacy or common SegWit address hides your public key behind a hash; the key only becomes visible when you first spend, which is why security guides have told people for a decade not to reuse addresses. A Pay-to-Taproot output does the opposite. The spending key, tweaked but still a valid public key, is the output itself, written in the clear the moment the coins land. Every key-path Taproot output is therefore exposed at rest, not just at spend time. Taproot did not invent on-chain key exposure, the earliest coins had it, but it made exposure the default for Bitcoin’s most modern address type, which is why the exposed-supply number keeps drifting up even as address-reuse hygiene improves.

This is the quiet irony that ties the IOSCO report back to Bitcoin’s own roadmap. The feature the ecosystem celebrated in 2021 for its elegance is the same feature that, read through a 2026 regulator’s risk lens, turns a rising share of the supply into standing targets. Taproot’s share of transactions, which peaked above 40% in early 2024, has settled closer to 20% as inscription demand faded, per adoption tracking cited by Cryptonews. Even at 20%, every one of those outputs is a public key in the open.

How Close Is the Machine, Really

IOSCO’s five-year horizon is deliberately fuzzy, and the Bitcoin-specific numbers that exist are sharper. In March 2026, research from Google Quantum AI, reported by CoinDesk, cut the estimated cost of breaking Bitcoin’s signature scheme to fewer than 500,000 physical qubits, down from earlier guesses in the millions. The concrete attack model needs on the order of 1,200 to 1,450 high-quality logical qubits; given Bitcoin’s roughly ten-minute block time, a machine like that could forge a competing transaction for an exposed key in about nine minutes, with something like a 41% chance of beating the legitimate spend into a block. Google’s own milestone for useful quantum systems sits around 2029.

Two caveats keep this from being a doomsday clock. First, not all of Bitcoin is equally exposed: Shor’s algorithm threatens signatures, but the mining and hash functions that secure the chain’s history face only Grover’s algorithm, which offers a mere quadratic speedup and is defended by larger parameters. Second, logical qubits are not fungible across hardware; a neutral-atom machine and a superconducting machine quoting the same logical-qubit count are not equivalent, so headline numbers deserve suspicion. The honest summary is the one IOSCO landed on: no machine today, a credible path to one inside the decade, and an upgrade that will take years whenever it starts.

Address typePublic key on-chain?Quantum exposure
P2PK (early mining era)Always, in the clearExposed from creation; about 1.7M BTC
P2PKH / P2WPKH (hash-based)Hidden until first spendSafe at rest if never reused
P2TR / Taproot (bc1p)Yes, the tweaked key is the outputExposed at rest from funding
P2MR / BIP-360 (proposed)Behind a post-quantum commitmentQuantum-resistant, not yet on mainnet

Harvest Now, Forge Later

The phrase IOSCO borrowed, “harvest now, decrypt later,” describes an attacker hoovering up encrypted messages today to decrypt once a quantum computer arrives. For most of finance that is a confidentiality problem with a shelf life: a message intercepted in 2026 may be worthless by the time it can be read. Bitcoin inverts the arithmetic. The target is not a transient secret but a public key that is permanent by design, and the prize is not information but bearer assets that do not expire. Call it harvest now, forge later. An attacker can catalog every exposed output years in advance and spend them the morning a capable machine switches on.

That permanence is why the Bitcoin version of the problem is harder than the bank version, and why a regulator worried about critical market functions should, logically, worry more about a bearer instrument than about a single encrypted session. It also explains the strange shape of the defense. You cannot simply rotate a compromised key after the fact, because by the time the key is compromised the coins are already gone. The only durable fix is to move value, ahead of time, into an output type whose public key is not sitting in the open. Which is exactly what Bitcoin has spent 2026 trying, and failing, to agree on how to build.

The Fix Bitcoin Is Building: BIP-360

The leading technical answer is BIP-360, a new output type its author Hunter Beast calls Pay-to-Merkle-Root. It was merged into the Bitcoin Improvement Proposals repository in February 2026, a milestone that sounds bigger than it is. Merging a BIP means the idea has a number and a specification, not that anything runs on mainnet. As of this writing the spec sits at version 0.12.1, there are no Pay-to-Merkle-Root outputs on the Bitcoin network, and, crucially, BIP-360 does not itself add a post-quantum signature. In its own words, the proposal “does not include the introduction of post-quantum signature schemes.” It builds the garage; the car comes later.

What BIP-360 does is model a quantum-safe address closely on Taproot while removing the key-path spend that leaks the public key, and reserve room for a future signature scheme (ML-DSA-44 is the working baseline) inside the structure, with the SegWit witness discount softening the fee hit from those much larger signatures. The reference material from Spark’s BIP-360 explainer is blunt about the gap: the format is the easy part. The hard parts, agreeing on which signature scheme, activating it through a soft fork, and migrating millions of coins off exposed keys without trampling anyone’s property, are all still ahead. A quantum-safe address nobody can use yet protects nobody.

The Fight IOSCO Described Without Naming It

When IOSCO wrote that migration depends on the voluntary coordination of thousands of independent validators and node operators, it was describing, in neutral supervisory prose, the most emotional argument in Bitcoin. The question is simple to state and vicious to answer: what happens to the roughly 6.9 million coins on exposed keys if their owners, some of whom are lost, some of whom may be Satoshi, never move them?

Jameson Lopp, the Casa co-founder who has become the debate’s most careful referee, lays out the trap in a widely cited essay. “The quantum migration debate is far more nuanced than just a question between freezing or not freezing vulnerable bitcoin,” he writes, before delivering the line that has stuck: “Every serious option violates a principle that Bitcoin users care about.” Doing nothing preserves the rules but hands a future attacker a third of the supply. Freezing the vulnerable coins prevents the theft but retroactively voids valid spending conditions, which is confiscation by another name. Forcing migration by a deadline is prudent engineering that looks, from the wrong angle, like deadline-backed seizure. Lopp’s own position is conditional: he would support deprecating today’s signatures only given a viable alternative, a long migration window, narrow and objective rules, and rescue options for frozen funds, and only, in his words, “unless it looks highly likely that a cryptographically relevant quantum computer is less than 10 years away.”

A companion proposal, BIP-361, sketches the sunset mechanism that would eventually make legacy signatures unspendable. It is a roadmap, not a scheduled event, and nothing about it has been activated. The governance problem IOSCO flagged in a single sentence is, for Bitcoin, the whole ballgame.

Bitcoin Cannot Fork on Command

Even if Bitcoin agreed tomorrow on a quantum-safe signature and a migration plan, it would still have to activate the change, and 2026 has been a long demonstration of how hard that has become. The last successful soft fork was Taproot, five years ago. Since then, every attempt has stalled. The covenant proposal OP_CTV (BIP-119) has a live signaling window that opened in March 2026 and, as the Spark covenant tracker shows, has drawn essentially 0% miner support against a 90% threshold, with the window timing out in March 2027. OP_CAT (BIP-347) has a complete specification and no activation path at all.

The nearest thing to momentum is BIP-54, the Great Consensus Cleanup, a feature-free bundle of bug fixes. Its co-author Matt Corallo put roughly 80% odds on it being Bitcoin’s next soft fork, while cautioning that developers see the earliest realistic activation in late 2027 and more likely 2028. Blockstream chief executive Adam Back has gone further, musing publicly that covenant opcodes might be Bitcoin’s last soft fork, after which the base layer ossifies. If a feature-free cleanup almost everyone agrees on is a multi-year project, a contested, consensus-breaking quantum migration is a far longer one. IOSCO warned that blockchain migration could be slow and fragmented. For Bitcoin, that is not a forecast; it is the track record.

ProposalWhat it doesStatus (late 2026)
BIP-54 (Consensus Cleanup)Fixes four old bugs, no new features~80% odds as next fork; earliest 2027 to 2028
OP_CTV (BIP-119)Covenant opcode for vaults, pools~0% signaling; window times out Mar 2027
OP_CAT (BIP-347)Re-enables stack concatenationSpec complete; no activation path
BIP-360 (P2MR)Quantum-safe address formatMerged Feb 2026; draft, not on mainnet
BIP-361Sunset of legacy signaturesConcept and roadmap only

What This Lands on the SEC’s Desk

IOSCO does not regulate anyone directly; it sets standards members are expected to implement. That is precisely why the report matters for U.S. readers. The Securities and Exchange Commission is an IOSCO member, and when IOSCO says it will keep quantum a supervisory priority through 2027, the message routes to the SEC and its peers. Chair Paul Atkins, who has run the agency since April 2025, has spent the year on a friendlier crypto posture than his predecessor, approving and standardizing the spot Bitcoin products that now hold a meaningful slice of the supply. Those approvals are the reason a quantum warning aimed at blockchains is also, quietly, a warning about products the SEC signed off on.

The most immediate supervisory hook is disclosure. IOSCO’s quantum-washing caution runs both ways: a regulator that polices firms for overstating quantum readiness will eventually ask whether an issuer has understated quantum risk. A spot Bitcoin ETF whose underlying holds coins on exposed keys carries a risk factor that, as of today, most prospectuses treat in a line or two. If a securities regulator starts naming quantum as a priority, that line or two gets longer. The same exemptive machinery that let these products reach the market without a bespoke rulebook is the machinery that will have to absorb a risk nobody underwrote for.

The Custody Exposure Nobody Prices

Self-custody advice has a reflex for most threats: move to cold storage, keep keys offline, shrink your attack surface. Quantum breaks the reflex, because an air-gapped hardware wallet does nothing for a public key already published on-chain. If your coins sit in an exposed Taproot or reused output, the vault door is irrelevant; the attacker is not coming through your device, they are coming through the ledger everyone can read. That inversion is worth remembering the next time a comparison of exchanges and custodians leans on cold-storage percentages as a proxy for safety.

For institutions the problem is organizational, not personal. A custodian holding client Bitcoin cannot unilaterally migrate it to a quantum-safe format that does not exist yet, and when one does exist, moving large balances will be a visible, fee-heavy, consensus-dependent exercise. IOSCO’s prescription, crypto-agility, is easy to write into a report and hard to retrofit into a system that assumed secp256k1 forever. The institutions most exposed are the ones that built the deepest around Bitcoin’s current cryptography, including the custodians behind the ETFs and the tokenized-asset rails regulators are now encouraging onto public chains. The report’s quiet point is that crypto-agility should have been a design requirement years ago, and for most of this market it was not.

Does the Market Price Any of This

Not visibly. Bitcoin traded near $58,900 on 21 November 2026, down about 5% on the day and roughly 14% on the week, and sitting more than 53% below the $126,080 all-time high set in late 2025, per CoinGecko. The move had nothing to do with qubits and everything to do with a brutal fourth-quarter drawdown, the kind of tape where a five-year risk struggles to compete for attention with next month’s macro calendar. Readers tracking the December countdown of Fed and policy catalysts will recognize the dynamic: quantum is a 2029 problem in a market obsessed with the next three weeks.

A few analysts have tried to put a number on the ignored tail. Charles Edwards of Capriole Investments has floated what he calls a Quantum Discount Factor, arguing that an unresolved quantum threat should shave a measurable premium off fair value until Bitcoin commits to a fix. On-chain analyst Willy Woo has taken the other side, contending that Bitcoin will adapt rather than break, because it always has. Both can be right at once: the protocol probably does adapt, and the path there is messy enough to deserve a discount. What changed on 19 November is not the odds of a quantum computer; it is that a securities regulator, not a cypherpunk, is now helping keep the clock. For holders weighing where Bitcoin finds a floor, that sits alongside the harder question of what actually supports the price in a drawdown.

What to Watch Into 2027

The IOSCO report does not change a line of Bitcoin’s code. What it changes is the audience. A debate Bitcoin has been having with itself now has a supervisory clock attached, and the next year holds a handful of concrete markers worth watching.

  • Whether BIP-360 moves from a merged draft to an activation client with real parameters, the first sign the quantum fix is leaving the whiteboard.
  • BIP-54 as the canary: if Bitcoin cannot activate a feature-free cleanup by 2028, a contested quantum migration is years further out than any roadmap admits.
  • The OP_CTV signaling window timing out in March 2027, a reminder of how little miner appetite there is for any change at all.
  • IOSCO’s promised 2027 quantum work program, and whether the SEC and its peers translate it into disclosure expectations for crypto products.
  • Any credible hardware milestone that narrows the gap to a cryptographically relevant machine, which would move the debate from principle to panic overnight.
  • Plain address hygiene: every holder who stops reusing addresses and avoids parking long-term savings on exposed keys shrinks the problem at the margin.

The through-line of 2026 was that Bitcoin’s hardest problems are no longer technical, they are social, and social problems do not resolve on a regulator’s calendar. IOSCO gave the quantum question a deadline it cannot enforce. Whether Bitcoin treats that as a prompt or an intrusion is the story of the next five years, and it will be settled the way the freeze debate will: by rough consensus, slowly, in public, with a third of the supply watching from the open.

Frequently Asked Questions

Did IOSCO say Bitcoin is about to be hacked by a quantum computer?

No. The report states that no quantum computer capable of breaking today’s financial cryptography exists, and none is in operational use. Its warning is about timing: a capable machine could emerge within five years, and the upgrades to defend against it take years, so preparation should start now rather than after a breakthrough.

Why does Taproot make Bitcoin more quantum-exposed?

A Pay-to-Taproot (bc1p) output publishes its spending public key on-chain the moment it is funded, unlike older hash-based addresses that hide the key until a first spend. That makes every key-path Taproot output exposed at rest, adding to the roughly 6.9 million BTC already on visible public keys from early mining and address reuse.

What is BIP-360 and does it fix the problem?

BIP-360 defines Pay-to-Merkle-Root, a quantum-safe address format merged into Bitcoin’s proposal repository in February 2026. It builds the structure for a post-quantum signature but does not add one itself, has no outputs on mainnet, and still needs a soft fork, a chosen signature scheme, and a migration plan before it protects any coins.

Could Bitcoin just freeze the vulnerable coins?

It could in theory, but the community is divided. Freezing exposed coins would stop future theft while retroactively voiding valid spending rights, which critics call confiscation. As Jameson Lopp argues, every serious option, doing nothing, freezing, or forcing migration, violates a principle Bitcoin users care about, which is why no plan has been agreed.

How does this affect Bitcoin ETFs and US investors?

The SEC is an IOSCO member, so IOSCO’s push to make quantum a 2027 priority reaches U.S. supervisors. The likeliest near-term effect is disclosure: regulators that warn against overstating quantum readiness may also ask issuers to spell out quantum risk, which most Bitcoin ETF prospectuses currently address only briefly.

By Marcus Okafor, senior markets editor at HOGE Wire, covering Bitcoin’s base layer and the politics of its upgrades.

Share 𝕏 Post Telegram