> For the complete documentation index, see [llms.txt](https://prizm.gitbook.io/pzm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prizm.gitbook.io/pzm/wp/tokens.md).

# Tokens

![Prizm Emission](/files/-MSLVmzByU7ceAMV0gCF)

{% hint style="info" %}
The initial emission is **10 million PZM** and the final amount is **6 billion PZM**. The coins were issued with the creation of the Genesis block (the first block in the blockchain). Premining implemented in all countries of the world, at nominal cost, in limited quantities, to achieve the starting of **decentralization** Prizm. The total amount of PZM will be 6 billion tokens. Account Genesis generates anti-coin signals of Premining (signal to send the coins for a certain wallet) to the limit of minus 6 billion PZM
{% endhint %}

### The existence of anti-coins in Genesis has several interesting side effects:

All tokens sent to the Genesis account are effectively destroyed, as the negative account balance cancels them The main function of Prizm is the traditional payment system, but was created to do much more. The goals of the CWT community can be achieved under the condition of PZM parity with the main Fiat currencies.


---

# 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://prizm.gitbook.io/pzm/wp/tokens.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.