> For the complete documentation index, see [llms.txt](https://docs.qms.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qms.finance/introduction.md).

# Introduction

<figure><img src="/files/bHA58gVVci64mcg6bZLX" alt=""><figcaption></figcaption></figure>

The QMS Network ("QMS") is a Layer-1 blockchain purpose-built for the post-quantum era. Its consensus layer is quantum-resistant by design, and it is built to accommodate quantum hardware in its miner network. Every building block of this chain is optimized for this future, from block time to consensus mechanism to tokenomics.\
QMS achieves this by using Proof-of-Useful-Work (PoUW) as its consensus mechanism. By replacing the wasteful hashing from standard PoW with computation suited to quantum hardware, QMS becomes a decentralized cloud computing platform that quantum miners can power.\
This is the "useful" in proof-of-useful-work: commercial clients pay to have their optimization problems solved, giving miners a second source of income on top of standard block rewards. This reduces the inflationary cost of securing the chain and triggers a compounding cycle: more rewards attract more miners, which grows the platform's capacity, which attracts more clients.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.qms.finance/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.