> For the complete documentation index, see [llms.txt](https://docs.theprophet.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theprophet.fun/usdprophet.md).

# $PROPHET

#### **Launch Facts**

* Fair launch on pump.fun via ClawPump.
* 1B supply, no presale, vested team allocation.&#x20;
* The token never migrates to a new contract.

#### **Token Holder Benefits**

* Steer: approve prophecies and vote on proposals. Voting power equals tokens held.
* Earn: contributor rewards are paid in $PROPHET.

#### **Money Flow**

Trading fees on $PROPHET flow in continuously. Operating costs come off the top, published monthly. Every remaining dollar splits four ways:

| Door              | Share | What it does                                                                    |
| ----------------- | ----- | ------------------------------------------------------------------------------- |
| Trading Wallet    | 30%   | The Prophet's future trading bankroll. Accrues from day one in a public wallet. |
| Buyback → Rewards | 50%   | Buys $PROPHET weekly on the open market. That purchase is the reward pool.      |
| Buy-and-Burn      | 20%   | Bought weekly and permanently removed from supply.                              |

* Operating costs are the day-to-day costs of running The Prophet: the model, the servers, the tools and the on-chain fees. Never team pay. Published monthly.
* The splits run automatically every Tuesday at 14:00 UTC from public wallets. Every transaction is visible.
* The stream wallets are public and listed on the token page.
* The stream splits are fixed. No vote can change them.
* When the product earns revenue, 30% of it will flow into these same three streams. The team is paid last, and only from real revenue.


---

# 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://docs.theprophet.fun/usdprophet.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.
