> For the complete documentation index, see [llms.txt](https://docs.chestfi.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chestfi.cash/tools/token-creation.md).

# Token Creation

Deploy a new ERC-20 token on Robinhood Chain. No Solidity, no compiler, no deployment scripts — the factory contract handles it and the source is verified automatically.

* **Path:** Web App → **Token Creation**
* **Status:** Live
* **Fee:** `0.000615 ETH` + gas

### The form

#### Token Name *(required)*

The full, human-readable name of your token — for example, `ChestFi Token`. This appears in wallets, explorers, and DEX interfaces. There is no hard length limit, but keep it under \~32 characters so it renders cleanly everywhere.

#### Token Symbol *(required)*

The ticker, **2–6 characters**. Uppercase is strongly recommended: `CHEST`, `RHFI`, `USDX`.

Symbols are not unique on-chain — anyone can deploy a token called `USDC`. This is why users should always verify by **contract address**, never by symbol.

#### Decimals *(required)*

How many decimal places your token supports. Accepts **0–18**, defaults to **18**.

| Value | When to use                                                                           |
| ----- | ------------------------------------------------------------------------------------- |
| `18`  | The default and the correct answer for \~99% of tokens. Matches ETH and most ERC-20s. |
| `6`   | Occasionally used for stablecoins, mirroring USDC/USDT convention.                    |
| `0`   | Indivisible tokens — tickets, memberships, one-of-a-kind units.                       |

> ⚠️ Decimals are **immutable** after deployment. Choosing `0` when you meant `18` means holders can never send fractional amounts. If in doubt, use `18`.

#### Total Supply *(required)*

The number of whole tokens minted at deployment, in human units — enter `1000000` for one million tokens, not `1000000000000000000000000`. ChestFi applies the decimals for you.

The entire supply is minted to the **Owner Address** in the deployment transaction.

#### Owner Address *(required)*

The address that receives the full initial supply and becomes the owner of the token contract. This defaults to your connected wallet, but you can change it — for example, to send the supply directly to a multisig or a treasury.

> ⚠️ Double-check this field. Tokens sent to a wrong or non-existent address at deployment are unrecoverable.

### Live preview

The right-hand panel mirrors your inputs in real time — Name, Symbol, Decimals, Total Supply, Owner — so you can sanity-check the values before you spend anything. It costs nothing to look twice.

### Deploying

1. Fill in every required field. The preview updates as you type.
2. Click **Create Token**.
3. Your wallet opens with two things to confirm: the `0.000615 ETH` creation fee and the gas for the deployment.
4. Approve and wait for the block to confirm.
5. ChestFi returns your **contract address** and a link to the token page on Blockscout.

**Save the contract address immediately.** It is the only canonical identifier your token has.

### What you get

The deployed contract is a **standard, fixed-supply ERC-20**:

| Property          | Value                                       |
| ----------------- | ------------------------------------------- |
| Standard          | ERC-20                                      |
| Supply            | Fixed at deployment — **no mint function**  |
| Transfer tax      | None                                        |
| Rebasing          | No                                          |
| Blacklist / pause | None                                        |
| Verification      | Source verified automatically on Blockscout |

This matters. A fixed-supply, no-tax, no-blacklist contract is the kind auditors and holders want to see, and it's what makes the token safely compatible with the Token Locker and, later, Token Vesting.

### After deployment: a suggested checklist

1. **Verify on the explorer.** Open your contract on Blockscout and confirm name, symbol, decimals, and supply match what you intended.
2. **Add to your wallet.** Import by contract address so you can see the balance.
3. **Lock the team allocation.** Use the Token Locker and share the public proof link. This is the single most effective trust signal you can give a community at launch.
4. **Add liquidity.** Pair your token against ETH on a DEX deployed to Robinhood Chain.
5. **Lock the LP tokens.** Also via the Token Locker for now.

### Guidelines & common mistakes

* Symbol should be 2–6 characters; uppercase is recommended.
* Total Supply is the initial number of tokens to mint. There is no way to mint more later.
* Owner Address becomes the token contract owner and receives the entire supply.
* **Everything is immutable.** Name, symbol, decimals, and supply cannot be changed after the transaction confirms. If you typo the name, your only option is to deploy again and pay the fee again.
* Deploying a token creates an asset, not a market. Price, liquidity, and demand are entirely up to you.


---

# 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.chestfi.cash/tools/token-creation.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.
