Quantum threat to crypto: the SEC task force submission warns quantum computers may break current blockchain cryptography by 2028, risking stored encrypted data and trillions in assets; immediate migration to quantum-resistant systems and prioritized protection for custodial wallets and exchanges is recommended.
PQFIF warns quantum computing could break Bitcoin, Ethereum, and other networks’ cryptography, risking trillions in assets.
The proposal highlights the “Harvest Now, Decrypt Later” threat and urgent migration to post-quantum cryptography.
Analyst Merlijn The Trader cites Algorand and Hedera as early adopters of quantum-ready security and institutional partnerships.
Quantum threat to crypto: SEC warns of cryptographic risk by 2028; read mitigation steps and migrate to quantum-resistant systems now. (COINOTAG)
SEC task force warns quantum computing could threaten crypto security by 2028, urging urgent migration to quantum-resistant systems.
- PQFIF warns quantum computing could break Bitcoin, Ethereum, and other networks’ cryptography, risking trillions in assets.
- The proposal notes the “Harvest Now, Decrypt Later” threat, with adversaries storing encrypted data for future quantum attacks.
- Analyst Merlijn The Trader points to Algorand and Hedera as early adopters of quantum ready security and institutional partnerships.
A proposal submitted to the SEC Crypto Assets Task Force has warned that the rise of quantum computing could compromise the security of the global digital asset ecosystem. The document, titled the Post-Quantum Financial Infrastructure Framework (PQFIF), stressed that advancements in cryptographically relevant quantum computers (CRQC) could break existing encryption standards protecting trillions of dollars in assets.
‘,
‘
🚀 Advanced Trading Tools Await You!
Maximize your potential. Join now and start trading!
‘,
‘
📈 Professional Trading Platform
Leverage advanced tools and a wide range of coins to boost your investments. Sign up now!
‘
];
var adplace = document.getElementById(“ads-bitget”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexBitget”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesBitget.length) : sessperindex;
adplace.innerHTML = adscodesBitget[adsindex];
sessperindex = adsindex === adscodesBitget.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexBitget”, sessperindex);
}
})();
The framework indicated the urgent need for migration to quantum-resistant systems to prevent catastrophic investor losses and a collapse of market confidence.
The quantum threat to crypto is the risk that cryptographically relevant quantum computers will be able to break the public-key and signature schemes that secure blockchains like Bitcoin and Ethereum. If achieved, this would enable decryption of stored data and forging of transactions, endangering custodial wallets, exchanges, and long-term records.
The PQFIF submission, authored by Daniel Bruno Corvelo Costa, warns that “Q‑Day” could arrive as early as 2028. It recommends automated vulnerability assessments, prioritized protection for high-risk systems, and a phased migration combining classical and post‑quantum cryptography. The framework references recent NIST standards (2024) and suggests HQC as a fallback.
“Harvest Now, Decrypt Later” describes adversaries collecting encrypted data today with the intention to decrypt once quantum capabilities mature. This is dangerous because it creates a time-lagged exposure: data considered secure now may become readable later, amplifying long-term confidentiality and integrity risks for financial records and custody systems.
‘
];
var adplace = document.getElementById(“ads-binance”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexBinance”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesBinance.length) : sessperindex;
adplace.innerHTML = adscodesBinance[adsindex];
sessperindex = adsindex === adscodesBinance.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexBinance”, sessperindex);
}
})();