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

# Smart Contract Architecture

The entire Ananasverse business logic runs on a minimum of **5–6 audited smart contracts**, each with a single responsibility.

## Contract overview

| # | Contract                            | Standard                | Role                          |
| - | ----------------------------------- | ----------------------- | ----------------------------- |
| 1 | Worker NFT Contract                 | ERC-721A                | Core NFT                      |
| 2 | Work Registry                       | —                       | Work Hub core                 |
| 3 | Profit Distribution / Revenue Vault | —                       | Distribution engine           |
| 4 | Treasury / Timelock                 | Multi-sig (Gnosis Safe) | Fund security                 |
| 5 | $ANANAS Token                       | ERC-20                  | Utility token                 |
| 6 | Airdrop & Governance                | —                       | Distribution / DAO (optional) |

## 1. Worker NFT Contract (ERC-721A)

The core NFT contract handling minting, metadata traits (whether an NFT is a President or a Worker tier 1–4), and transferability. Built on **ERC-721A** to minimize gas fees during mass minting.

Key responsibilities:

* Minting the 4,444 Worker NFTs across Team and Public phases.
* Storing and exposing the four stats (Hash Power, Battery, Durability, Luck).
* Transferability and royalty logic.

## 2. Work Registry

The place where holders assign their NFTs to a specific operation — Food & Beverage, Real Estate, or Transport & Logistics today, with more asset classes to come.

Key responsibilities:

* Records which NFT ID is working in which operation.
* Tracks each NFT's active Hash Power used in profit calculations.
* Drains Battery and Durability on every work cycle.

## 3. Profit Distribution / Revenue Vault

Receives profit deposits (tokens such as USDG or ETH) from real-world operations.

Key responsibilities:

* Calculates each holder's claim pro-rata based on active Hash Power per operation.
* Applies durability penalties when a worker is below 50%.
* Lets holders claim directly — no admin involvement.

## 4. Treasury / Timelock Management

Secures mint proceeds before they are allocated to real businesses or liquidity injection.

Key responsibilities:

* Holds all mint proceeds in a multi-sig (e.g. **Gnosis Safe**) with timelock.
* Executes allocation to the operating fund, liquidity pool, and reserve.
* Ensures liquidity can never be withdrawn unilaterally by a single admin.

## 5. $ANANAS Utility Token (ERC-20)

The internal ecosystem token used for bonus rewards on top of stablecoin payouts.

Key responsibilities:

* Distributed as utility rewards with each payout.
* Exchangeable on DEX / liquidity pools.
* Enables recharge and repair operations in the Work Hub.

## 6. Airdrop & Governance (Optional)

Planned additions:

* Automated $ANANAS airdrop module.
* DAO governance for community decisions on new asset classes and allocation changes.

## Design principles

* **Modular:** every contract has a single responsibility.
* **Audited:** contracts are reviewed before launch.
* **Transparent:** every payout and allocation is verifiable on-chain.
* **Upgradeable:** structured so the community always knows where funds sit and how payouts are calculated.

## Related

* [Security & Transparency](/security.md) — how the contracts protect funds.
* [Fund Allocation](/fund-allocation.md) — how the Treasury moves money.
* [Profit Model](/profit-model.md) — how the Revenue Vault computes payouts.


---

# 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/smart-contracts.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.