> For the complete documentation index, see [llms.txt](https://doc.pixotchi.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.pixotchi.tech/tokens/leaf-token.md).

# LEAF Token

### **Overview**

**LEAF** is the secondary in-game resource of Pixotchi.\
It is generated exclusively by staking $SEED and is designed to act as a **utility token** for long-term progression.

LEAF does not have an external liquidity pool and is not intended for speculative trading.\
It functions solely inside the Pixotchi ecosystem.

***

### **Generation**

Players can earn LEAF by staking their SEED tokens. There is:

* **No lock-up period**
* **Real-time accrual of rewards**
* **Free claiming and unstaking at any time**

Current approximate emission rate:

**\~3.33 LEAF per SEED per day**\
(Rate may vary dynamically based on total staked SEED and reward pool distributions.)

***

### **Utility**

LEAF is primarily used for **land progression**, including:

* Upgrading buildings
* Unlocking higher-level production
* Future utility within new land buildings
* Potential hybrid mechanics introduced in V2

In addition, LEAF can be swapped for SEED inside the **Marketplace building** on owned land.\
This is an in-ecosystem conversion and does not affect external exchanges.

***

### **Access Points**

LEAF staking and management are available via:

* **Pixotchi Mini App / Full App**
* **Staking Dashboard** (web version)

Both interfaces connect directly to the staking contracts.

***

### **Design Philosophy**

The LEAF system introduces a strategic layer to gameplay:

* Stakers gain long-term progression benefits
* Heavy land owners require sustained LEAF supply
* Player growth pace becomes closely tied to resource management
* The economy avoids runaway mint-and-print behavior

LEAF exists to complement SEED rather than replace it, forming a two-token system optimized for a sustainable onchain game loop.


---

# 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://doc.pixotchi.tech/tokens/leaf-token.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.