> For the complete documentation index, see [llms.txt](https://docs.silverswap.io/spiritswap-v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silverswap.io/spiritswap-v2/tokenomics/usdspirit/emissions.md).
# Emissions
As of March 2022 Team tokens have finalized their vesting period and completed their distribution round. Moving forward emissions are totally dedicated towards two emission endpoints:
* Farm / Gauge: 81.82%
* DAO: 8.18%
**Farm / Gauge emissions:** Are governed through inSPIRIT holders by way of [gauge control](/spiritswap-v2/core-features/yield-farms/gauges.md). While the emission allocation to Farms / "Gauges" are constant as per the diagram below, it is inSPIRIT holders who decide which farms receive variable emission allocation weight, each epoch (weekly). \
\
**DAO emissions:** Are sent to the SpiritSwap Multi-Sig wallet, which are then put into an investment strategy decided upon by the Multi-Sig until the funds are required for use. Use of these funds are restricted for activities such as;\
\
\- Development expenses\
\- Service Contract expenses\
\- Marketing expenses \
\- General operations to maintain the upkeep of the exchange
---
# 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.silverswap.io/spiritswap-v2/tokenomics/usdspirit/emissions.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.