Hts Fungible Token

Overview

HTS represents fungible assets as native ledger entities with optional compliance controls beyond typical ERC-20 deployments. This skill encodes the procedural mapping between business roles (treasury, compliance, operations) and Hedera key fields documented under Token Properties.

When to use this skill

• Designing treasury + compliance separation via distinct keys.
• Choosing infinite vs finite supply (TokenSupplyType).
• Debugging association/KYC/freeze precedence issues before transfers succeed.

Prerequisites

• Funded operator account on intended network.
• Treasury account — defaults to operator in reference scripts; production uses cold treasury.

Workflow

1. Model roles → keys — See references/key-roles-taxonomy.md.

2. Create token — TokenCreateTransaction with name, symbol, decimals, initial supply, treasury, keys.

   await new TokenCreateTransaction()
     .setTokenName("Demo USD")
     .setTokenSymbol("DUSD")
     .setDecimals(8)
     .setInitialSupply(1_000_000)
     .setTreasuryAccountId(treasuryId)
     .setTokenType(TokenType.FungibleCommon)
     .setSupplyType(TokenSupplyType.Infinite)
     .setAdminKey(adminKey)
     .setSupplyKey(supplyKey)
     // ... optional compliance keys
   

   Reference: scripts/create-fungible-token.js.

3. Associate recipients — Accounts must opt-in via TokenAssociateTransaction before receiving tokens (unless auto-account patterns apply — verify docs).

4. Transfers — TransferTransaction.addTokenTransfer(tokenId, account, amount) with signed payer/treasury as required.

5. Compliance toggles — TokenGrantKycTransaction, TokenRevokeKycTransaction, TokenFreezeTransaction, TokenUnfreezeTransaction, TokenWipeTransaction, TokenPauseTransaction, TokenUnpauseTransaction.

6. Mint/burn — TokenMintTransaction, TokenBurnTransaction require supplyKey signatures.

Examples

Example 1

“Create an infinite-supply governance token with separate admin and supply keys.”

Provision distinct PrivateKeys, assign adminKey vs supplyKey, leave mint-only authority with multisig supply key if policy demands.

Example 2

“Investors must pass KYC before receiving allocations.”

Enable kycKey, default deny via documentation + off-chain checks, call grant KYC before first transfer.

Example 3

“Pause trading during an incident.”

Use pauseKey, document who may unpause; communicate regulatory expectations if investors are retail.

Troubleshooting

References

• Local: references/key-roles-taxonomy.md, references/compliance-config.md
• Docs: Define a token, Custom token fees