> For the complete documentation index, see [llms.txt](https://agarwoods-nft.gitbook.io/agarwoodsnft/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agarwoods-nft.gitbook.io/agarwoodsnft/readme.md).

# AGARWOOD NFT GAME WHITEPAPER

### Introduction

Ever wondered what it’s like to farm one of the world’s most valuable woods while earning rewards? That’s exactly what inspired me to create Agarwood NFT Game — a unique Web3 farming experience built on the WAX blockchain. Agarwood is known as *“liquid gold”* due to its rarity and high value, and I wanted to bring that same excitement into the NFT space. But this isn’t just another farming game — strategy, resource management, and economy play a huge role in success.

### Vision & Mission

**Vision:** To create a sustainable and rewarding NFT ecosystem that promotes long-term player engagement and economic balance.

**Mission:** To provide a fair and engaging farming experience where players are rewarded for their time and effort through the WAX blockchain, creating a balanced and thriving economy. Through the use of smart contracts and transparent tokenomics, we aim to foster trust and engagement within the community, ensuring the longevity of AGARWOOD.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://agarwoods-nft.gitbook.io/agarwoodsnft/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 `build a script that syncs our docs to a CMS` 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.