> ## Documentation Index > Fetch the complete documentation index at: https://docs.cosmos.network/llms.txt > Use this file to discover all available pages before exploring further. # Tokenfactory module > Create and administer factory denoms on the Cosmos Hub: creation fee, which admin capabilities the Hub enables, the commands, and how to secure the admin key. Commands on this page were run on gaia v28.3.1 (Cosmos SDK v0.53.4, CometBFT v0.38.23) on 2026-10-15 by agent testing on a local devnet. This page is for builders who want to issue a token on the Cosmos Hub and for operators who need to read `osmosis.tokenfactory.v1beta1` messages in blocks. It assumes `gaiad` is configured for the Hub and a funded key ([Delegator CLI guide](https://docs.cosmos.network/hub/latest/delegators/delegator-guide-cli.md#point-gaiad-at-the-hub)). At the end you have a denom named `factory//` that you can mint, burn, and hand over to a multisig or to governance. ## What the Hub runs The Hub uses [cosmos/tokenfactory](https://github.com/cosmos/tokenfactory), a fork of the Strangelove implementation with the sudo mint capability removed. Maintained by the Cosmos Hub team. No tagged releases; gaia v28.3.1 pins v0.53.5. Repository active. Checked 2026-10-15. Module documentation: [x/tokenfactory README](https://github.com/cosmos/tokenfactory/blob/main/x/tokenfactory/README.md). Any account can create a denom. The creator becomes its admin. The module is wired with two capabilities in `app/keepers/keepers.go`: * `EnableSetMetadata`: admins can set the bank denom metadata (symbol, exponent, description). * `EnableCommunityPoolFeeFunding`: the creation fee goes to the community pool rather than being burned. The `EnableBurnFrom` and `EnableForceTransfer` capabilities are not enabled. The CLI still has `burn-from` and `force-transfer` subcommands because they are part of the module. The Hub rejects those messages. An admin can therefore mint, mint to others, burn from its own balance, change the admin, and modify metadata. It can do nothing else. Smart contracts can use the same messages through the module's CosmWasm bindings. ## Parameters Creation fee: 10 ATOM, paid to the community pool. ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad q tokenfactory params --node https://cosmos-rpc.publicnode.com:443 ``` The output shows `denom_creation_fee: 10000000uatom` and `denom_creation_gas_consume: "2000000"`. Creating a denom also consumes 2,000,000 gas on top of the fee. The create transaction therefore needs `--gas` of at least about 2,200,000, or `--gas auto`. ## Create a denom ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad tx tokenfactory create-denom mytoken --from mykey \ --gas auto --gas-adjustment 1.5 --gas-prices 0.005uatom ``` The message is `MsgCreateDenom` with `subdenom: mytoken`. The resulting denom is `factory//mytoken`. Every later command and every transfer uses that denom. Confirm who created and who administers it: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad q tokenfactory denoms-from-creator $(gaiad keys show mykey -a) gaiad q tokenfactory denom-authority-metadata factory/cosmos1.../mytoken ``` The first lists the denom. The second returns `authority_metadata.admin` with the creator's address. ## Mint, burn, and metadata Mint to yourself or to another account, in base units: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad tx tokenfactory mint 1000000factory/cosmos1.../mytoken --from mykey --gas auto --gas-adjustment 1.5 --gas-prices 0.005uatom gaiad tx tokenfactory mint-to cosmos1RECIPIENT... 1000000factory/cosmos1.../mytoken --from mykey --gas auto --gas-adjustment 1.5 --gas-prices 0.005uatom ``` Burn from the admin's own balance only: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad tx tokenfactory burn 500000factory/cosmos1.../mytoken --from mykey --gas auto --gas-adjustment 1.5 --gas-prices 0.005uatom ``` Set the display metadata so wallets and explorers show a symbol and decimals. The arguments are denom, ticker symbol, description, and exponent: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad tx tokenfactory modify-metadata factory/cosmos1.../mytoken MYT "Example token" 6 --from mykey \ --gas auto --gas-adjustment 1.5 --gas-prices 0.005uatom gaiad q bank denom-metadata factory/cosmos1.../mytoken ``` The bank query returns the metadata with `symbol: MYT` and a denom unit with `exponent: 6`. The uatom entry on the Hub has the same shape (`symbol: ATOM`, exponent 6). ## Secure the admin key Even with burn-from and force-transfer disabled, a compromised admin key can mint without limit. It can also change the admin to lock you out. Three ways narrow that risk, from least to most restrictive: 1. Use a multisig as the admin. Create the denom from a multisig account ([multisig accounts](https://docs.cosmos.network/hub/latest/delegators/delegator-guide-cli.md#multisig-accounts)) or transfer it with `change-admin`. 2. Grant a limited operator through `authz`. An operator account can be allowed to execute only `MsgMint`, with an expiry: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad tx authz grant cosmos1OPERATOR... generic --msg-type /osmosis.tokenfactory.v1beta1.MsgMint \ --expiration 1800000000 --from mykey --gas auto --gas-adjustment 1.5 --gas-prices 0.005uatom ``` 3. Transfer admin to the governance module account. After that, every mint or metadata change needs a passed proposal: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad tx tokenfactory change-admin factory/cosmos1.../mytoken cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn --from mykey \ --gas auto --gas-adjustment 1.5 --gas-prices 0.005uatom ``` The `change-admin` command is immediate and has no undo. The new admin is the only account that can change it again. The query `gaiad q tokenfactory denoms-from-admin
` lists what an address administers. > [!WARNING] > > Check the destination with `gaiad keys parse
` before signing a `change-admin`. A `change-admin` to a mistyped address is permanent. Prefer moving admin to a multisig you have already tested with a small transfer. ## Verify ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad q bank total-supply-of factory/cosmos1.../mytoken --node https://cosmos-rpc.publicnode.com:443 gaiad q tokenfactory denoms-from-admin $(gaiad keys show mykey -a) --node https://cosmos-rpc.publicnode.com:443 ``` The supply matches what you minted minus what you burned. The admin listing shows the denom until you change its admin. After that, it moves to the new admin's listing. ## Next * [Modules on the Hub](https://docs.cosmos.network/hub/latest/modules/README.md) for the other modules and their parameters. * [Parameter change proposals](https://docs.cosmos.network/hub/latest/governance/proposal-types/param-change.md) to change the creation fee (`osmosis.tokenfactory.v1beta1.MsgUpdateParams`). * [Community pool spend](https://docs.cosmos.network/hub/latest/governance/proposal-types/community-pool-spend.md) for where the creation fees end up.