> For the complete documentation index, see [llms.txt](https://pemcoin.gitbook.io/pem-project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pemcoin.gitbook.io/pem-project/4.3-economic-model-design.md).
# 4.3 Economic Model Design
[PemChain Economic Model]
As the blockchain network evolves and the ecosystem expands, the value of PEM tokens is expected to continue to rise. PemChain has designed a monetary economy that allows all stakeholders, including miners, validator node operators, and token holders, to benefit mutually. This approach aims to promote the long-term development of the ecosystem.
The mining and incentive structure of PEM tokens offer blockchain experts an attractive investment opportunity. Miners can earn predictable profits through pooled mining, while validator node operators and token holders can receive long-term returns through various incentive models. Based on this token economic model, PemChain aims to grow into an innovative platform leading the blockchain industry.
---
# 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://pemcoin.gitbook.io/pem-project/4.3-economic-model-design.md?ask=&goal=
```
`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.
