Is Acurast Quantum Safe?

Is Acurast quantum safe? That question matters more than most ACU holders realise. Acurast runs a decentralised confidential compute network built on a Substrate-based chain, which means its cryptographic foundations sit squarely in the same ECDSA and EdDSA territory that quantum computers are expected to break within one to two decades. This article examines exactly what cryptography Acurast uses, where the genuine exposure lies, what migration paths exist in the Substrate ecosystem, and how purpose-built lattice-based alternatives approach the same threat from a different starting point.

What Cryptography Does Acurast Actually Use?

Acurast is built on the Substrate framework, developed by Parity Technologies and shared with Polkadot, Kusama, and dozens of other parachains. That lineage has direct implications for its cryptographic posture.

Signing Schemes in the Substrate Stack

Substrate exposes three account types by default:

• sr25519 — Schnorr signatures over Ristretto255, used by most Polkadot-ecosystem accounts
• ed25519 — Edwards-curve Digital Signature Algorithm (EdDSA) over Curve25519
• ecdsa — the secp256k1 scheme familiar from Bitcoin and Ethereum

Acurast wallets and validator keys primarily rely on sr25519 and ed25519. Both are elliptic-curve constructions. Their security rests on the hardness of the Elliptic Curve Discrete Logarithm Problem (ECDLP). A sufficiently powerful quantum computer running Shor's algorithm can solve ECDLP in polynomial time, collapsing the security of all three schemes to effectively zero.

TEE Attestation and ECDSA

Acurast's defining feature is its use of Trusted Execution Environments (TEEs), specifically Apple Secure Enclave on processor-grade mobile hardware, to attest job execution. Those attestation certificates use P-256 (secp256r1) ECDSA signatures. P-256 is also an elliptic-curve scheme. The same quantum attack vector applies.

This creates a layered exposure: not only are user-facing wallet keys at risk, but the attestation infrastructure that makes Acurast's verifiable compute model trustworthy is also built on pre-quantum primitives.

---

Understanding Q-Day: When Does the Threat Become Real?

"Q-day" refers to the point at which a cryptographically relevant quantum computer (CRQC) can break 256-bit elliptic-curve keys in a practical timeframe. Estimates vary significantly, but the risk landscape breaks into three distinct phases.

For a blockchain project like Acurast, the most immediate concern is not someone draining wallets tomorrow. It is that long-lived public keys, keys that have been reused across many transactions and are permanently recorded on-chain, create a retroactive attack surface the moment a CRQC becomes accessible.

Why Reused Public Keys Amplify the Risk

Every time an address signs a transaction, its full public key is broadcast to the network. On Substrate-based chains this is standard. An attacker harvesting that public key today needs only to run Shor's algorithm against it when they have access to a sufficiently powerful machine. Addresses that have never broadcast a transaction (where only the hash is known) have marginally more protection, but once a key is exposed on-chain, it stays exposed permanently.

---

Does Acurast Have a Quantum Migration Roadmap?

As of the time of writing, Acurast has not published a formal post-quantum cryptography (PQC) migration roadmap. That is not unusual. The majority of Substrate-based projects are in the same position, watching the progress of the Polkadot core team and NIST standardisation process before committing engineering resources.

What Substrate-Level Migration Could Look Like

The Substrate framework is modular by design. A migration to quantum-resistant signing would, in theory, require:

1. New account type support — adding a PQC signing module (e.g. CRYSTALS-Dilithium or FALCON) to the runtime
2. Key migration period — a governance-enforced window during which holders move funds from legacy EC addresses to new PQC addresses
3. Validator key rotation — all collators and validators re-registering with PQC keys
4. TEE attestation update — coordination with hardware vendors to replace ECDSA-based attestation certificates with PQC equivalents

Step four is particularly complex for Acurast, because the TEE attestation layer is tied to physical hardware and Apple's certificate authority. That dependency is outside the project's direct control.

NIST PQC Standardisation Context

In August 2024, NIST finalised its first set of post-quantum cryptographic standards:

• ML-KEM (CRYSTALS-Kyber) — for key encapsulation
• ML-DSA (CRYSTALS-Dilithium) — for digital signatures
• SLH-DSA (SPHINCS+) — hash-based signature fallback

FALCON (now standardised as FN-DSA) was also included. These lattice-based and hash-based schemes are immune to Shor's algorithm because they rely on mathematical problems — Learning With Errors (LWE) and Short Integer Solution (SIS) — that have no known efficient quantum algorithm.

Until Substrate integrates one of these natively, Acurast and every parachain built on it remain in a pre-quantum-safe state.

---

Comparing Quantum Vulnerability Across ACU's Key Surfaces

It is useful to be precise about which parts of the Acurast system are most exposed, rather than treating quantum risk as a single monolithic threat.

SHA-256-based hashing is worth a note of relative comfort: Grover's algorithm gives a quantum speedup against hash functions, but only reduces effective security from 256 bits to 128 bits, which remains computationally infeasible to brute-force. The signing layer is where genuine urgency exists.

---

Lattice-Based Post-Quantum Wallets: A Different Architecture

Projects designing cryptographic infrastructure from scratch today, rather than migrating legacy EC schemes, have the option to build on NIST-standardised lattice-based algorithms from the ground up. This architectural difference is significant.

A lattice-based wallet uses problems like LWE or Module-LWE as its hardness assumption. These are believed to resist both classical and quantum attacks, and they are the mathematical foundation underlying CRYSTALS-Dilithium (ML-DSA) and CRYSTALS-Kyber (ML-KEM).

The practical tradeoffs versus EC-based schemes:

• Key and signature sizes — lattice signatures are larger (Dilithium Level 3 signatures are ~3.3 KB versus ~64 bytes for ed25519). This has throughput implications for high-frequency chains.
• Verification speed — competitive with EC at the verification step; key generation is slightly slower.
• Maturity — NIST standardisation in 2024 gives these schemes a credible security review history, but they lack the 20-year deployment history of secp256k1.
• Harvest-resistance — keys generated under lattice schemes today are safe against future quantum harvest attacks, which is the most immediate, non-speculative risk.

BMIC.ai is one example of a project building a quantum-resistant wallet from this architectural starting point, using lattice-based post-quantum cryptography aligned with NIST PQC standards rather than attempting to bolt on migration to an existing EC stack. For users holding Acurast or other Substrate-based assets, the practical implication is that the wallet used to custody those assets is itself a distinct cryptographic risk surface, separate from the chain's own migration progress.

---

What ACU Holders Should Monitor

Given that Acurast has no published PQC migration plan and the underlying Substrate framework has not yet shipped a standardised PQC account type, there are concrete signals worth tracking:

Near-Term Indicators (1–3 Years)

• Polkadot fellowship proposals — runtime changes to Polkadot Relay Chain propagate to parachains over time. Watch the Polkadot governance forum for PQC account type RFCs.
• NIST implementation libraries — maturation of liboqs and similar open-source PQC libraries makes Substrate integration increasingly straightforward.
• Acurast GitHub activity — any cryptographic primitive changes in the runtime pallet will surface in repository commits before formal announcements.

Medium-Term Indicators (3–7 Years)

• Formal migration governance vote — if Acurast moves forward, expect a governance proposal with a defined key-migration window.
• TEE hardware PQC attestation — monitor Apple, AMD, and Intel secure enclave roadmaps for P-256 replacement timelines.
• Regulatory pressure — financial regulators in the US and EU are beginning to mandate PQC timelines for critical infrastructure. If DeFi falls under similar requirements, migration velocity will accelerate sharply.

---

Practical Steps for Acurast Holders Right Now

Waiting for chain-level migration is passive. There are steps individual holders can take to reduce their personal exposure under the current architecture:

1. Minimise public key exposure — avoid reusing addresses across multiple transactions where possible. Fresh addresses on Substrate chains have not yet broadcast their public key (only the hash is on-chain), offering marginal additional time before a CRQC attack becomes feasible.
2. Audit your custody stack — identify which wallet software you are using and whether it has any stated PQC roadmap.
3. Track key-migration windows — when Acurast or Polkadot announces a migration period, moving assets to new PQC-derived addresses early reduces exposure relative to waiting until the deadline.
4. Hold only in quantum-resistant custody — for assets where long-term storage is the goal, consider whether the signing infrastructure protecting those assets will still be secure in 10 to 15 years under the CRQC scenarios most credible researchers now consider plausible.
5. Diversify cryptographic risk — holding assets across both chain types (legacy EC and native PQC) distributes the migration risk rather than concentrating it.

None of these steps eliminates quantum risk at the Acurast protocol layer. That requires action from the development team and the Polkadot ecosystem. But they meaningfully reduce individual exposure in the interim.

---

Conclusion

Acurast is not quantum safe. Its cryptographic stack, inherited from Substrate and compounded by ECDSA-based TEE attestation, is vulnerable to Shor's algorithm at the same level as every other elliptic-curve blockchain in production today. There is no published migration roadmap, and the TEE attestation dependency introduces complexity that goes beyond a standard runtime upgrade. The Q-day timeline remains uncertain, but the harvest-now-decrypt-later attack is already a rational concern for high-value, long-lived key material. ACU holders monitoring this risk should watch Polkadot governance closely and evaluate the quantum-resistance of every layer in their custody stack, not only the chain itself.