# Governance

### Overview

Nabla aims to become a permissionless, decentralized, and trustless protocol. To steer the protocol and its strategic direction, Nabla aims to build a DAO consisting of key contributors, partner protocols, investors, users, and community members. They can express their opinion through various governance channels (Forum, Discord, TG) and vote with $sNABLA tokens.

The DAO will gradually receive more responsibilities and essentially be responsible for the following areas:

* Adjust protocol parameters (e.g. fee percentage, fee split, token incentives)
* [Adding new pool hubs/pools\*](#user-content-fn-1)[^1] and removing pools
* Setting and adjusting slippage parameters and pool caps
* Treasury expenditures (e.g. grants, contributor rewards, marketing activities)
* New strategic initiatives (e.g. new chain deployment, partnerships)

The above list is not exhaustive. However, Nabla aims to become as trustless as possible. This requires the impact of governance on the core protocol to be as minimal as possible and the use of automation where possible. Thus, reliance on human interaction is reduced, and security is simultaneously increased by eliminating any attack vectors.

<br>

[^1]: Given Nabla’s unique design, setting up new pools comes with specific requirements for the underlying asset and its oracles. Hence, adding pools is initially not permissionless. Over time, however, the DAO should also be able to cover this via on-chain governance.


---

# Agent Instructions: 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:

```
GET https://docs.nabla.fi/nablatoken/governance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.