> 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/readme.md).

# Introduction

Ananasverse is an on-chain profit-sharing ecosystem backed by **Stock Tokens** — tokenized real-world assets (RWA) on Robinhood Chain. Holders own a **Worker NFT**, assign it to an **asset pool** in the **Work Hub**, and earn a pro-rata share of that pool's actual profit.

This documentation explains every part of the ecosystem: how Worker NFTs work, how profit is calculated and distributed, which Stock Tokens the fund holds, how the money is secured on-chain, and where the project is headed.

***

## The core idea

Ananasverse connects NFT ownership to real asset income:

1. **Mint** a Worker NFT during the mint.
2. **Assign** it to an asset pool (for example, COINX, QQQX, or TSLAX) through the Work Registry contract.
3. **Earn** a pro-rata share of that pool's profit, paid in stablecoins (ETH/USDG) plus $ANANAS token rewards.

The fund that holds these Stock Tokens is capitalized from the NFT mint and managed under a clear allocation framework. All logic runs on audited smart contracts; every payout is verifiable on-chain. There are no guaranteed returns — payouts are whatever the underlying assets actually earn.

## How the model works

| Layer             | What it does                                                                     |
| ----------------- | -------------------------------------------------------------------------------- |
| **Worker NFT**    | ERC-721A asset with four stats: Hash Power, Battery, Durability, and Luck.       |
| **Work Hub**      | The interface where holders assign workers to live asset pools.                  |
| **Work Registry** | Records which NFT works in which pool and tracks active Hash Power.              |
| **Revenue Vault** | Receives pool profit and lets holders claim their share.                         |
| **Treasury**      | Multi-sig + timelock safe that secures mint proceeds.                            |
| **$ANANAS**       | ERC-20 utility token (1B fixed supply) used for recharges, repairs, and rewards. |

## The core loop

```
Mint Worker NFT → Assign to asset pool → Work Registry drains Battery & Durability
      → Pool generates profit → Revenue Vault distributes pro-rata
      → Claim ETH/USDG + $ANANAS → Recharge / Repair → Keep earning
```

## Navigation

* [Getting Started](/getting-started.md) — start here if you are new.
* [Worker NFTs](/worker-nfts.md) — stats, rarity tiers, and the mint.
* [The Work Hub](/work-hub.md) — assigning, battery, durability, and luck.
* [Profit Model](/profit-model.md) — the exact distribution formula.
* [RWA Portfolio](/rwa-portfolio.md) — the Stock Token portfolio.
* [Fund Allocation](/fund-allocation.md) — how mint proceeds are split.
* [Tokenomics & $ANANAS](/ananas-token.md) — supply, allocation, emissions, and the token sink.
* [Smart Contract Architecture](/smart-contracts.md) — technical deep dive.
* [Security & Transparency](/security.md) — how funds are protected.
* [Roadmap](/roadmap.md) — what comes next.
* [FAQ](/faq.md) — common questions.
* [Glossary](/glossary.md) — terminology.
* [Risk Disclaimer](/disclaimer.md) — important legal notice.

***

> **Please read the** [**Risk Disclaimer**](/disclaimer.md) **before participating.** Ananasverse does not promise or guarantee any return. Profit distributions depend entirely on the performance of the underlying assets (Stock Tokens).


---

# 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://docs.ananasverse.xyz/readme.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.