Not Panic, But Preparation: What New Quantum Policy Means for Bitcoin Developers

Builder Notes from Bitcoin House Malaysia

Two Events, One Week: Why This Moment Matters

On June 22, 2026, President Trump signed two executive orders that moved quantum computing from a research priority to a national strategic mandate. The first, "Ushering in the Next Frontier of Quantum Innovation," launches a whole-of-government effort to build a scientifically relevant quantum computer within this administration. The second, "Securing the Nation Against Advanced Cryptographic Attacks," sets specific deadlines: federal agencies must complete migration to post-quantum cryptography for key establishment in high-value systems by December 31, 2030, and for digital signatures by December 31, 2031.

The same week, Finnish quantum computing company IQM Quantum Computers announced a significant advancement in quantum error correction, claiming their directional tile codes reduce logical error rates by up to 1,000 times compared to surface codes at comparable hardware footprint.

Neither event means quantum computers can break Bitcoin today. But together, they signal something important for developers: the engineering discussion is becoming more concrete, and the institutions that set global cryptographic standards are now operating on explicit timelines. Bitcoin's upgrade cycle, Taproot took four years from proposal to activation, cannot afford to wait for the threat to materialize before preparation begins.

What IQM's Breakthrough Actually Changes

[Main image: quantum computing circuits]

Quantum computers leverage qubits that exist in superposition states, allowing certain calculations to run exponentially faster than classical computers. The fundamental obstacle has been decoherence: environmental noise causes qubits to lose their quantum state, producing errors that corrupt calculations.

A 2022 estimate suggested breaking ECDSA over secp256k1 would require approximately 13 million noisy physical qubits running for 24 hours. IQM's error correction result does not mean a cryptographically relevant quantum computer is near. It does mean that error-correction assumptions can change, and those assumptions directly affect long-term resource estimates for attacking elliptic-curve cryptography.

For context, IBM's current systems contain around 1,000 physical qubits. The gap remains large. The question is no longer purely academic. For protocol developers, it is becoming an engineering planning problem.

For Bitcoin developers, the exposure map matters immediately. P2PKH and P2WPKH addresses expose public keys only at spending time, giving quantum attackers a narrow window between broadcast and confirmation. Reused addresses and unspent outputs from addresses that have already published their public key on-chain face longer-term structural exposure. P2TR outputs are different: the Taproot output key is already visible on-chain, placing them in the long-range exposure discussion even though their upgrade path differs from early P2PK outputs.

Presidio Bitcoin's living research repository estimates that if a cryptographically relevant quantum computer existed today, around 6.5 million BTC could be at risk due to long-exposed public keys, with roughly 1.72 million BTC in early P2PK outputs and much of the remainder linked to address reuse.

Trump's PQC Deadlines and What They Mean for Bitcoin Infrastructure

Trump's cryptography executive order does not mention Bitcoin directly. Its immediate scope covers federal agencies, intelligence systems, and government contractors. But the implications extend further.

The order directs the Office of Management and Budget and the National Cyber Director to lead a nationwide migration to post-quantum cryptography. Government contractors face future procurement requirements aligned with NIST's Federal Information Processing Standards. The broader policy push is backed by recent federal funding signals. In May 2026, the U.S. Department of Commerce announced letters of intent to provide about $2.013 billion in CHIPS and Science Act incentives to nine quantum companies, including quantum foundries and computing firms.

This matters for Bitcoin developers for three reasons.

First, NIST's post-quantum standards now have enforcement timelines behind them. CRYSTALS-Dilithium, standardized by NIST in 2024 as ML-DSA, and SPHINCS+, standardized as SLH-DSA, are no longer theoretical candidates. They are the benchmarks federal systems will migrate toward. Bitcoin's protocol discussions about post-quantum signature schemes will increasingly reference these standards.

Second, the "harvest now, decrypt later" threat is now being treated as real and present by the U.S. government. Data intercepted today can be stored and decrypted retroactively once quantum capability matures. For Bitcoin outputs with permanently exposed public keys, this framing is directly applicable.

Third, federal investment is accelerating commercial quantum development. Private sector timelines typically run parallel to or ahead of federal benchmarks. The engineering discussion is becoming more concrete than most 2022-era threat models assumed.

Post-Quantum Signatures: Trade-offs for Bitcoin's Constrained Environment

The cryptographic schemes under consideration come with significant trade-offs that matter for developers building on Bitcoin.

Signature sizes for post-quantum schemes are substantially larger than current ECDSA signatures. CRYSTALS-Dilithium (ML-DSA) signatures run approximately 2.4KB compared to 64 bytes for ECDSA. SPHINCS+ (SLH-DSA) signatures are larger still. For block space, transaction fees, and bandwidth, these differences are not trivial.

For Lightning Network implementations serving Malaysian merchants or migrant worker remittance applications, the impact compounds. Channel states require fast signature verification. Payment paths need compact proofs. If post-quantum signatures increase verification time or transaction size substantially, Lightning's sub-second payment experience degrades. Research into aggregatable post-quantum schemes is directly relevant to whether second-layer solutions remain viable in a post-quantum environment.

Hybrid approaches are under active discussion in Bitcoin development: using Taproot script trees to commit to both Schnorr and post-quantum signatures, enabling gradual transition while preserving backward compatibility. This introduces complexity, two signature types, coordination between legacy and quantum-safe outputs, fee estimation across mixed transaction types, but it preserves the option for a non-disruptive migration path.

The sovereignty principle that must hold through any transition: post-quantum cryptography cannot require trusted setup ceremonies or third-party key generation services. For developers building non-custodial tools in jurisdictions where institutional trust is a design constraint rather than a given, this is the architectural requirement that determines whether the tool remains sovereign.

What Malaysian and SEA Developers Should Do Now

Trump's executive order sets 2030 as the federal deadline for post-quantum migration of key establishment systems. Bitcoin's governance model is slower and more decentralized than any government agency. The implication is straightforward: Bitcoin's post-quantum preparation needs to begin well before the threat materializes, because protocol upgrades require years of research, testing, and consensus.

For developers building in Southeast Asia, three practical priorities follow.

Address hygiene is the most immediate action available. Advise users never to reuse addresses. Build wallet applications on BIP-32 hierarchical deterministic patterns that generate fresh addresses automatically. For non-custodial wallets serving migrant workers or unbanked populations, this is quantum hygiene embedded into the user experience without requiring user understanding of the underlying cryptography.

Track the Presidio Bitcoin research repository and Bitcoin Core's post-quantum signature discussions. The migration scenarios, voluntary transition versus emergency protocol action, carry different implications for applications that use timelocks, multisig configurations, or inheritance schemes. Scripts that depend on specific address types may need redesign depending on which migration path the network chooses.

Consider the migration risk for long-duration scripts. If your application holds user funds in configurations designed to persist for years, quantum migration could invalidate those scripts. Understanding the range of implementation paths, new address types, new signature opcodes, full cryptographic replacement, is now a design requirement, not a future consideration.

Key Takeaway: Post-quantum Bitcoin work is preparation, not panic, and developers should start with address hygiene.

💬 Discussion question: With the U.S. government setting 2030 as the federal post-quantum cryptography deadline for key establishment, and Bitcoin's upgrade cycle historically taking four or more years, what should Bitcoin Core developers prioritize first: signature scheme research, migration mechanism design, or user-facing address hygiene tooling?

#Bitcoin #Malaysia #BitcoinDev #QuantumComputing