> For the complete documentation index, see [llms.txt](https://docs.tezos-homebase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tezos-homebase.io/how-to-configure-your-dao-in-homebase/token-configuration.md).

# Token Configuration

**Contract Name** - what you're naming this contract. This is the name that will be seen in wallets and on DApps.

**Description** - what the token is used for

**Supply** - the total number of tokens you want to create. Plan carefully on this, because currently in Homebase even if you increase the supply, the total available in your DAO for proposal voting is not changeable.

**Decimals** - The number of decimals determines the smallest quantity of your token that can be transacted. For example, Bitcoin has 8 decimals and the smallest amount of bitcoin you can transact with is 0.00000001 BTC.

**Symbol** - The symbol for your token. For example, XTZ is used for Tezos and BTC is used for Bitcoin. It doesn't necessarily have to be a unique set of letters - after you deploy your token contract, you will have an address for it that is use in combination with the symbol.

**Icon** - The image for the token. You'll need to upload your image to an image storage site (or IPFS) and then post the link to the image in this field.

Next screen, **Initial Token Distribution -** the wallet address and amount of the intial token holders to receive tokens. 

**Review** - It's a good idea to take a screenshot of your token settings so you have them handy.

**Make sure to copy your token address on the success screen.**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tezos-homebase.io/how-to-configure-your-dao-in-homebase/token-configuration.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 `automate deployments from our CI pipeline` 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.