> For the complete documentation index, see [llms.txt](https://organic-1.gitbook.io/organic-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://organic-1.gitbook.io/organic-docs/tokenomics/fees-and-treasury-flow.md).

# Fees and Treasury Flow

#### Creator Fees and Treasury Flow

Here’s the simple flow: until the treasury multisig is live, creator fees go to the dev wallet. As we finalize the treasury setup, those fees will be routed into the multisig, with a small ops wallet for day-to-day needs and a public ledger so anyone can track every move. Rewards are then split using the same task weights and scores defined in Contributors & Points.

**Current**

* Creator fees route to the dev wallet: `CuBV7VVq3zSrh1wf5SZCp36JqpFRCGJHvV7he6K8SDJ1`
* Treasury is being set with a Squads multisig

**Building next**

* Route fees from dev wallet to **\[treasury main address]**
* Ops wallet with a daily cap
* Biweekly public ledger

**Split**

* Split by task weights and scores as defined in **Contributors & Points**


---

# 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://organic-1.gitbook.io/organic-docs/tokenomics/fees-and-treasury-flow.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.