Skip to main content
Before you deploy, you need to fill in four fields on the token creation form. These values define what your BEP-20 token is and how it behaves on BNB Chain. Take your time here — once your contract is deployed to the blockchain, these values are permanent.
All four fields are written directly into your smart contract at deployment time. They cannot be edited, updated, or corrected after the transaction is confirmed. Double-check everything before you click Deploy.

​
Fields

​
string
required
The full display name of your token. This is the name that appears in wallets, block explorers like BscScan, and most tracking interfaces.Requirements
  • Can include letters, numbers, and spaces
  • Keep it under 50 characters for the best display compatibility across wallets and explorers
  • Must not be blank
Examples
  • My Token
  • Rocket Finance
  • Golden Panda Coin
Best practice: Choose a name that clearly represents your project. Avoid names that closely mimic well-known tokens or projects, as this can create confusion and raise trust issues with your community.
​
string
required
The short ticker identifier for your token. This is the abbreviated label shown in trading interfaces, DEX listings, and wallet balances — similar to how BTC represents Bitcoin or BNB represents Binance Coin.Requirements
  • Typically 3–6 uppercase letters (e.g. MTK, GPANDA)
  • Numbers are technically allowed but uncommon
  • Must not be blank
Examples
  • MTK
  • RFI
  • GPANDA
Best practice: Search existing token lists and BscScan before settling on a symbol. Many symbols are already in use across BNB Chain. While duplicate symbols are technically possible on the blockchain, using a unique one avoids confusion for your community and anyone trying to find your token.
​
integer
required
The total number of tokens created at the moment your contract is deployed. All tokens in this supply are sent directly to your wallet immediately after deployment.Requirements
  • Must be a whole number (no decimals in this field)
  • Must be greater than zero
  • There is no maximum enforced by the form, but choose a realistic number for your project
Examples
  • 1000000 — one million tokens
  • 1000000000 — one billion tokens
  • 21000000 — twenty-one million tokens (common for projects that want to mirror Bitcoin’s supply model)
Best practice: Think carefully about your supply in relation to your project. A very large supply (e.g. trillions of tokens) combined with a low price per token is a common pattern, but there is no formula that works for every project. The total supply is fixed permanently at deployment — standard Teron contracts do not include any mint functions, so no additional tokens can be created after the contract is deployed.
​
integer
required
The number of decimal places your token supports. This determines the smallest unit of your token that can be transferred or traded.Requirements
  • Must be a whole number between 0 and 18
  • Defaults to 18, which is the BEP-20 standard
How it worksWith 18 decimals, one token is represented internally as 1,000,000,000,000,000,000 (10¹⁸) base units. This means your token can be divided into very small fractions, just like BNB itself. With 0 decimals, tokens can only be transferred as whole units.Best practice: Leave this at 18 unless you have a specific reason to change it. Most DEXs, wallets, and tools expect 18 decimals for BEP-20 tokens. Changing this value can cause display issues in wallets and compatibility problems with some trading platforms.
Before you deploy, search BscScan and a few DEX token lists for your chosen symbol. Picking a symbol that is already widely used by another project can cause genuine confusion — your community may end up looking at the wrong token.