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!

Original Tweet
X | LinkedIn | Medium | Docs

Check out the testnet activity here: https://testnet.qmsscan.io/

QMS AMA Recap: The Vision, The Testnet, The Road Ahead

Our first AMA is in the books — over 1,000 of you joined CTO Christopher Portmann live. The full recap is up on our blog, but here are the highlights:

The vision
→ Consensus: hash-based, quantum-resistant by design — no signature vulnerability to patch later.
→ Execution: EVM-compatible today, migrating to post-quantum signatures over time.
→ Finalization: launches with a permissioned set of operators to protect the chain while it's young, decentralizing in stages — post-quantum signatures here are a longer-term piece of the puzzle.

Testnet status
Live and open to everyone. The first 24 hours held up well, including a same-day fix after bots hit the faucet — anti-bot protection went out fast.

What's next
→ Opening mining to external participants
→ Finalizing the finalization layer, difficulty adjustment, and tokenomics
→ A marketplace preview
→ Connecting miners to real client problems
→ Post-quantum execution layer upgrades

No secretive development — the team wants the community testing and giving feedback as this builds out.

Read the full recap: https://qms.finance/news/qms-ama-recap-the-vision-the-testnet-the-road-ahead

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 @QWAPOfficial
→ 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.

Original Tweet
X | LinkedIn | Medium | Docs

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.

Original Tweet
X | LinkedIn | Medium | Docs

Steps: https://docs.qms.finance/for-developers/deploy-a-smart-contract

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.

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.

Original Tweet
X | LinkedIn | Medium | Docs

For a deeper dive into QMS's consensus design, block production, and post-quantum security, check out our whitepaper: docs.qms.finance/whitepaper

In less than 2 weeks, the QMS Testnet has passed 1 million addresses.

The explorer shows:
• 5.6M+ transactions
• 1M+ addresses
• 78.8K+ blocks
• 12.1s average block time

Thanks to everyone who has helped with testing. What other stats should we track?

Original Tweet
X | LinkedIn | Medium | Docs

On 7 October, Europol and Ethereum researcher Justin Drake gave crypto holders the same advice for 2 different threats: move funds to a fresh address that has never shown its public key.

Europol's worry is a future quantum computer, and Drake's is AI finding a mathematical shortcut, though no attack was named.

Either attack would start from a public key the chain can already see, so you can doubt the AI claim and the advice still holds. A fresh address only hides the key until you spend, and the lasting fix, a new kind of signature, takes years.

Original Tweet
X | LinkedIn | Medium | Docs

Where signatures sit on QMS:

Miners run solvers, and a hash lottery awards the block, with no public key signature in that mechanism. Wallets on this testnet use Ethereum-style signatures. Post-quantum signatures are planned for finality in a future release, initially with a permissioned set of finalizers.

Every proof-of-useful-work chain has to answer one attack: post a problem you already solved, then mine with the answer.

QMS removes the payoff in three ways (white paper §4.4):

- The solver has to be randomized.
- Its seed comes from the parent block hash.
- Blocks go to a lottery over valid outputs, blind to quality.

Solving problems well is what clients will pay for in the marketplace, planned for a future release.

Original Tweet
X | LinkedIn | Medium | Docs

10+ million transactions and counting on QMS Testnet.

Two weeks since launch, and things are moving fast.

Thanks to everyone who’s been part of the journey so far. Plenty more to come!

Original Tweet
X | LinkedIn | Medium | Docs

Found a bug while testing QMS? Report it so the team can reproduce and fix it.

Head to the 🎟│tickets channel on our Discord and fill out the bug report form: discord.gg/qmsnetwork

Please include:

→ What you were doing (swap, deploy, faucet, explorer, etc.)
→ Steps to reproduce, and whether it happens every time
→ Expected vs. actual result, including any error messages
→ Tx hash or wallet address, plus the approximate time
→ Wallet, browser, and device

To share screenshots or videos: After submitting the form, the bot will open a private thread for you. You can attach them there.

Original Tweet
X | LinkedIn | Medium | Docs

The more details you provide, the easier it is for us to investigate and fix the issue. 🫡

A quick reminder: QMS Testnet tokens have no real value. Always use official QMS links, never share your seed phrase or private key, and remember that our team will never DM you first.

Quantum computing could do more than threaten today’s cryptography.

QMS aims to use it to solve real-world problems, while using that same computation to secure the network, once quantum solvers outperform classical alternatives.

Original Tweet
X | LinkedIn | Medium | Docs

See details in our white paper: docs.qms.finance/whitepaper

Google just cracked open a quantum computing bottleneck researchers have been working on since 2004.

To perform certain advanced operations, quantum computers need special resources called "magic states." Producing reliable ones is so demanding that, by some estimates, it could consume up to 95% of a future quantum computer's resources.

In 2024, Google researchers proposed a technique called "magic state cultivation." It worked on paper.

Now, research published in Science shows it working on Google's Willow processor:

• 40× fewer errors than uncultivated states
• 99.99% magic state fidelity

The next challenge is making it work at scale.

For blockchains, progress like this has two implications:

More powerful quantum computers could eventually threaten today's cryptographic systems. They could also become valuable computing resources.

QMS is designed with both possibilities in mind.

On security: QMS's consensus doesn't rely on public-key signatures for block production. Post-quantum transaction signatures are also on the roadmap.

On computing: Proof-of-Useful-Work aims to turn mining into productive computation, solving optimization problems that clients would pay for.

QMS starts with classical computing, with a long-term plan to incorporate quantum hardware as it becomes commercially competitive.

Original Tweet
X | LinkedIn | Medium | Docs

For more details on Google's research:
https://x.com/googlequantumai/status/2110799626554998921

Two important quantum computing developments last week:

Anthropic is reducing the computing resources quantum algorithms need, while Google is improving the hardware's reliability.

Both advances could bring practical quantum computing closer, reinforcing the importance of preparing cryptographic systems for the post-quantum era.

1️⃣ Anthropic: AI makes quantum algorithms more efficient

- Claude Mythos 5 designed circuits using fewer qubits and costly operations in 7 of 8 tasks.
- In one optimization task, it reduced the required operations from 5.1 million to 440,000, roughly 12x fewer.
- It also found a new approach to elliptic curve calculations, which are relevant to modern cryptography.

More efficient algorithms could reduce the hardware and computing time needed for practical quantum applications, including future cryptographic attacks. These remain theoretical resource estimates.

2️⃣ Google: Willow achieves 40x fewer errors

- Google demonstrated a technique called magic state cultivation on its Willow quantum chip.
- It reduced errors by roughly 40x and achieved 99.99% logical fidelity when preparing T-states.
- These states are essential for running complex calculations on error-corrected quantum computers.

Better error correction could make large-scale quantum computers more practical. The results are promising, although the technique still needs to work at a much larger scale.

Original Tweet
X | LinkedIn | Medium | Docs

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 @QWAPOfficial
→ 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.

Original Tweet
X | LinkedIn | Medium | Docs