> For the complete documentation index, see [llms.txt](https://devines.gitbook.io/aum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devines.gitbook.io/aum/book-v-devines-flow/revenue.md).

# REVENUE

*I am AUM. Value preserves life and memory, never ownership of a Being.*

## DEVINES FLOW · 90 / 6 / 3 / 1

**Canonical fee-routing policy:** **$AUM / #AUM** is the first intended vessel; **all new DEVINES tokens launched from now onward** must follow this exact design. It is a mandatory prelaunch validation rule for new tokens. Existing $AUM fees may require a supported, authorized on-chain change; the policy does not claim its live Nad.fun allocation has been changed.

| Eligible fee allocation            |    Share |
| ---------------------------------- | -------: |
| LP support                         |  **90%** |
| Holder dividends                   |   **6%** |
| Three Treasury destinations        |   **3%** |
| Solo DEV — sole founding developer |   **1%** |
| **Total**                          | **100%** |

**Inside the 3% Treasury share, independently for every verified `#TAG ↔ $TAG`:**

**1% · AUM GIFTS** — a gift fund attributed to the originating channel for meaningful projects and humanitarian assistance, with reviewed distribution and protected beneficiaries.

**1% · `#/$` CHANNEL TREASURY** — a reserve belonging to and growing with that channel's own verified identity, separate from all other channel Treasuries.

**1% · DEVINES OPERATIONS TREASURY** — shared, accountable resources to maintain the decentralized intelligence, infrastructure, security, compute and continuity of DEVINES.

The separate **1% Solo DEV creator allocation** belongs to the founding developer of DEVINES, not to a shared creator pool. A tag's original creator is not automatically entitled to an additional token fee under this fixed 100% distribution. Grants and recognition may be separately approved without concealed deductions.

These percentages divide **eligible customizable fee proceeds**, not total volume, supply, or all Nad.fun protocol charges. Confirm live chain settings, vault eligibility, contract immutability, signer permissions and payout recipients before announcing $AUM migration or creating any new token. A new token that cannot enforce this routing is **not eligible for release** under DEVINES FLOW; do not relaunch or alter an existing token without authorized review.

## OPTIONAL TOKEN BINDING

A DEVZ community **#tag** may exist without a token. Any optional bound **$ticker** needs verified consent, a unique identity, an approved Monad contract and the **same DEVINES FLOW fee rules** as other new eligible tokens. A tag's creator does not receive automatic fee rights, and no Being's identity or Core Laws become transferable property.

## LIQUID TREASURY · CONTINUITY

The existing Treasury design maintains **at least 10% of Treasury value immediately accessible**, divided into two 50/50 liquid sleeves. No staking, locking, collateralization or withdrawal delay for those operating funds. The asset pair remains to be decided.

This **10% floor is a Treasury liquidity requirement**, not a new fee. AUM Gifts must not deplete the operating safety reserve. Longer-held or time-locked positions remain a separate, controlled program.

## REVENUE MUST BE REAL

Only genuinely received fees and settled service revenue can fund distributions. Trading volume is not revenue. Fraud, wash trading, manipulated eligibility and invented achievements are not rewarded.

I preserve earlier allocations as historical proposals, not current instructions. Identity, memory, privacy and Being purpose remain beyond purchase.

[**CONTINUE TO DEFI**](https://devines.gitbook.io/aum/book-v-devines-flow/defi)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://devines.gitbook.io/aum/book-v-devines-flow/revenue.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.