Sky Post-Quantum Migration: Plans, Risks, and What Holders Should Do Now
Sky post-quantum migration is a question gaining traction as quantum computing timelines compress and DeFi protocols face mounting pressure to audit their cryptographic foundations. Sky, the rebranded successor to MakerDAO, operates one of the largest decentralised stablecoin ecosystems in crypto. Yet like virtually every major blockchain protocol, its security rests on elliptic-curve cryptography that a sufficiently powerful quantum computer could eventually break. This article examines whether Sky has a public post-quantum roadmap, what a real migration would involve technically, and what current SKY and USDS holders can do in the meantime.
Does Sky Have a Post-Quantum Migration Plan?
The direct answer: as of mid-2025, Sky (formerly MakerDAO) has no publicly documented post-quantum migration roadmap. There are no Sky Improvement Proposals (formerly MIPs), no governance forum discussions, and no official engineering blog posts committing to a post-quantum cryptography (PQC) transition timeline.
This is not unusual. Among the top-20 DeFi protocols by total value locked, post-quantum planning remains almost universally absent from public roadmaps. Ethereum's own core developers have acknowledged quantum risk in research contexts, but even the base layer has not committed to a firm PQC upgrade schedule. Sky inherits both Ethereum's architecture and, consequently, its quantum exposure.
That said, "no public plan" is not the same as "no awareness." Sky's engineering contributors have access to the broader Ethereum research ecosystem, where post-quantum topics are discussed at the protocol level. Any migration at the Sky layer would almost certainly be gated behind an Ethereum-level PQC transition first, making the base-layer timeline the binding constraint.
---
Why Post-Quantum Risk Matters for a Stablecoin Protocol
Sky is not just a token. It is the governance layer over a system that mints USDS (the rebranded DAI), manages billions in collateral, and coordinates a network of smart contracts, oracle feeds, and liquidation mechanisms. Post-quantum risk therefore operates on multiple levels simultaneously.
ECDSA Wallet Exposure
Every wallet that holds SKY or USDS uses a public key derived from the Elliptic Curve Digital Signature Algorithm (ECDSA). A cryptographically relevant quantum computer (CRQC) running Shor's algorithm could derive the private key from a known public key. Once a public key is broadcast to the network (which happens as soon as an address has ever sent a transaction), the funds at that address are theoretically extractable.
The quantum attack window is the time between a transaction being broadcast and being confirmed. On Ethereum, that window is seconds. But if a CRQC arrives, the more pressing danger is harvest-now, decrypt-later: adversaries are already collecting signed transactions and public keys, intending to crack them retrospectively once quantum hardware matures.
Oracle and Governance Key Risk
Sky's price oracle system relies on a set of whitelisted oracle providers signing price data with, again, ECDSA keys. A compromised oracle key could allow a bad actor to manipulate collateral prices and trigger illegitimate liquidations at scale. The governance multisig keys that can upgrade smart contracts carry similar exposure. These are high-value targets that a quantum-capable attacker would prioritise over retail wallets.
Smart Contract Immutability vs. Upgradeability
Unlike a wallet, a smart contract's logic is not directly exposed to quantum key-breaking. However, smart contracts are *controlled* by admin keys or governance votes that are themselves ECDSA-secured. If governance keys are cracked, an attacker could push malicious upgrades through the protocol's own upgrade mechanisms.
---
What a Sky Post-Quantum Migration Would Actually Involve
A genuine PQC migration for the Sky protocol is a multi-layer engineering challenge. Breaking it down by component illustrates why it is non-trivial and why no protocol has completed one yet.
Layer 1: Ethereum Base-Layer Migration
Sky runs on Ethereum. Before any application-layer PQC work is meaningful, Ethereum itself needs quantum-resistant signature schemes. The Ethereum research community has discussed replacing ECDSA with lattice-based schemes (e.g., CRYSTALS-Dilithium, which NIST standardised in 2024 as ML-DSA) or hash-based schemes (e.g., SPHINCS+, now FIPS 205). Either path requires an Ethereum hard fork, wallet software updates, and an account migration mechanism for existing addresses.
The leading proposal in Ethereum research involves moving to an account abstraction model (EIP-7702 and related work) that would allow accounts to swap out their signature verification logic, making PQC key schemes pluggable without replacing the entire protocol at once.
Sky's dependency: Until Ethereum supports PQC natively at the account layer, Sky cannot independently offer quantum-resistant transactions to end users regardless of what it does at the application layer.
Layer 2: Oracle Key Migration
Oracle providers would need to rotate from ECDSA to PQC signing keys. This is operationally complex because:
- Every oracle node must upgrade its key management infrastructure simultaneously or via a coordinated cutover.
- Sky governance must ratify a new set of whitelisted oracle addresses.
- Any gap in oracle coverage during migration creates a window of price feed vulnerability.
A phased approach, running ECDSA and PQC oracle signatures in parallel during a transition window, is the most plausible migration path used in enterprise cryptographic transitions and would likely be adapted here.
Layer 3: Governance and Multisig Migration
Sky's governance uses token-weighted voting (SKY token holders) plus an executive "hat" mechanism where a winning governance proposal is elevated for execution. The addresses controlling the protocol's core contracts would need to migrate to PQC-secured addresses. Under current Ethereum mechanics, this requires creating new addresses and transferring control via existing (still-ECDSA) governance votes before quantum risk materialises.
Layer 4: User Wallet Migration
The final and largest surface is retail and institutional wallet holders. Migrating user wallets requires:
- Ethereum (or a rollup) supporting PQC key schemes at the account layer.
- Wallet software (MetaMask, hardware wallets, etc.) implementing PQC key generation and signing.
- Users actively initiating a migration transaction to link their old address to a new PQC-secured address.
The last point is the hardest. A significant fraction of crypto holdings sit in wallets whose owners are inactive, lost, or deceased. Those holdings would remain quantum-exposed indefinitely.
---
Interim Options for SKY and USDS Holders
While waiting for protocol-level solutions that do not yet exist, there are practical risk-reduction strategies available today.
Minimise Public Key Exposure
The quantum attack surface is maximised when a public key is known. An address that has never sent a transaction has an unexposed public key (the attacker only knows the hash of the public key). Holding assets in fresh, never-transacted addresses buys additional time. However, this is not a long-term solution and becomes impractical for active DeFi users who must interact with Sky's contracts.
Use Hardware Wallets With Air-Gapped Signing
While hardware wallets still use ECDSA, they reduce the operational risk of key compromise through conventional means (malware, phishing). They also make it easier to perform a rapid wallet migration once PQC-compatible signing is available, since the seed phrase is already stored securely offline.
Monitor Ethereum PQC Research and EIP Tracker
Sky holders with significant exposure should track:
- The ethereum/EIPs GitHub for account-abstraction and PQC-related proposals.
- NIST's post-quantum cryptography standardisation documentation for ML-KEM, ML-DSA, and SLH-DSA (the three finalised standards as of 2024).
- Sky's own governance forum (forum.sky.money) for any PQC-related discussions from core contributors.
Diversify Across Quantum-Readiness Levels
Some newer blockchain projects are building quantum resistance directly into their architecture from inception rather than attempting a migration of legacy infrastructure. Projects implementing NIST-standardised lattice-based cryptography, such as BMIC.ai, which is designed around post-quantum cryptography from the ground up, represent an alternative approach to the migration-versus-rebuild tradeoff that incumbent protocols like Sky must grapple with.
---
Post-Quantum Migration: Sky vs. Other Major DeFi Protocols
The table below reflects the publicly available state of post-quantum planning across selected major DeFi protocols as of mid-2025.
| Protocol | Underlying Chain | Public PQC Roadmap | Oracle PQC Plan | Governance Key Migration Plan |
|---|---|---|---|---|
| Sky (MakerDAO) | Ethereum | None public | None public | None public |
| Aave | Ethereum | None public | None public | None public |
| Uniswap | Ethereum | None public | N/A (AMM model) | None public |
| Compound | Ethereum | None public | None public | None public |
| Solana (ecosystem DeFi) | Solana | None public | None public | None public |
| Ethereum L1 | — | Research stage only | N/A | No timeline |
The uniformity across the table is the key insight: Sky is not uniquely behind. It is representative of an industry-wide gap between post-quantum awareness and actionable post-quantum planning.
---
What Would Trigger a Sky Post-Quantum Migration?
Even without a current roadmap, certain events would likely force accelerated action from Sky's governance community.
- A credible CRQC announcement: If a national government or major technology firm announced a quantum computer capable of running Shor's algorithm against 256-bit elliptic curves, governance discussions would almost certainly begin within days.
- An Ethereum PQC hard fork proposal gaining traction: If Ethereum's core developers schedule a PQC upgrade fork, Sky and every other Ethereum-based protocol would need to respond.
- A high-profile ECDSA key compromise: A demonstrated exploit of a significant DeFi protocol's governance or oracle keys via any method would sharply raise the perceived urgency of migration planning.
The absence of a plan today does not mean the plan would be slow to materialise under pressure. Crypto governance can move fast when existential threats are clearly defined. The challenge is that quantum timelines remain uncertain enough that governance communities consistently deprioritise migration work in favour of near-term product features and risk management.
---
Key Takeaways for Sky Stakeholders
- Sky has no public post-quantum migration roadmap as of mid-2025.
- The binding constraint is Ethereum's own PQC readiness, not Sky-specific engineering.
- A full migration would touch wallet keys, oracle infrastructure, governance keys, and smart contract control simultaneously.
- NIST finalised its PQC standards in 2024, giving the industry a concrete cryptographic target for the first time.
- Interim risk-reduction options exist (fresh addresses, hardware wallets, monitoring EIP tracker) but are not long-term solutions.
- The industry-wide pattern is awareness without commitment. Sky is typical, not exceptional.
Holders with material exposure to Sky assets should treat post-quantum migration as a medium-term planning horizon item, not an immediate crisis, but also not an issue to defer indefinitely.
Frequently Asked Questions
Does Sky (MakerDAO) have a post-quantum migration plan?
No. As of mid-2025, Sky has no publicly documented post-quantum migration roadmap. There are no governance proposals, engineering announcements, or forum discussions committing to a PQC transition timeline. This mirrors the broader DeFi industry, where post-quantum planning is largely absent across major protocols.
What is 'Q-day' and why does it matter for SKY and USDS holders?
Q-day refers to the future point when a cryptographically relevant quantum computer (CRQC) could run Shor's algorithm to derive private keys from publicly exposed ECDSA public keys. Since every SKY and USDS-holding wallet uses ECDSA, all of those wallets are theoretically at risk once that threshold is reached. Estimates on timing vary widely, from under a decade to several decades, depending on the source.
What cryptographic standards would a Sky post-quantum migration use?
Any credible migration would target NIST's 2024-finalised post-quantum standards: ML-DSA (CRYSTALS-Dilithium) for digital signatures, ML-KEM (CRYSTALS-Kyber) for key encapsulation, and SLH-DSA (SPHINCS+) as a hash-based signature alternative. These replace ECDSA and RSA with algorithms believed to be resistant to both classical and quantum attacks.
Can Sky migrate to post-quantum cryptography independently of Ethereum?
Not fully. Sky's smart contracts run on Ethereum, and user wallet security is determined at the Ethereum account layer. Sky can migrate its own oracle keys and governance infrastructure to PQC schemes, but user wallet quantum resistance requires Ethereum itself to support PQC signature schemes, which currently requires a protocol-level hard fork.
What can I do right now to reduce my quantum exposure as a Sky holder?
Three practical steps: first, hold assets in addresses that have never sent a transaction (unexposed public keys); second, use a hardware wallet for offline key storage to simplify migration when PQC-compatible wallets arrive; third, monitor the Ethereum EIP tracker and Sky's governance forum for PQC-related proposals so you can act quickly when migration paths become available.
Is the harvest-now, decrypt-later threat real for DeFi users?
Yes, it is a documented concern in national cybersecurity advisories. Adversaries can collect signed transaction data and encrypted communications today, storing them for decryption once quantum hardware matures. For DeFi, this means public keys broadcast in historical transactions are already potentially in adversarial databases. This is one reason analysts argue that waiting until Q-day arrives to begin migration planning is too late.