> ## Documentation Index
> Fetch the complete documentation index at: https://docs.injective.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Token Standards

Injective provides a variety of different token standards one can use when creating a dApp. In this document, we will cover the different types of tokens, as well as recommendations and guidance for using each.

## Denom

A denom is how assets are represented within the Bank module of Injective. These assets can be used for trading, creating new markets on the exchange module, participating in auctions, transferring to another address, etc.

Depending on the origin of the denom and how it was created on Injective, we have different types of denoms:

| Denom type | Format | Origin |
| - | - | - |
| **Native** | `inj` | The native coin of Injective. Also the Injective EVM gas token |
| **Factory** | `factory/{creator}/{subdenom}` | Created permissionlessly via [TokenFactory](https://docs.injective.network/defi/tokens/token-factory.md) |
| **Peggy** | `peggy0x{ERC20_CONTRACT_ADDRESS}` | Bridged from Ethereum via the [Peggy bridge](https://docs.injective.network/developers-native/bridges/ethereum.md) |
| **IBC** | `ibc/{hash}` | Bridged from another IBC chain |
| **EVM** | `erc20:0x{CONTRACT_ADDRESS}` | Deployed directly on the Injective EVM against the [Bank precompile](https://docs.injective.network/developers-evm/bank-precompile.md) |
| **Insurance fund** | `share{id}` | Token shares of an insurance fund |

Each of the above has a registered bank denom, which is what the native exchange, auction, insurance and permissions
modules rely on as the single source of truth. Under the [MultiVM Token Standard](https://docs.injective.network/developers-evm/multivm-token-standard.md),
a denom with a registered token pair can also be called from the EVM. The [erc20 module](https://docs.injective.network/developers-evm/erc20-module.md)
maps the denom to an ERC20 contract address, and calls to that contract resolve through the
[Bank precompile](https://docs.injective.network/developers-evm/bank-precompile.md) to the same bank balance. EVM dApps interact with the paired
address as a standard ERC20. There is no second balance to bridge or reconcile.

> [!NOTE]
>
> CW20 assets are **not** native bank denoms. Their balances live in contract storage. An existing CW20 can be
> represented as a factory denom of the form `factory/{CW20_ADAPTER_CONTRACT}/{CW20_CONTRACT_ADDRESS}`
> through the [CW20 adapter](https://docs.injective.network/developers-cosmwasm/cw20-adapter.md), but CW20 is not recommended for new
> integrations and is planned for deprecation.

## Where to Go

> [card] [Launch a Token](https://docs.injective.network/developers-defi/token-launch.md)
>
> Create, set metadata, mint, pair across Injective EVM, list and launch a market.

> [card] [Token Factory](https://docs.injective.network/defi/tokens/token-factory.md)
>
> Native token minting facility on Injective.

> [card] [MultiVM Token Standard](https://docs.injective.network/developers-evm/multivm-token-standard.md)
>
> One balance across the native layer and the EVM.

> [card] [Token Metadata](https://docs.injective.network/developers/assets/token-metadata.md)
>
> How wallets and explorers read name, symbol and decimals.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.