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

# Worker NFTs

Worker NFTs are the entry point to the Ananasverse ecosystem. Each of the **4,444** Cyberpineapple workers carries four stats that decide how much it earns and how often it needs upkeep.

## The four stats

| Stat           | Function                                                                                                                                                                            |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Hash Power** | Your worker's share of the profit pool. More Hash Power means a larger share of every payout.                                                                                       |
| **Battery**    | Depleted on every work cycle. At zero, the worker stops hashing until recharged.                                                                                                    |
| **Durability** | Wears down while assigned to an operation. Below 50%, it applies a hash penalty.                                                                                                    |
| **Luck**       | Rolls for extra rewards: critical rewards that double the cycle's $ANANAS, skipped battery/durability drain, or real-world perks such as discount vouchers from partner operations. |

## Rarity tiers

| Tier      | Rarity    | Supply | Hash Power | Battery | Durability | Luck |
| --------- | --------- | ------ | ---------- | ------- | ---------- | ---- |
| President | Unique    | 4      | 150        | 300     | 300        | 100  |
| Tier 4    | Legendary | 240    | 125        | 240     | 240        | 85   |
| Tier 3    | Rare      | 800    | 100        | 180     | 180        | 60   |
| Tier 2    | Uncommon  | 1,400  | 80         | 130     | 130        | 50   |
| Tier 1    | Common    | 2,000  | 50         | 80      | 80         | 30   |

Total supply: 4 + 240 + 800 + 1,400 + 2,000 = **4,444**.

## Why rarity matters

* **Hash Power sets income.** A President hashes 3× harder than a Tier 1 Common, so it earns a proportionally larger share of the operation's profit pool.
* **Battery and Durability decide running costs.** Higher stats mean longer work cycles before you need to spend $ANANAS on recharge or repair.
* **Luck rolls for bonuses.** Higher luck means more critical rewards and drain skips per cycle.

Rarity drives yield: a rarer worker earns more per cycle, which means more $ANANAS over time. The value of an NFT is driven by supply, demand, and rarity rather than any fixed pricing.

## The mint

* **Total supply:** 4,444 Worker NFTs (President + Worker tiers 1–4).
* **Team (200):** Reserved for the team, locked for 6 months after launch.
* **Public (4,244):** Open to everyone at launch. No whitelist.
* **Mint mechanics:** Built on **ERC-721A** to minimize gas fees during mass minting.

## After the mint

Mint proceeds are split according to the [Fund Allocation](/fund-allocation.md) framework. You assign your Worker NFT to an operation in the [Work Hub](/work-hub.md); the Work Registry starts draining Battery and Durability cycle by cycle, and when operations generate profit you claim your share through the [Revenue Vault](/smart-contracts.md).

## Transferability

Worker NFTs are transferable and include royalty logic on secondary trades. Ownership determines the right to earn; whoever holds the NFT controls its assignment and claims its payouts.

## Related

* [The Work Hub](/work-hub.md) — how assigning and upkeep work.
* [Profit Model](/profit-model.md) — how Hash Power translates to payouts.
* [$ANANAS Token](/ananas-token.md) — the token used for recharge, repair, and rewards.


---

# 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/worker-nfts.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.