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

# Governance

The ARKS community believes that ARKS governance should not be limited to the functionality and settings of NFT lending, but should also empower users with the right to manage platform assets for effective governance.

**Treasury**

The ARKS community will gather all community revenue into the Treasury, including but not limited to:

1. 80% of the profit after deducting the cost of redeem fees
2. 20% of the cost of upgrading (paid in ARKS) will go to the national treasury, while the other 80% will be burned and governed by DAO. There may be inflation in the future, but only after the total amount of unlocked ARKS reaches 80% will there be possible inflation.
3. A certain percentage of protocol interest revenue
4. National treasury asset management
5. Fees for using the "buy now pay later" or collateralized lending protocols
6. NFT transaction fees (not currently collected during the community expansion period, but may be collected in the future)

The Treasury is mainly composed of a combination of USDT and ARKS, and users can use their veARKS tokens to vote on how the funds in the Treasury are used and allocated.

**Governance Platform**

In the initial stage, the platform will be managed by the team who will collect and initiate governance proposals, which will be voted upon by veARKS holders to decide on the proposal outcome. Later on, the governance process will gradually transition to decentralized governance, where users can initiate proposals and use their veARKS tokens to vote on the proposal outcomes.


---

# 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://arkslabs.gitbook.io/arks/dao/governance.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.