Token Metadata - Injective Docs

Token metadata (name, symbol, decimals) controls how your token appears across two systems:

System	What reads it	How it’s set
On-chain (bank module)	MetaMask, Blockscout, Solidity contracts calling `symbol()` / `name()` / `decimals()`, any EVM tool	Depends on denom type (see below)
Off-chain (injective-lists)	Injective-native frontends (Hub, Explorer, trading dApps built with the TypeScript SDK)	Submit a PR to injective-lists

Both are needed for a complete integration. On-chain metadata ensures EVM compatibility; off-chain metadata ensures display in Injective dApps.

Setting On-Chain Metadata

How you set bank module metadata depends on your denom type:

TokenFactory (factory/...)
Peggy (peggy0x...)
IBC (ibc/...)
ERC20 (erc20:0x...)

The denom admin can set metadata directly using MsgSetDenomMetadata:

injectived tx tokenfactory set-denom-metadata metadata.json \
  --from=ADMIN_KEY \
  --chain-id=injective-888 \
  --node=https://testnet.sentry.tm.injective.network:443 \
  --gas=auto --gas-adjustment=1.5 --gas-prices=160000000inj \
  --yes

Where metadata.json:

{
  "base": "factory/YOUR_ADDRESS/MYTOKEN",
  "name": "My Token",
  "symbol": "MYTOKEN",
  "display": "MYTOKEN",
  "description": "Description of your token",
  "decimals": 18,
  "denom_units": [
    { "denom": "factory/YOUR_ADDRESS/MYTOKEN", "exponent": 0, "aliases": [] },
    { "denom": "MYTOKEN", "exponent": 18, "aliases": [] }
  ]
}

Once set, the MTS ERC20 contract will immediately return the correct values for name(), symbol(), and decimals().See TokenFactory examples for TypeScript SDK usage.

Peggy-bridged tokens do not inherit metadata from Ethereum. The Peggy bridge creates the denom but does not set name, symbol, or decimals.To set metadata for a Peggy denom, you need a governance proposal. This is because Peggy denoms have no admin authority - only the governance module can write to the bank module’s metadata store for these denoms.Submit a proposal with MsgSetDenomMetadata where the sender is the governance module account:

{
  "messages": [
    {
      "@type": "/injective.tokenfactory.v1beta1.MsgSetDenomMetadata",
      "sender": "inj10d07y265gmmuvt4z0w9aw880jnsr700jstypyt",
      "metadata": {
        "base": "peggy0xYOUR_TOKEN_ADDRESS",
        "name": "Your Token Name",
        "symbol": "SYMBOL",
        "display": "SYMBOL",
        "description": "Your token description",
        "decimals": 18,
        "denom_units": [
          { "denom": "peggy0xYOUR_TOKEN_ADDRESS", "exponent": 0, "aliases": [] },
          { "denom": "SYMBOL", "exponent": 18, "aliases": [] }
        ]
      }
    }
  ],
  "metadata": "",
  "deposit": "100000000000000000000inj",
  "title": "Set TOKEN metadata",
  "summary": "Set bank denom metadata for peggy0xYOUR_TOKEN_ADDRESS so the MTS ERC20 returns correct name, symbol, and decimals.",
  "expedited": true
}

Submit with:

injectived tx gov submit-proposal proposal.json \
  --from=YOUR_KEY \
  --keyring-backend=file \
  --chain-id=injective-888 \
  --node=https://testnet.sentry.tm.injective.network:443 \
  --gas=auto --gas-adjustment=1.5 --gas-prices=160000000inj \
  --yes

Once the proposal passes, the MTS ERC20 contract will immediately return the correct metadata - no redeployment needed.

Testnet proposals: Use a deposit slightly below min_deposit so it doesn’t enter voting immediately. After submitting, reach out to the team on Discord or the Developer Telegram to coordinate validator votes. See the testnet proposals guide for details.

If you create an MTS token pair before setting metadata, the ERC20 contract will return blank name, blank symbol, and 0 decimals. MetaMask will not display the token correctly, and Blockscout will not index it by name. Set metadata before or after creating the pair - the ERC20 reads from the bank module on every call.

See the ACME bridge example for a complete walkthrough including the governance proposal template.

Same as Peggy denoms - IBC denoms have no admin authority. Metadata must be set via a governance proposal using the same MsgSetDenomMetadata pattern shown in the Peggy tab.Replace the base and denom_units[0].denom with your IBC denom (e.g., ibc/2CBC2EA121AE42563B08028B51D50FB7B0DABBEE2F1E37C98EBB4347B7BE8FBC).

For tokens deployed natively on Injective’s EVM (not bridged), the token deployer can set metadata via the bank precompile’s setMetadata function:

// Call from the same account that deployed the ERC20
IBankModule(0x0000000000000000000000000000000000000064).setMetadata(
    tokenAddress,
    "Token Name",
    "SYMBOL",
    18
);

This writes directly to the bank module. Only works for erc20: denoms - the precompile rejects other denom types.

Frontend Metadata (injective-lists)

For display in Injective-native dApps (Hub, Explorer, trading interfaces built with @injectivelabs/sdk-ts), submit your token to the injective-lists repository. This is separate from on-chain metadata. Injective-lists controls display in Injective frontends, while bank module metadata controls what EVM tools (MetaMask, Blockscout, Solidity) see. Follow the contributing guide to submit a PR with your token’s metadata.

If your token is missing from injective-lists, TokenFactoryStatic will return undefined for that denom. See the injective-lists integration guide for setup.

​Setting On-Chain Metadata

​Frontend Metadata (injective-lists)

Setting On-Chain Metadata

Frontend Metadata (injective-lists)