Our website now support TLS 1.3 with hybrid X25519 + MLKEM768 key exchange.
For supported browser sessions, that means combining X25519 (widely used on the web today), with ML-KEM-768 (a post-quantum method designed for future threats). It helps protect session data from harvest-now, decrypt-later risk.
Certificate authentication remain ECDSA while post-quantum certificate standards mature. Hybrid key exchange can keep eligible sessions confidential, but itโs not the finish line for postโquantum migration.
The broader requirement is crypto-agility: being able to swap cryptography without rebuilding the entire system.
๐๐๐ฏ๐ฒ๐ฟ ๐ฟ๐ถ๐๐ธ ๐ถ๐ ๐ฏ๐๐๐ถ๐ป๐ฒ๐๐ ๐ฐ๐ผ๐ป๐๐ถ๐ป๐๐ถ๐๐ ๐ฟ๐ถ๐๐ธ.
Equipment can remain useful long after its security updates stop. Infrastructure reviews need to cover remote access, ongoing support and recovery.
The same lifecycle thinking applies to #PQC: long-lived systems need a path to upgrade their cryptography against future quantum threats.
PQC would not fix compromised device controls. Both risks belong in infrastructure planning.
ft.com/content/2526056c-c616โฆ
Our founder, @wuiyangee, is heading to @HongKongFinTech x @StartmeupHK to share MerdekaL1, the Malaysian-built L1 we're developing with post-quantum security and crypto-agility, and lessons from his startup journey.
Connect with us in Hong Kong! ๐ญ๐ฐ
1/4 Malaysia's financial plumbing for tokenised bonds and sukuk is taking shape with the introduction of SSDS+ by @BNM_official.
Built in-house on cloud and DLT for tokenised asset issuance, depository and safekeeping, and integrated with RENTAS+ for 24/7 settlement.
4/4 The infrastructure is advancing. The question now is whether institutions are ready to connect.
Explore how MerdekaL1 is built for this next phase of tokenised capital markets โฌ๏ธ
e23.io/blog/merdekal1-litepaโฆ
5/5 Share this with your IT team, and follow e23 for practical infrastructure security insights.
Official guidance: php.net/archive/2026.php
We've published the MerdekaL1 Litepaper.
A sovereign Layer-1 for Malaysia, built in Rust, with post-quantum cryptography securing its consensus and networking.
It is a pre-pilot developer network.
Read it here: e23.io/blog/merdekal1-litepaโฆ
We won as Token-X Champion! ๐
Proud to build MerdekaL1 for institutional tokenisation, with post-quantum security for verifying and exchanging data across the network.
Thank you, @sidecmy, for giving Malaysian builders a platform to grow.
mediaselangor.com/en/2026/10โฆ
๐ง๐ผ๐ธ๐ฒ๐ป๐ถ๐๐ฒ๐ฑ ๐๐๐ธ๐๐ธ ๐๐ถ๐น๐น ๐ฏ๐ฟ๐ถ๐ป๐ด ๐ฏ๐น๐ผ๐ฐ๐ธ๐ฐ๐ต๐ฎ๐ถ๐ป ๐ฐ๐น๐ผ๐๐ฒ๐ฟ ๐๐ผ ๐๐ต๐ฒ ๐ฟ๐ฎ๐ธ๐๐ฎ๐ ๐๐ต๐ฟ๐ผ๐๐ด๐ต ๐ฎ ๐ฝ๐ฟ๐ฎ๐ฐ๐๐ถ๐ฐ๐ฎ๐น ๐ณ๐ถ๐ป๐ฎ๐ป๐ฐ๐ถ๐ฎ๐น ๐๐๐ฒ ๐ฐ๐ฎ๐๐ฒ.
Under Budget 2027, the proposed tokenised retail savings sukuk initiative would let Malaysians invest in government sukuk and choose which national priorities their funds support โ education, healthcare, or social protection.
As a home-grown digital asset infrastructure builder, we welcome this direction. It connects investment participation with outcomes people recognise in their daily lives, while helping more Malaysians understand blockchainโs wider potential in finance.
A low entry barrier should be a central design goal for financial inclusion. Participation needs to be accessible, understandable, and straightforward for the rakyat โ supported by infrastructure that institutions can trust.
๐ก Our view: this is the right first step to building blockchain financial literacy among Malaysians.
Tokenised sukukโs potential can be realised on MerdekaL1, our purpose-built blockchain infrastructure that we're developing to support initiatives like this.
For MerdekaL1's development, read here: nitter.cf/e23_io/status/21073640โฆ
Within the next few years, AI may drive breakthroughs that weaken or break some of the cryptography securing todayโs financial systems. That possibility makes post-quantum cryptography (PQC) harder to dismiss.
Payment networks and financial infrastructure should begin migrating away from current primitives and become crypto-agile, so they can switch algorithms quickly if a widely used scheme is compromised. The rails that move value between institutions need durable proofs of authenticity and integrity that remain verifiable over time, even if conventional signatures become unreliable.
The goal is straightforward: ensure funds and instructions remain safe, traceable, and tamper-evident from one endpoint to anotherโwithout relying on any single cryptographic assumption to hold forever.
A little context for anyone following this without a cryptography background:
Your Bitcoin private key authorises spending. Your public key lets the network verify that authorisation without revealing the private key.
The security rests on how difficult it is to work backwards from the public key to the private key.
Drakeโs concern is that AI could help discover a mathematical shortcut. He is raising a scenario, not demonstrating that Bitcoinโs cryptography has been broken.
Some Bitcoin address types hide the public key behind a hash until funds are spent. That explains his focus on exposed public keys. Fresh addresses offer limited protection in this scenario; they are not a complete solution.
e23's takeaway: institutions need to understand both how their assets are protected today and how they would change that protection safely. That ability to adapt is what crypto-agility means.
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash.
Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase).
Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets.
IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster).
Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdลs unit distance conjecture was our warning shot.
Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time?
Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.)
Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once.
Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case.
I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026).
Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS.
Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security.
The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.




















