Trump signs quantum security executive order, which may promote post-quantum security research for Bitcoin

On Monday, U.S. President Trump signed two executive orders aimed at accelerating the development of U.S. quantum computing capabilities and advancing the government's transition to post-quantum cryptography. Although the executive orders did not directly mention Bitcoin, industry insiders believe this could benefit the blockchain's post-quantum security research and development.

The two executive orders focus on defending against advanced cryptographic attacks and promoting cutting-edge quantum innovation. They include a clear timeline: to advance the construction of quantum sensors by September 2028 and require federal high-value assets and high-impact systems to complete the transition to post-quantum cryptography by the end of 2031. Project Eleven CEO Alex Pruden stated that this means the U.S. government will invest time and resources to achieve post-quantum security goals and may extend related requirements to the entire federal contractor system, not just limited to government agencies, thereby accelerating the implementation of post-quantum cryptographic technology.

At the time of this policy announcement, the blockchain industry’s concern about quantum threats continues to rise. Organizations like the Ethereum Foundation and the Solana Foundation have begun advancing post-quantum security research and development, while the Bitcoin community is also discussing potential risks. Some publicly exposed Bitcoin addresses are believed to face the risk of private keys being derived once powerful quantum computers emerge in the future. Pruden pointed out that this executive order clearly sets the deadline for adopting post-quantum cryptography as 2031, which is more binding than the previous guidance from the U.S. government that proposed phasing out traditional cryptographic systems by 2035. For Bitcoin and the broader cryptocurrency industry, government investment in post-quantum security may accelerate the maturity of related tools, standards, and migration paths.