> For the complete documentation index, see [llms.txt](https://niftsy-protocol-niftsy-1.gitbook.io/niftsy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://niftsy-protocol-niftsy-1.gitbook.io/niftsy/key-documents/tokenomics/general-provisions.md).

# General provisions

General provisions of tokenomics:

1. The total token emission is **500,000,000 NIFTSY** for all chains/DAGs.
2. The emission in each blockchain (or DAG, and/or other DDN) occurs according to a formula that reduces emission by **12%** from the previous DDN.
3. The emission initially occurs to a multisig DAO in the amount of 500,000,000, and then there is a primary burn for a given DDN.
4. The main functions of the token are listed in the corresponding section - these include participation in the DAO; use of dApps DAO Envelop functions; discounts, and other functions.


---

# 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://niftsy-protocol-niftsy-1.gitbook.io/niftsy/key-documents/tokenomics/general-provisions.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.