Choose the right chain
Decide where the token should live. Token Factory supports Solana and selected EVM networks, and each network has its own fees, wallets and token standards.
STEP-BY-STEP / SELF-CUSTODIAL DEPLOYMENT
HOODBTC Token Factory helps you create a standard token from your own wallet without manually building the full deployment workflow. This guide explains what each stage means so you can make deliberate choices before signing the final blockchain transaction.
A token can be deployed quickly, but the choices can matter permanently. Prepare the name, symbol, supply model, decimals, metadata and authority settings before you sign.
Decide where the token should live. Token Factory supports Solana and selected EVM networks, and each network has its own fees, wallets and token standards.
Know the intended initial supply and how divisible the token should be before deployment. Do not enter random values just to continue.
Mint, freeze, ownership or other authority options can change who can control the token later. Review exactly what the selected network and form support.
The exact wallet prompts differ by blockchain, but the decision flow stays similar: choose the chain, configure the token, review control settings, sign and verify.
Use tokenfactory.hoodbtc.com. Confirm the domain before connecting a wallet or approving any transaction.
Choose Solana or a supported EVM network such as Ethereum, BNB Chain, Base, Arbitrum One, Polygon, Avalanche C-Chain or Optimism when available in the live product.
Select the wallet you want to use for deployment. Keep enough of the required network asset or supported payment asset available for blockchain costs and any applicable service fee shown by the live interface.
Choose the token name users will see and its short ticker or symbol. Check spelling and capitalization because changing token identity later may be difficult or impossible depending on the chain and metadata standard.
Enter the initial supply and supported decimal precision. Supply defines how many units are created initially; decimals determine how finely one token can be divided in wallets and applications.
Where supported, add a logo, description, website or social links. Use official project information and verify every URL before publishing it as token metadata.
Study each available authority option before deployment. If an option can mint more supply, freeze accounts, update metadata or control ownership, understand whether you want to retain, transfer or revoke that capability.
Confirm the network, token settings, costs and wallet address. Approve the requested transaction only if everything matches. After confirmation, use the provided transaction or explorer link to verify the token onchain.
Deployment creates the token contract or token asset on the selected blockchain. It does not automatically list the token on HOODBTC Trade, create a liquidity pool, guarantee a price, create buyers or make the token tradable everywhere.
These are the decisions most token creators should understand rather than treating them as simple form fields.
The readable project name and ticker shown by compatible wallets, explorers and applications.
The number of token units created at deployment, subject to the selected token standard and authority configuration.
Decimals control how small a fraction of one token can be represented. They do not increase the economic value of the token.
If supported and retained, mint authority can allow additional tokens to be created later. Revoking it can make future minting unavailable.
Some standards can include authorities that affect token accounts or administrative control. Availability and behavior vary by network.
Logo, description and project links help identify a token, but metadata does not prove legitimacy or create market value.
Record the official mint or contract address. This is more reliable than identifying a token only by name or ticker.
Use a compatible blockchain explorer to verify supply, token address, transaction and visible authority state.
Confirm logo and project links display as expected where supported.
Deployment alone does not decide how tokens should be distributed or managed.
A token needs a separate market or liquidity arrangement before users can trade it on a compatible venue.
Token distribution, fundraising, marketing and promises can create legal or regulatory obligations depending on jurisdiction and design.
Never publish a seed phrase, private key or recovery phrase. If a website, message or person asks for one, stop. Wallet approval is enough for legitimate Token Factory deployment flows.
No. The product is designed around wallet-based approval. Never enter your seed phrase or private key into the Token Factory or send it to anyone claiming to provide support.
A fixed-supply design generally requires choosing the intended initial supply and ensuring no authority remains that can create additional supply. The exact authority options and terminology vary by blockchain, so review the live settings before deployment.
No. HOODBTC Token Factory and HOODBTC Trade are separate products in the same ecosystem. Token creation does not automatically create a market, liquidity or listing on the trading product.
Blockchain deployment consumes network resources and requires transaction fees. The live interface can also show an applicable HOODBTC service fee separately where configured.
Some metadata or authority-controlled settings may be updateable, while other choices can be permanent. The answer depends on the selected network, token standard and the authorities retained or revoked at deployment.
Choose the network, configure the token, review every authority and approve deployment from your own wallet.