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

# Getting Started

This guide walks you through the entire journey, from the mint to your first payout.

## 1. Mint a Worker NFT

The total supply is **4,444 Worker NFTs**, split into two phases:

| Phase  | Supply | Details                                                  |
| ------ | ------ | -------------------------------------------------------- |
| Team   | 200    | Reserved for the team. Locked for 6 months after launch. |
| Public | 4,244  | Remaining supply, open to everyone at launch.            |

There is **no whitelist** — minting opens directly to the public. No application round or registration is required.

Each Worker NFT carries four stats that decide how much it earns and how often it needs upkeep:

| Stat           | What it does                                                                             |
| -------------- | ---------------------------------------------------------------------------------------- |
| **Hash Power** | Sets the size of your share of an operation's profit pool.                               |
| **Battery**    | Drains on every work cycle. When it hits zero, the worker stops earning until recharged. |
| **Durability** | Wears down over time. Below 50%, it applies a hash penalty until repaired.               |
| **Luck**       | Rolls for extra rewards such as double $ANANAS, skipped drain, or real-world perks.      |

See [Worker NFTs](/worker-nfts.md) for the full rarity table.

## 2. Assign your worker to an operation

After minting, connect your Web3 wallet (MetaMask or OKX) and open the **Work Hub**.

1. Select a live operation — currently **Food & Beverage**, **Real Estate**, or **Transport & Logistics**.
2. Confirm the assignment on-chain through the **Work Registry** contract.
3. Your worker begins hashing and claims its share of the operation's profit every cycle.

There are **no lock-up periods**. You can move a worker between operations at any time.

## 3. Keep your worker running

* **Recharge Battery** with $ANANAS to keep the worker hashing.
* **Repair Durability** when it drops below 50% to remove the hash penalty.

Upkeep costs more for repairs than for recharges, so high-durability workers cost less to run over time.

## 4. Claim your profit

Every distribution cycle, the profit a live operation generated is deposited into the **Revenue Vault**. Your share is calculated from your active Hash Power, and you claim it directly — no admin involvement.

Payouts are made in **ETH/USDG** (stablecoin income) with **$ANANAS** utility rewards on top.

## What you need

* A Web3 wallet such as **MetaMask** or **OKX**.
* Funds for the mint price and for future recharges/repairs ($ANANAS).
* A Worker NFT to start earning.

## Next steps

* Understand the [Profit Model](/profit-model.md) to know exactly how payouts are computed.
* Explore the [RWA Portfolio](/rwa-portfolio.md) to see which businesses the fund operates.
* Read the [Risk Disclaimer](/disclaimer.md) before participating.


---

# 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/getting-started.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.