> For the complete documentation index, see [llms.txt](https://whitepaper.getpaid.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.getpaid.family/usdget-economics/governance.md).

# Governance

Covers proposed $GET holder governance over fee splits, supported chains, treasury allocations, anti-vamping controls, and future technical voting mechanics.

$GET governance is intended to give holders influence over selected protocol-level parameters. This governance scope is proposed. $GET has not launched, and no governance system is deployed.

{% hint style="info" %}
The proposed model identifies potential governance decisions. Technical governance mechanics remain subject to final specification.
{% endhint %}

### Governance scope

#### 1. Fee parameters

Holders may vote on the default fee split. The current model assigns 60% to creators, 10% to burn, 10% to buyback, and 10% to protocol. It accounts for 90% of routed fees, with the remaining allocation to be finalized before implementation.

#### 2. Supported chains

Holders may vote on which chains the protocol supports.

#### 3. Treasury

Holders may vote on treasury allocation. Proposed allocation areas include:

* Operations
* Insurance
* Development
* Grants

#### 4. Anti-vamping parameters

Holders may vote on the cooldown, lock period, and threshold used by the proposed anti-vamping design.

#### 5. Other protocol parameters

Holders may vote on other selected protocol parameters where governance control is defined.

### Governance mechanics

Quorum, voting duration, proposal thresholds, delegation, timelocks, execution, emergency governance, and voting contract architecture will be defined as the governance system moves toward implementation.


---

# 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://whitepaper.getpaid.family/usdget-economics/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.