# Does Anchorage Digital's PQC Strategy Actually Solve the Bitcoin Migration Problem?

An estimated two-thirds of circulating Bitcoin is held under legacy signing credentials that Shor's algorithm — running on a sufficiently large fault-tolerant quantum computer — could compromise. Anchorage Digital, the only federally chartered crypto bank in the United States, has now published a concrete operational strategy to address that exposure, including original cryptographic research and open-source tooling that moves beyond compliance posturing into executable infrastructure.

The firm's strategy has two distinct layers: internal hardening of its own custody infrastructure using a multi-layered cryptographic architecture, and an externally facing contribution to the broader public blockchain ecosystem. That second component is the more technically ambitious — and the more scrutiny-worthy — of the two.

The core threat Anchorage is designing against is the "harvest now, decrypt later" adversary model: state-level or well-resourced actors who intercept and archive today's encrypted transactions, betting that sufficiently capable quantum hardware will eventually make decryption tractable. For institutional digital asset custodians, this is not a theoretical horizon — it is an active operational risk that regulators and counterparties are beginning to price into due diligence conversations.

---

## The Post-Quantum Turnstile: ZK Migration for Legacy Bitcoin Holders

The most technically novel element of Anchorage's release is what the firm calls the **Post-Quantum Turnstile**: a zero-knowledge framework built on STARKs (Scalable Transparent Arguments of Knowledge) that allows holders of legacy credentials to migrate signing authority to post-quantum keys without exposing either their private or public key material during the process.

This matters because the naive migration path — simply signing a transaction that transfers funds to a new PQC-protected address — requires broadcasting a public key on-chain, which is precisely the information Shor's algorithm needs to reconstruct the private key. The Turnstile framework is designed to close that window.

The scope of the target population is significant. According to Anchorage's own estimate, the Turnstile is designed to address credential holders covering approximately two-thirds of circulating Bitcoin. That figure, sourced directly from the firm's published strategy, reflects the proportion of Bitcoin that remains in address formats where the public key has never been exposed on-chain — meaning current-day security is intact, but any future spend transaction would expose it.

**Analysis:** STARK-based ZK proofs are computationally intensive, and on-chain verification costs on Bitcoin's base layer are non-trivial. Anchorage has not, in the material summarized by the Quantum Computing Report, detailed the transaction size overhead, verification cost, or whether the Turnstile is designed for Bitcoin's base layer, a Layer 2, or requires a soft/hard fork to implement. These are the questions enterprise buyers and protocol developers should be pressing on before treating this as a deployable solution rather than a research prototype.

---

## sqisign-rs: A Compact Signature Scheme for On-Chain Use

Anchorage also open-sourced **sqisign-rs**, a Rust implementation of the SQIsign signature scheme, which is grounded in supersingular elliptic curve isogenies. The firm's published material states that sqisign-rs produces a signature footprint approximately seven times smaller than Falcon — a NIST-standardized lattice-based signature scheme — for on-chain execution.

Compact signatures are not a vanity metric in blockchain contexts. On-chain real estate directly affects transaction fees, block capacity, and the practical economics of PQC migration at scale. If the seven-times compression figure holds under production conditions, sqisign-rs would represent a meaningful efficiency gain over deploying Falcon directly on Bitcoin or Ethereum.

