Skip to main content
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: 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, a denom with a registered token pair can also be called from the EVM. The erc20 module maps the denom to an ERC20 contract address, and calls to that contract resolve through the Bank precompile 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.
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, but CW20 is not recommended for new integrations and is planned for deprecation.

Where to Go

Launch a Token

Create, set metadata, mint, pair across Injective EVM, list and launch a market.

Token Factory

Native token minting facility on Injective.

MultiVM Token Standard

One balance across the native layer and the EVM.

Token Metadata

How wallets and explorers read name, symbol and decimals.
Last modified on October 26, 2026