Project Research Dossier: QMS Finance

Project Name: QMS Finance

1/7

Quantum Monetary System (QMS) is a new layer-1 attempting to combine post-quantum security with proof-of-useful-work (PoUW). Instead of pure hashing, which has value only for network security, miners are intended to solve optimization problems, including QUBO problems, and eventually receive payment from commercial clients for high-quality solutions. QMS therefore aims to create a decentralized computing marketplace in which one solver run can generate both a block reward and a potential client payment for the miner. ( https://docs.qms.finance/overview/the-quantum-challenge-and-opportunity.md , https://4237698239-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlxcI4pd9LbQ4gbo3eSr%2Fuploads%2Fgit-blob-3dff83b15529c3bf552bad0c59ff1a420f9b03ea%2FQMSWhitePaper.pdf?alt=media ) Preliminary assessment: a very early high-risk infrastructure project with a strong research thesis but high execution, adoption, tokenomics, and decentralization risk. Until QMS has a functional mainnet, open mining, a client marketplace, finalized emission parameters, and independent security reviews, it should be viewed as a technology bet on a future market rather than as a mature layer-1 asset.

2/7

1. What QMS builds and why it matters

QMS is building a layer-1 blockchain for the “quantum era.” The project is based on two propositions. First, future quantum computers may break the elliptic-curve signatures on which much of the existing blockchain system relies. Second, the same quantum hardware may be useful for optimization problems such as portfolio optimization, risk selection, clustering, vehicle routing, and scheduling. (https://docs.qms.finance/overview/the-quantum-challenge-and-opportunity.md)

The architecture has four layers:

• the network layer for peer-to-peer communication and catch-up;

• the custom consensus layer using PoUW and chain selection;

• the finality layer for explicit finality;

• the EVM-compatible execution layer for transactions and smart contracts.

QMS presents this as a flywheel: clients pay for optimization, payments increase miner revenue, stronger revenue attracts more computing capacity, and greater capacity makes the marketplace more attractive to clients. However, this remains a design hypothesis. The official materials explicitly state that the strength of this cycle depends on uptake, meaning real demand. (https://4237698239-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlxcI4pd9LbQ4gbo3eSr%2Fuploads%2Fgit-blob-3dff83b15529c3bf552bad0c59ff1a420f9b03ea%2FQMSWhitePaper.pdf?alt=media)

3/7

2. Product status and execution progress

QMS v0.1 is live on Testnet. Users can connect an EVM wallet, receive free test tokens, make transactions, deploy smart contracts, and test QWAP, an independent DEX being built on QMS. The RPC uses Chain ID 19480, the target block time is 10 seconds, and the explorer is testnet.qmsscan.io. Testnet tokens, including tokens labelled QMS, USDC, USDT, WETH, and WBTC, have no monetary value. (https://qms.finance/news/welcome-to-qms-testnet)

The roadmap is divided into stages. V1 is intended to add feature-complete PoUW consensus, the PQ finality layer, and production-oriented EVM execution. V2 is intended to focus on the useful-work marketplace, backend conversion of client data into QUBO, and solution rewards. In the AMA, the team identifies opening mining to external participants, a marketplace preview, and the full marketplace as priorities. (https://qms.finance/news/qms-ama-recap-the-vision-the-testnet-the-road-ahead)

3. QMS tokenomics

QMS uses a single native token for gas fees, miner rewards, and finalizer rewards. Transaction fees follow EIP-1559: the base fee is burned, while the optional priority fee goes to the miner that included the transaction. Client solution rewards are intended to be paid from the client’s locked funds, but the marketplace contract may determine what portion of the client payment is burned and what portion goes to miners. (https://4237698239-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlxcI4pd9LbQ4gbo3eSr%2Fuploads%2Fgit-blob-3dff83b15529c3bf552bad0c59ff1a420f9b03ea%2FQMSWhitePaper.pdf?alt=media)

4/7

What has not been disclosed or finalized

The white paper explicitly states that the exact parameter values are not yet fixed.

The reviewed primary sources do not contain a canonical table for: •maximum supply or a fixed cap; •genesis allocation; •premine; •team/advisor allocation; •private sale; •investor unlocks; •vesting/cliffs; •TGE date; •mainnet token contract address; •initial circulating supply.

Therefore, it is currently impossible to calculate FDV, market cap at TGE, or a future dilution profile reliably. This is particularly important for a PoUW layer-1: if client revenue is absent or small, security costs may be financed mainly through newly minted tokens, creating pressure on holders.

4. Unlock and dilution risk

QMS currently has no disclosed investor/team unlock calendar that can be analyzed. This does not mean dilution risk is low; rather, it is uncertain and unquantified.

The main source of potential dilution is block rewards. Protocol minting creates new tokens, and the white paper explicitly acknowledges that the cost of block rewards falls on existing token holders through dilution. Burn mechanisms may offset part of the emissions, but their scale will depend on transactions, client marketplace payments, and finalization activity. Since v0.1 does not yet have the complete block-reward system or client payments, there is no historical data with which to estimate net issuance. (https://4237698239-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlxcI4pd9LbQ4gbo3eSr%2Fuploads%2Fgit-blob-3dff83b15529c3bf552bad0c59ff1a420f9b03ea%2FQMSWhitePaper.pdf?alt=media)

5/7

5. Team and verification signals

Confirmed signals: an official QMS website, documentation, a September 2026 version 1.0 white paper, a public testnet, explorer, RPC, onboarding documentation, QWAP integration, and developer documentation exist. QMS publishes engineering/news materials and official X, LinkedIn, Telegram, Discord, and Medium channels.

The AMA officially names Christopher Portmann as CTO. QMS describes him as having approximately 15 years of academic work in quantum and classical cryptography and around five years at blockchain companies. This is a positive personal verification signal, but it does not replace full disclosure of the team, legal structure, and financing. (https://4237698239-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlxcI4pd9LbQ4gbo3eSr%2Fuploads%2Fgit-blob-3dff83b15529c3bf552bad0c59ff1a420f9b03ea%2FQMSWhitePaper.pdf?alt=media)

6. Key risks

Tokenomics and dilution risk. Exact emission parameters have not been set, while maximum supply, initial allocation, and vesting have not been published. Block rewards may dilute holders, while burns will depend on actual usage. This makes any token valuation before the final specification highly speculative.

Post-quantum scope risk. The consensus and planned finality layers are designed around post-quantum security, but the current testnet execution layer uses standard Ethereum signatures. Users may remain exposed if they do not migrate to a PQ-compatible account design in the future. PQ account upgrades are not yet available in v0.1.

Governance risk. The white paper explicitly states that voting rules, proposal thresholds, vote weighting, and the relationship between QMS Network and on-chain governance are still to be defined. Until these rules exist, holders do not have clearly confirmed governance rights or protection against unilateral parameter changes.

6/7

My position: I do not hold QMS tokens, mining allocation, private allocation, or any other financial interest in QMS Network; I am not a team member, advisor, or investor in the project.

Overall assessment: QMS has one of the more interesting theses among early layer-1 projects: use post-quantum architecture and turn security computation into a potential decentralized optimization marketplace. The technical idea is concrete, the documentation contains formal details on PoUW, QUBO, and token flows, and the testnet is already available for public testing.

Until these items are resolved, QMS should be classified as a high-risk pre-mainnet infrastructure project with substantial execution, adoption, dilution, and centralization risk. A strong research narrative alone does not prove that QMS can become an economically sustainable layer-1 or that client payments will offset future token inflation.