**Skeptical note:** SQIsign is not among the NIST Post-Quantum Cryptography standards finalized in recent rounds. Isogeny-based cryptography has had a turbulent few years — the SIDH/SIKE family was broken in 2022, though SQIsign operates on a different mathematical foundation (SQIsign uses the Deuring correspondence, not SIDH's commutative structure). The cryptographic community has not reached the same consensus on isogeny-based schemes as it has on lattice-based (CRYSTALS-Kyber, CRYSTALS-Dilithium, Falcon) or hash-based approaches. Institutional adopters should treat sqisign-rs as a research contribution worth monitoring, not a production standard.

---

## What This Means for Institutional Custody and the Broader PQC Migration Timeline

Anchorage's move is notable less for the specific primitives it deploys and more for what it signals about where the institutional digital asset sector is in its PQC readiness cycle. A federally chartered bank publishing original cryptographic research and open-source tooling is a different posture than the compliance-checkbox approach that has characterized most financial sector PQC announcements to date.

For enterprise buyers evaluating digital asset custody providers, Anchorage has effectively raised the bar for what a credible PQC preparedness narrative looks like. Custodians who cannot articulate a harvest-now-decrypt-later defense and a concrete key migration path for legacy credential holders will face increasing scrutiny from institutional clients and, eventually, from regulators.

The Bitcoin-specific migration problem Anchorage is targeting also has systemic implications beyond custody. Protocol developers, exchange operators, and wallet providers all face the same two-thirds-of-circulating-supply exposure. A workable ZK-based migration standard — if the Turnstile framework proves technically sound and achieves protocol-level adoption — would be a genuine contribution to Bitcoin's long-term cryptographic resilience. Whether that adoption path exists without a coordinated protocol upgrade is a separate and harder question.

For the post-quantum cryptography sector broadly, the Anchorage announcement reflects the accelerating pace at which financial institutions are moving from awareness to implementation. The practical deadline is not the arrival of a cryptographically relevant quantum computer — it is the point at which regulators or counterparties begin requiring documented PQC posture as a condition of custody mandates.

---

## Key Takeaways

- **Anchorage Digital** is the only federally chartered crypto bank in the U.S. and has published a multi-layered PQC preparedness strategy targeting the "harvest now, decrypt later" threat model.
- The **Post-Quantum Turnstile** uses STARK-based zero-knowledge proofs to allow legacy credential holders — covering an estimated **two-thirds of circulating Bitcoin** per Anchorage's figures — to migrate to PQC signing keys without exposing public or private key material.
- **sqisign-rs**, Anchorage's open-sourced Rust implementation of SQIsign, claims a signature footprint approximately **seven times smaller than Falcon** for on-chain use — potentially significant for transaction economics, but SQIsign is not yet a NIST-standardized scheme.
- The internal custody infrastructure deploys a **three-layer cryptographic architecture**, though the specific primitives were not detailed in the summarized source material.
- Institutional custody providers without a documented PQC migration path are increasingly exposed to client and regulatory scrutiny.
- Critical open questions remain: on-chain verification costs for the Turnstile, protocol-level adoption requirements, and the production readiness of isogeny-based signatures.

---

## Frequently Asked Questions

**What is the "harvest now, decrypt later" attack and why does it matter for Bitcoin?**
Adversaries can record encrypted blockchain transactions today and store them until a sufficiently powerful quantum computer running Shor's algorithm can retroactively decrypt the public-key cryptography protecting those transactions. For Bitcoin, the risk is that any unspent output whose public key is exposed on-chain becomes vulnerable once fault-tolerant quantum hardware reaches sufficient scale.

**What is the Post-Quantum Turnstile that Anchorage Digital developed?**
It is a zero-knowledge framework built on STARKs that allows Bitcoin holders using legacy signing credentials to migrate their signing authority to post-quantum keys without broadcasting their current public key on-chain — the step that would otherwise expose them to quantum attack during migration.

**Why is sqisign-rs significant compared to NIST PQC standards like Falcon?**
Anchorage claims sqisign-rs produces signatures approximately seven times smaller than Falcon for on-chain use, which would reduce transaction costs and block space consumption during PQC migration. However, SQIsign has not been standardized by NIST and carries more cryptographic uncertainty than lattice-based schemes that have completed formal evaluation.

**How much of circulating Bitcoin is at risk from quantum attacks on public keys?**
Anchorage estimates that approximately two-thirds of circulating Bitcoin is held under legacy credentials targeted by their Turnstile framework — specifically, addresses where a public key migration would require on-chain exposure during any future spend.

**What should enterprise digital asset custodians do now about post-quantum threats?**
At minimum: document your exposure to harvest-now-decrypt-later scenarios, audit which client assets are held under key types that require on-chain public key exposure for future spends, and evaluate whether your signing infrastructure is compatible with NIST-standardized PQC algorithms. Regulatory pressure for documented PQC posture is materializing faster than cryptographically relevant quantum hardware — the compliance timeline is the nearer-term risk.