Skip to main content
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:
  • Native denom - inj, the native coin of Injective, which is also the EVM gas token.
  • Factory denoms - factory/{creator}/{subdenom}, created permissionlessly through TokenFactory.
  • Peggy denoms - peggy0x{ERC20_CONTRACT_ADDRESS}, bridged from Ethereum via the Peggy bridge.
  • IBC denoms - ibc/{hash}, bridged from another IBC chain.
  • EVM denoms - erc20:0x{CONTRACT_ADDRESS}, deployed directly on the Injective EVM against the Bank precompile.
  • Insurance fund denoms - share{id}, token shares of an insurance fund.
A CW20 asset is not a bank denom, since its balances live in contract storage. It can be represented as factory/{CW20_ADAPTER_CONTRACT}/{CW20_CONTRACT_ADDRESS} through the CW20 adapter, which is not recommended for new integrations. See Token Standards for the same taxonomy with links, and MultiVM Token Standard for how a single denom is reachable from both the native layer and the EVM.

​
Token

Token is simply a denom on the Injective chain with some meta information. The metadata includes information like symbol, name, decimals, logo for the particular denom, etc. The metadata of the denom is quite important for a dApp developer as information on the chain is stored in its raw form (for example 1inj on the chain is represented as 1*10^18inj) so we need to have a way to show the user human-readable information (numbers, logo, symbol, etc).
Deprecation NoticeNote that there was a “Denom Client” available within the Injective SDK. This has been deprecated in favour of Injective List.
Last modified on October 26, 2026