QMS Testnet is now live.
Our first public release. The EVM-compatible execution layer is open:
→ Add QMS Testnet to your wallet
→ Claim free test tokens from the faucet
→ Swaps and LP on @QWAP_xyz
→ View transactions on the block explorer
https://t.co/7ONsySIP4O
CT is debating what AI could do to curves and lattices.
QMS’s block-production lottery depends on neither. Here’s where signatures sit:
→ Block production: Miners run optimization solvers, and a hash lottery awards the right to produce a block. No public-key signatures in that mechanism. Today’s testnet uses randomly generated problems.
→ Finality: Planned to use post-quantum signatures from its first release, initially with a permissioned finalizer set. Planned for v1, the next release.
→ Wallets: Ethereum-style signatures today, with post-quantum account upgrades planned.
That means no block-production signature scheme to migrate. Finality and wallets still depend on the security of the signatures they use.
Fresh addresses buy time. As Justin points out, getting out of bunker mode still requires a cryptographic migration.
How much of a chain needs public-key cryptography at all?
On QMS, block production needs none. It's secured by computational work, with no miner signing keys to expose. Finality is designed around post-quantum signatures. The execution layer starts with standard EVM accounts using ECDSA, with a path to post-quantum accounts.
Whatever odds you put on an early Q-Day or a classical break, design the migration path before the threat sets the timetable.
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.
Steps: https://t.co/eh62FVWPFW
Post-quantum wallet signing is not in this release. Tooling that waits for a finalized block may hang or read genesis state. Use block confirmations.
Testnet state is not expected to carry over to the next version.
If you already have an Ethereum contract, deploy it on QMS Testnet and see how it runs.
Use Foundry or Hardhat. Standard EVM contracts need no code changes. Pay gas in test QMS using a throwaway wallet.
Test tokens have no monetary value.
Bots gave QMS Testnet its first public stress test. They swamped the faucet on day one, and anti-bot protection went in immediately.
Now it’s your turn:
→ Make a swap or provide liquidity on @QWAP_xyz
→ Deploy a contract and see how it runs
→ Open a block in the explorer and see what problem it solved
→ Find something unusual? Drop it in Discord
That’s what testnet is for: finding the edges before they reach mainnet.
Most people ask how to survive quantum computers.
QMS asks: what if they could work for the blockchain network?
In our first AMA, CTO @Christopher_QMS unpacked the vision, what the testnet proves today, and what comes next.
Full recap: https://t.co/TE7f4FhuBE
@QMSNetwork Testnet Beta just hit another milestone: 1 million transactions! It took a bit over 3 days to get there. 🙂
Thank you to our fantastic community for testing our chain! ❤️
We launched our @QMSNetwork Testnet Beta without doing any load testing. Our code worked. We opened the testnet to the public. Happy to see that we hit 75% utlization this morning, with some blocks full to near 100%. All is working smoothly. 🔥🚀🚀
Two days after launch, QMS Testnet’s explorer shows:
• 272K+ transactions
• 137K+ addresses
• 22K+ blocks
• 10.5s average block time
Thanks to everyone testing and sharing feedback. Keep it coming!
Come test QMS with us and earn Quanta, our community points for the Discord role holders.
Make a swap and add liquidity on @QWAP_xyz to earn 10 Quanta per set, up to 10 sets.
Submit your wallet in quanta-testnet on Discord before you start.
This campaign ends Oct 7. Join here: https://t.co/2KKjIO82TD
Quick faucet update:
We’re seeing very high demand, including automated traffic, so we’ve added new anti-bot protection to keep test tokens accessible to real users.
The update is live now. Queued requests are being processed and tokens should continue arriving over the next few hours.
Thanks for testing QMS Testnet with us.
Live in one hour: our CTO @Christopher_QMS on day one of the QMS testnet, plus answers to your questions from Discord.
See you there: https://t.co/ezXnYmkY8u
Quick faucet update:
We’re seeing very high demand, including automated traffic, so we’ve added new anti-bot protection to keep test tokens accessible to real users.
The update is live now. Queued requests are being processed and tokens should continue arriving over the next few hours.
Thanks for testing QMS Testnet with us.
Day one of the QMS Testnet, and our CTO is going live to walk you through it.
Join @Christopher_QMS to hear why we're building QMS, what we're testing, and what's next. Plus answers to your questions from Discord.
Today at 10:30 AM UTC.
X Space link below 👇