QMS Network is a Layer-1 blockchain built for the post-quantum era. Waitlist is open, visit our website below to join:
Joined May 2026
- Tweets335
- Following2
- Followers20.9K
- Likes291
Most chains treat quantum hardware as something to defend against.
QMS is designed to put it to work.
22.5M+ transactions on QMS Testnet in four weeks.
A week ago, we were at 16M+.
More than 3.3M addresses have transacted.
Thanks to everyone testing the network and sharing feedback. Keep testing, and let us know what you find.
Action needed if you LP on @QWAP_xyz:
Remove liquidity from the USDT, USDC, WBTC, and WETH pools before Thu, Oct 29. You can redeposit once the new pools are live.
Details from the QWAP team below.
Heads up, QWAP LPs: We're deprecating and re-adding USDT, USDC, WBTC and WETH on the testnet, along with their liquidity pools, on Thursday, Oct 29 at 9 AM UTC.
If you have liquidity in any affected pool, please withdraw it before the update. You can add liquidity again once the new pools are live.
Questions? Ask us on Discord.
Qubit counts alone can’t tell you how close quantum computers are to breaking encryption. The machine also has to correct its errors fast enough to finish the attack, and that depends partly on software running on ordinary computers.
Last week showed why:
Iceberg Quantum estimated RSA-2048 could be broken with 72,000 physical qubits in 3.7 days, assuming a 1µs correction cycle. Its decoder averages 4µs per round. How decoding keeps pace with that assumed cycle rate is an important implementation question.
Quantinuum reported an estimated logical-memory error rate of 5 × 10⁻⁶ per correction cycle, about five errors per million rounds. It decoded the experimental data offline. The same paper benchmarks decoders fast enough for real time, but the experiment didn’t use them live.
Leiden and Riverlane found standard correlated decoding erring about 4.4 times more often than simpler matching in one tested configuration with very low hardware error rates. They also proposed a fix.
When a smaller attack estimate makes headlines, check the conditions:
1. How reliable must the qubits be? Iceberg’s estimate assumes a physical error rate of roughly one in 1,000.
2. Has the complete error-correction system demonstrated the speed the estimate assumes?
Air cargo is expected to generate $162 billion in revenue in 2026, according to IATA.
Every flight has limited space and weight capacity. Choosing which shipments to carry affects what it can earn. So, better loading decisions have (huge) commercial value.
Here’s a tiny example of choosing the best combination within a limit, illustrating the basic idea behind the optimization problems QMS’s Proof of Useful Work is designed to tackle:
You have 10 units of cargo space. Choose a combination of packages that gives the highest total value.
A: 6 units, value 12
B: 5 units, value 10
C: 5 units, value 9
D: 4 units, value 5
Each package can be loaded once, whole or not at all. You cannot exceed 10 units in total.
Which packages would you load? Reply before reading anyone else’s answer.
The hard part of a post-quantum migration is coordination, not cryptography, and that cost grows with the size of the chain.
The algorithms are standardized. What takes years is getting every wallet, custodian and bridge to move, each on its own schedule.
QMS has one advantage here: it's early.
There's a question bigger chains are already wrestling with: What happens to wallets that never upgrade?
Some owners have lost their keys, others have simply walked away. And if those accounts become vulnerable to quantum attacks, what should happen to the funds?
Ethereum's own post-quantum team says this is still an open governance question. It estimates that long-abandoned funds account for around 0.1% of ETH's supply, compared with roughly 5% of Bitcoin's.
QMS is planning for this from the start.
The proposal is to freeze accounts that haven't migrated once post-quantum signatures are widely supported. Owners with the original seed could then recover access using a post-quantum-secure zero-knowledge proof.
It's much easier to plan for this while a network is young, before years of wallets, applications and infrastructure have built up around it.
That's an advantage QMS has today, and one worth making use of.
Worth a read if you haven't yet:
teapawt.net/QMSNetwork/status/2092…
Which testnet stat do you most want to know each week?
11%Busiest day
21%Verified contracts
59%Swaps on QWAP
10%Something else, tell us👇
351 votes • Final resultsA portfolio manager can’t judge an investment by expected returns alone. It also has to fit their risk budget and position limits.
The same idea applies to QMS’s planned useful-work marketplace.
Clients will define what a solution needs to achieve and the reward for meeting those requirements. Miners will know what to work toward, and clients will decide what’s worth paying for.
See details in our white paper: §7.2 Solution Rewards, p. 18: docs.qms.finance/whitepaper
16M+ transactions processed on QMS Testnet in three weeks!
A week ago, we were at 10M+.
Thanks to everyone testing the network and sharing feedback. Keep pushing it and let us know what you find.
Day 3 of 7. You can still start the Testnet Streak today and earn Quanta each day you take part.
The QMS Testnet Streak kicks off today.
Thanks to your feedback, we've made improvements to swaps and liquidity provision, so now it's time to try them out.
Join our 7-day challenge to earn Quanta, our Discord community reward points that count toward the October leaderboard.
Here's how:
→ New participant or switching wallets? Submit your wallet in Discord first.
→ Make 1 test-token swap + add liquidity daily on @QWAP_xyz
→ Earn 8 Quanta points per day (10 for Pioneers & Qwabbits)
→ Complete any 6 of 7 days for a bonus
→ Earn up to 70 Quanta points (88 for Pioneers & Qwabbits)
Head to our Discord announcements for full details.
What’s changed in post-quantum migration since our September update? Here’s where things stand today:
Bitcoin: September 18's “Output Public Key Exposure Classification” draft classifies existing outputs by exposure. It's informational and observation-only, has no BIP number and proposes no consensus change.
Solana: On October 13, Squads tested Falcon-512 multisig voting on mainnet using Blueshift's Vector verifier. It's app-level and opt-in; the fee payer still needs Ed25519. SquadsX support is planned for its next release, not confirmed shipped.
ZKsync: Airbender Prime, announced October 13, uses hash-based STARKs. Its L1 proofs will use Keccak-256 commitments instead of BN254 pairings. That's a planned proof-system change; user signatures are unchanged.
NEAR: On October 1, Fireblocks demonstrated rotating one funded mainnet account from Ed25519 to ML-DSA-65 in two transactions, keeping its address. nearcore 2.14, adding Universal Account IDs, reached release candidate 5 on October 19. It isn't on mainnet.
Where things stand:
Bitcoin: BIP-360 and BIP-361 remain Draft. Neither is activated. BIP-360 mitigates long-exposure attacks but adds no post-quantum signature. BIP-361 covers migration and a legacy-signature sunset, but requires a post-quantum signature BIP that doesn't yet exist. August's SHRINCS signature draft has no BIP number. There's no activation proposal.
Ethereum: EIP-8141, Frame Transactions, is Scheduled for Inclusion in Hegotá but remains Draft; its specification may evolve. Hegotá is expected in Q2 2027, with no confirmed date. This account-abstraction approach would let accounts adopt new signature schemes later.
The Ethereum Foundation's Protocol cluster has a self-imposed December 2029 target for quantum resistance across execution, consensus and data, to be reassessed in January 2027. No post-quantum signatures are live on L1.
Solana: The Foundation's plan remains at research and evaluation. There are no network-wide post-quantum transaction or consensus signatures. Anza's Quantumglow is a post-quantum consensus research design with no deployment date. Winterwallet works on mainnet as an opt-in app-level vault and isn't formally audited.
NEAR (not in our September snapshot): ML-DSA-65 has been live on mainnet since July 20 as an opt-in key type, and NEAR's roadmap reports Meteor Wallet support is live. Validators still use Ed25519 for block production. Post-quantum consensus is targeted for end-2027; Chain Signatures has no post-quantum threshold-signing timeline.
Ethereum L2s: No major L2 uses post-quantum transaction signatures protocol-wide by default. Starknet's BLAKE2s OS program and configuration hashes are live on mainnet; Falcon-512 accounts are opt-in, with a mainnet demonstration. L2s still depend on Ethereum for settlement, bridge messaging and blob data availability.
None of the ecosystems covered here has completed a full-stack post-quantum migration.
QMS Testnet runs a Reth fork with the standard Ethereum JSON-RPC. Your Foundry or Hardhat setup should work as-is.
Known differences, so you don't have to find them:
→ finalized tag returns genesis (no finality layer yet)
→ PREVRANDAO returns 0
→ no blob txs
Found one that isn't on this list? Let us know.