Post quantum... When ready? a lot of money injected on matrix and using deprecated Encription..

[R00tedbrain]

Your use case

Dear Element and Matrix Developers,

I am writing to you as a concerned user and observer of the rapid advancements in technology, particularly in the realms of security and privacy. With the rapid evolution of cryptographic challenges brought about by quantum computing, I would like to respectfully raise an important concern and request for the future of the Element platform and Matrix protocol: the implementation of post-quantum cryptographic algorithms.

Background and Justification
Advancements in Quantum Computing:
Leading technology players, such as Google, IBM, and other industry pioneers, have made significant breakthroughs in quantum computing. The recent developments of increasingly powerful quantum chips are no longer theoretical—they are tangible achievements. These systems will soon have the potential to break classical cryptographic algorithms such as RSA, ECC, and even some current encryption methods.

Residual Data in Matrix:
The federated and decentralized nature of the Matrix protocol allows messages to be stored residually over long periods across different servers. While Element currently uses encryption methods such as OLM and Megolm for end-to-end security, these are not resistant to post-quantum attacks. Consequently, any adversary storing encrypted messages today may decrypt them in the near future as quantum computing advances.

The Need for Post-Quantum Cryptography:
The implementation of post-quantum cryptography is no longer optional—it is an urgent necessity. Organizations like NIST (National Institute of Standards and Technology) have already advanced the standardization of post-quantum algorithms such as Kyber, Dilithium, and Falcon, which are designed to withstand quantum attacks.

Other emerging platforms are proactively adopting hybrid encryption methods (combining classical and post-quantum cryptography) to ensure future-proof security while maintaining backward compatibility with existing systems.

Investment and Expectations:
With over $16 million in investment injected into the Matrix project, there is significant user trust and reliance on the platform’s promise of security and privacy. However, it is concerning that a platform of this magnitude has yet to prioritize post-quantum encryption, which is becoming a critical standard.

The absence of post-quantum cryptography risks undermining user trust and raises questions about the platform's long-term viability as a technological leader in secure communications.

Our Request
We respectfully urge the Element and Matrix development teams to:

Prioritize the implementation of post-quantum cryptographic algorithms for OLM, Megolm, or as part of a critical update to the protocol.
Explore the adoption of hybrid encryption mechanisms (classical + post-quantum) to ensure seamless compatibility while preparing for quantum-safe communications.
Provide the community with a clear roadmap regarding plans to modernize the cryptographic foundations of the platform.
Conclusion
The security and privacy of communications remain the cornerstone of Element and the Matrix protocol’s mission. However, technological advancements are progressing at an unprecedented pace, and the encryption solutions of today may quickly become obsolete. Implementing post-quantum cryptography would ensure that the platform is future-proof and continues to be a trusted leader in secure, decentralized communication.

I deeply appreciate the hard work and dedication that your team has demonstrated in building and maintaining this platform. I trust that you will consider this request seriously and lead the way in adopting technologies that safeguard user privacy in the post-quantum era.

Thank you for your time, and I look forward to learning about your plans regarding this proposal.

Sincerely,
R00tedbrain

Have you considered any alternatives?

No response

Additional context

No response

Are you willing to provide a PR?

No

[spaetz]

Probably rather belongs into the existing cross-client issue at matrix-org/matrix-spec#975