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

# Profit Model

Every distribution cycle, the profit generated by a business operation is distributed pro-rata to the Worker NFTs actively hashing in that operation.

## The formula

```
Profit per NFT = ( Your Hash Power in Sector X ÷ Total Active Hash Sector X ) × Sector Daily Profit Pool
```

## Variables explained

| Variable                        | Meaning                                                                                                     |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Your Hash Power in Sector X** | Your worker's Hash Power while assigned and hashing in that operation, with any durability penalty applied. |
| **Total Active Hash Sector X**  | The combined Hash Power of every Worker NFT currently hashing in the same operation.                        |
| **Sector Daily Profit Pool**    | The day's real-world profit from that operation, deposited into the Revenue Vault.                          |

## Worked example

Operation X generates a **$10,000 USDG** profit pool this cycle. The total active hash in the operation is **10,000**.

Your Worker NFT is a **Tier 4** (125 hash) at full battery and durability:

```
Share  = 125 ÷ 10,000 = 1.25%
Payout = 1.25% × $10,000 = $125 USDG
```

## The cost of running

Earning is not free — your worker consumes resources that you restore with $ANANAS:

* **Battery** drains each cycle and must be recharged.
* **Durability** wears down and must be repaired, especially below 50% where it applies a hash penalty.

Your net income is your payout minus the cost of keeping the worker running.

## Payout mechanics

* Profit is deposited into the **Revenue Vault** in stablecoin form (USDG/ETH or native).
* Each holder's claim is computed on-chain from active Hash Power.
* Holders **claim directly** from the Vault — no admin involvement.
* Payouts arrive as **ETH/USDG** stablecoins, with **$ANANAS** token rewards on top.
* The fund managers take a fee for operating the businesses; the remaining profit is distributed to holders.

## Transparency

* The formula is fixed and executed on-chain, so everyone receives exactly what they earned.
* There is **no fixed APY and no guarantee of returns**. The only thing that decides your payout is how the underlying real business performs.

## Related

* [The Work Hub](/work-hub.md) — battery, durability, and luck mechanics.
* [Fund Allocation](/fund-allocation.md) — where the profit-producing capital comes from.
* [Smart Contract Architecture](/smart-contracts.md) — the Revenue Vault in detail.


---

# 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.ananasverse.xyz/profit-model.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.
