Wallet approval
No private key reaches SolCreate. Every fee, setup and HTS action is presented by the connected wallet.
SolCreate
Hedera mainnetNative HTS workflow40 HBAR / action
Hedera launch stack
Native HBAR and HTS token operations
Create Hedera Token Service assets, manage supply and account controls, then choose a supported Hedera DEX for wallet-confirmed liquidity.
Native Hedera workflow
One control room from HTS creation to HBAR liquidity
SolCreate uses Hedera-native transactions rather than disguising HTS actions as a generic EVM flow. Hedera WalletConnect keeps compatible wallets such as HashPack and Kabila as the approval layer, while Mirror Node reads and SaucerSwap pool data explain what will happen before signing.
The Hedera HBAR Token Creator and HTS Tools hub is the public overview for Native HBAR and HTS token operations: create a Hedera Token Service asset, review HBAR liquidity paths, manage supply keys, update metadata, handle account controls and prepare distribution from one launch map.
Use the overview before launch to decide which Hedera authority choices should remain active. A creator can keep supply authority for later minting, add freeze authority for explicit account controls, keep metadata authority for a future image or URI update, or avoid extra controls when a fixed launch record is the better fit.
The live tool routes keep each action separate for clearer public communication: creation returns the HTS token ID, liquidity routes document pool setup or LP withdrawal, mint and burn routes explain supply changes, metadata routes explain information updates, and multisender routes document recipient distribution.
Every state-changing tool has a fixed 40 HBAR SolCreate service fee. Hedera network fees, token auto-associations and any SaucerSwap pool-creation fee are separate and shown before the relevant approval.
01Create HTS TokenLaunch a native fungible HTS token with metadata and explicit authority choices.->02Add HBAR LiquidityCreate or add to a SaucerSwap V1 HBAR pool with live reserve context.->03Remove LiquidityExit 25, 50, 75 or 100 percent of a wallet-held V1 LP position.->04Mint MoreIncrease supply only when the connected account controls the supply key.->05Burn SupplyPermanently reduce supply through the active supply key.->06Update MetadataPin refreshed metadata and write the new URI through the metadata key.->07Freeze / UnfreezeApply account-level HTS controls only when a freeze key exists.->08MultisenderDistribute an HTS token to multiple associated Hedera accounts.->
Live network context
Token keys, balances, associations and transaction status are read from Hedera Mirror Node endpoints.
SaucerSwap V1
Fungible LP tokens make partial removal explicit and verifiable with clear 25/50/75/100 percent steps.
Hedera launch guide
Read the Hedera HTS launch checklist before using the live creator
Hedera route selection
Choose the right Hedera Token Service workflow before signing
A Hedera token launch usually has more than one step. The token creator creates the HTS asset, but launch teams may also need HBAR liquidity, token metadata updates, supply changes, account controls or holder distribution. SolCreate separates those workflows so builders can open the exact route that matches the next wallet action instead of mixing creation, minting, burn and liquidity intent on one page.
Creator route
Use the Hedera HTS token creator when the project still needs a new token ID, initial supply, metadata URI and explicit key decisions before any launch communication starts.
Open Hedera HTS creator ->Liquidity route
Use the HBAR liquidity tools after the token exists and the wallet is ready to review pair direction, pool context, LP custody and withdrawal planning separately from creation.
Plan HBAR liquidity ->Supply route
Use the mint or burn tools only when the connected account controls the required supply key and the team can explain why supply is changing after launch.
Review supply actions ->Distribution route
Use multisender after recipient account IDs, token associations and transfer amounts have been checked so the public holder record is easier to document.
Prepare HTS distribution ->HTS key planning
Authority choices that Hedera creators should document
Hedera Token Service keys are not cosmetic settings. They define which wallet can change supply, metadata or account-level controls after the token is live. Before a community launch, write down the reason for every active key and the public message that will explain it.
Supply key
Needed for later minting and some burn workflows. If a project keeps it active, publish a clear reason and avoid surprising the community with unexplained changes.
Freeze key
Enables account-level freeze and unfreeze actions. Keep it only when there is a real compliance, custody or recovery reason that users can understand.
Metadata key
Allows future token image, URI or project-information updates. Before launch, decide who controls updates and how changes will be announced.
Admin record
Document which wallet controls each action, which transaction was approved and which public token ID or pool record should be shared after completion.
Launch checklist
Practical checks before using the HBAR Token Creator
Use this Hedera creator overview as a staging page before the live tool. It keeps the phrase “Hedera HBAR Token Creator” clearly connected to practical launch preparation and helps visitors understand the difference between a native HTS token launch, a liquidity action and later supply administration.
- 01Confirm the token name, symbol, decimals, treasury account and initial supply before opening the live creator.
- 02Decide whether supply, freeze and metadata keys should remain active or be omitted for a simpler launch record.
- 03Prepare HBAR for SolCreate service fees, Hedera network fees, token associations and any separate liquidity action the wallet may need to approve.
- 04Share the final HTS token ID, metadata link, supply plan and liquidity context with the community after the transaction is confirmed.
HTS comparison guide
Hedera Token Creator vs docs, generators and explorer-only launch notes
A Hedera token launch is easier to defend when the team can explain why it used a native HTS token creator, which authority keys stayed active, how HBAR liquidity was prepared and which receipt proves each step. This section gives builders a practical comparison without replacing Hedera documentation or HashScan verification.
Official HTS documentation
Use Hedera docs when a team needs protocol-level details, SDK references or fee semantics. Use SolCreate when the immediate job is a guided wallet flow that turns those choices into a token ID, receipt trail and next-step launch record.
Generic EVM token generators
Generic ERC-20 generators usually frame the project as a Solidity contract deployment. The Hedera route keeps native HTS fields, treasury account choices, token associations and HBAR liquidity context visible instead of flattening them into an EVM checklist.
Explorer-only verification
HashScan is the public record after signing. SolCreate helps before that moment by separating creation, metadata, supply, freeze, distribution and liquidity decisions so the explorer link has a clean story behind it.
Receipt and evidence record
What to save after a Hedera HTS creator transaction
The best Hedera launch page is not just a button. It gives the builder a checklist for the public record after wallet approval, so later liquidity, metadata, mint, burn or distribution work can be tied back to the correct token ID and transaction.
- 01Save the HTS token ID, treasury account, decimals, initial supply and every active key immediately after creation.
- 02Pair the HashScan transaction with the exact SolCreate route used: creator, metadata, mint, burn, freeze, multisender, add liquidity or remove liquidity.
- 03Before adding HBAR liquidity, confirm token association readiness, pool direction, LP custody and whether later LP removal should use SaucerSwap or Pangolin context.
- 04For public launch notes, separate what happened on Hedera from what remains pending, such as metadata updates, multisender distribution or scanner review.
Hedera HTS FAQ
Creator, supply and verification questions
Is SolCreate creating an ERC-20 contract on Hedera?
No. The Hedera creator path is for native Hedera Token Service assets. EVM-style ERC-20 routes live on the EVM chains that SolCreate supports separately.
When should a project use mint or burn after creating an HTS token?
Use mint only when the supply key is intentionally active and the project can explain the new supply. Use burn when the treasury is permanently reducing token supply and the amount has been reviewed before signing.
Does the Hedera overview replace HashScan verification?
No. SolCreate prepares and separates the workflow before signing; HashScan remains the public place to inspect the confirmed transaction and token account record afterward.