Skip to main content

Most Used Commands

Create a new token with treasy and admin key set to alias Alice
Token associate

Full Command Reference

If you want to create a complex token with many keys, custom fees, and other options, take a look at the below guide for creating tokens from a specification file using the token create-from-file command.
Create a new fungible token with specified properties.
string
required
Token name.
string
required
Token symbol.
string
required
Treasury account: either an alias or treasury-id:treasury-key pair.
int
default:"0"
Decimals for the token. Default: 0.
int
Initial supply amount. Default: display units (with decimals applied). Append “t” for raw base units (e.g., “1000t”).
int
default:"INFINITE"
Set supply type: INFINITE (default) or FINITE.
int
Maximum supply of the token to bet set upon creation. This option is required if you set supply type to FINITE.
string
Admin key to be set for the token upon creation. If option not set then the operator key is passed as admin key.
string
Optional name to register for the token.
string(local|local_encrypted)
Key manager to use: local or local_encrypted (defaults to config setting).
string
Optional memo for the token (max 100 characters).
Create a new token from a JSON file definition with advanced features. See the full guide below.
Example: hcli token create-from-file --file ~/projects/token.json
string
required
Token definition file path (absolute or relative) to a JSON file.
string(local|local_encrypted)
Key manager to use: local or local_encrypted (defaults to config setting).
Associate a token with an account to enable transfers.
string
required
Token: either a token alias or token-id
string
required
Account: either an alias or account-id:account-key pair to associate with the token.
string(local|local_encrypted)
Key manager to use: local or local_encrypted (defaults to config setting).
Transfer a fungible token from one account to another.
string
required
Token: either a token alias or token-id.
string
required
Destination account: either an alias or account-id.
string
required
Source account: either a stored alias or account-id:private-key or account-id:key-type:private-key pair.
int
required
Amount to transfer. Default: display units (with decimals applied). Append “t” for raw base units (e.g., “100t”).
string(local|local_encrypted)
Key manager to use: local or local_encrypted (defaults to config setting).
List all tokens stored in state for the current network or a specified network.
Show token key information (admin, supply, wipe, etc.).
string
Filter tokens by network (defaults to current active network).

Guide: Token Create From File (Specification)

Create a token by defining its configuration in a JSON file. This is the recommended approach for repeatable token creation (scripts, CI, team handoffs), and it supports aliases for token keys so you don’t have to hardcode account keys everywhere.

What it does

token create-from-file reads a JSON file that matches a supported schema and creates a token on the selected network. You can define:
  • token metadata (name, symbol, decimals, memo)
  • supply model (finite/infinite, initial/max supply)
  • token keys (admin, supply, wipe, kyc, freeze, pause, feeSchedule)
  • optional token associations
  • optional custom fees

Quickstart

Create a token.json file and add a JSON specification. Here’s a basic example that both uses the full key format for the treasuryKey and the alias format for the adminKey.
You can create a toke from this specification by running the following command: hcli token create-from-file --file ./token.json

Full breakdown

Here’s a full breakdown of all the options you can use: