factory/{creatorAddress}/{subdenom}. Because they are namespaced by creator address,
creation is permissionless and there are no name collisions to resolve.
TokenFactory tokens are bank denoms, which is what makes them the preferred token launch method on Injective. The exchange,
auction, insurance and permissions modules all interface natively with bank denoms, so a TokenFactory token can be
traded on the native orderbook, used as collateral, or gated by compliance rules with no adapter in
between.
Ready to launch?
Launch a Token is the step-by-step guide: create, set metadata, mint, pair for the EVM, list and
launch a market.
What Admin Control Gives You
The sender ofMsgCreateDenom is assigned as the denom’s admin. The message carries no admin field,
so the initial admin is always the creator. TokenFactory allows admin reassignment through
MsgChangeAdmin, and the authority itself is stored in the native module as part of the denom’s
authority metadata, not in contract code.
Admin authority exists to keep routine token operations out of governance. The admin mints, burns
where permitted, and updates name, symbol and decimals with a single message, effective immediately.
By contrast, peggy and IBC denoms have no admin. Their metadata is set automatically when the bridge
or transfer first creates them, and correcting it requires a governance proposal.
EVM originated denoms (erc20:0x...) follow a third model: authority lives in the token contract itself.
The bank precompile accepts setMetadata, mint and burn calls only from the paired contract, resolving
the denom from the calling address, so admin control is whatever the contract code grants, such as the
owner role of a MintBurnBankERC20. No TokenFactory admin record exists for these denoms and no
governance is required.
Unlike contract based tokens, total supply is tracked and queryable through the bank module directly,
with no contract call required.
What You Can Layer On Top
A TokenFactory denom is not visible to the EVM until you register an ERC20 pair. Until then,
MetaMask and Solidity contracts cannot see it. See
MultiVM Token Standard.
Choosing TokenFactory
Tokens bridged into Injective via Wormhole are also TokenFactory denoms.
Irreversible Choices
Three settings cannot be changed after the fact:decimals once nonzero, allow_admin_burn once
false or disabled, and metadata authority once the admin is renounced. The
Launch a Token guide covers each.
CW20 Adapter
TheCW20AdapterContract represents an existing CW20 asset as a TokenFactory denom of the form
factory/{CW20_ADAPTER_CONTRACT}/{CW20_CONTRACT_ADDRESS}. The adapter holds the CW20 tokens and mints
the factory denom; redeeming burns the denom and releases the CW20 back to the owner.
For conversion and redemption examples, see CW20 Adapter.
Reference
Launch a Token
End-to-end launch guide, from creation through market.
Module Specification
Messages, state, params and errors.
SDK Examples
TypeScript examples for every TokenFactory message.
Token Metadata
Metadata fields and how wallets read them.