> For the complete documentation index, see [llms.txt](https://docs.kubchain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kubchain.com/quickstart/launching-a-token-on-kub.md).

# Launching a Token on KUB

When launching a token on KUB, you can choose between two standards: KAP-20 or ERC-20. This guide will help you decide which option suits your needs and provide a step-by-step process for deploying a KAP-20 token.

## Choosing Your Launch Path

### KAP-20

KAP-20 is the fungible token standard specific to KUB, based on the ERC-20 model but tailored with unique KUB features. Opt for KAP-20 if you require:

* **KUB Wallet Compatibility** - Utilize KYC-aware processes to seamlessly integrate KUB Wallet into your project.
* **Asset Recovery** - This feature allows the token's governance committee to reverse fraudulent transactions (e.g., following a legal directive), giving token developers control over recovery actions.
* **Ecosystem Alignment** - Tokens such as kKUB, kBTC, kETH, and others in the KUB ecosystem use the KAP-20 standard.

KAP-20 operates at the contract level: you’ll deploy the official version from [kub-chain/kub-contracts](https://www.npmjs.com/package/@kub-chain/contracts) and connect it to a shared set of contracts (including the KYC registry, AdminProjectRouter, and TransferRouter).

### ERC-20

The KUB network also supports ERC standard tokens. Use a standard [OpenZeppelin ERC-20](https://docs.openzeppelin.com/contracts/5.x/api/token/erc20) token if you need:

* **Consistency with Other EVM Chains** - Ensure your token functions identically to those deployed on different EVM networks.
* **No Admin Recovery or KYC Functions** - Keep your contract simpler without these additional complexities.
* **Minimal Constructor Surface** - Reduce the number of parameters required for deployment.

Deploying an ERC-20 token follows the same process as on any EVM chain: just adhere to the typical deployment guidelines with your OpenZeppelin contract.


---

# 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.kubchain.com/quickstart/launching-a-token-on-kub.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.