Create Token
Last updated
Last updated
To get started with asset tokenization via Token Tool connect your wallet and select the blockchain of your choice from the network dropdown at the top right. Once you have done that you can create your first token.
The create token page is split into two sections:
DeFi Token to create and deploy standard ERC20 tokens (and their equivalents on other EVM chains)
Security Token more relevant for issuers seeking to enable more centralized control over the tokenized assets
Using these functions you can define the following parameters and features for your token:
Both DeFi Token and Security Token have the following settings which are mandatory:
Token name: This is ideally a human readable name such as "USD Coin"
Symbol: The token symbol is comparable to its ticker symbol, typically four or more characters are used such as "USDC"
Initial supply: The amount of tokens that get minted at token creation. Note that you have to activate "Can mint" further below if you want to be able to increase the supply after token creation. The supply is usually determined by the desired token denomination (i.e. the nominal value per token). For a bond offering with a nominal amount of USD 10 million and a denomination of USD 100,000 the supply would have to be 100 tokens.
Decimals: Values can be 0-18, when 0 is used, the token is not divisible (security tokens for example usually are not divisible and will have 0 decimals)
All the following token features and configrations are optional, make sure you activate them only if required. It is not possible to deactivate them after initial creationg of the token once it's deployed to the network.
These features serve in importance for the life-cycle management of the token. Nevertheless, we recommend to activate only those features which are likely to be needed after initial token creation. Activating these features increases the cost of your token, see the Token Tool Pricing for detailed information.
The section below is to create ERC20 tokens following the most popular standards in the industry.
Set Custom Token Contract Name: sets a custom token contract name. The custom token contract name cannot be changed after the initial token creation.
Can burn: You can choose whether to allow token burning after initial token creation, which reduces the total supply of tokens.
Can mint: You can determine whether to enable additional token minting after the initial creation, which increases the total supply of tokens.
Can pause: You can decide whether to allow your token and related operations to be paused and resumed as needed. This can be useful in emergency situations, such as a security vulnerability or a malicious attack. However, be aware that enabling pausing grants centralized control to the token creator.
Can blacklist: You can specify whether to allow individual accounts, such as malicious actors, to be blacklisted after initial token creation. Note that even with whitelisting enabled, you can still blacklist an address that is on the whitelist. This is useful for preventing tokens from being transferred to addresses that are associated with fraudulent or harmful activities.
Set total supply cap: Sets the maximum total token supply limit for minting. Limit cannot be changed after the initial token creation.
Charge transaction tax / fee: You can choose to charge a fee on every token transfer. The fee will be sent to the specified tax/fee wallet, which by default is the connected token creator wallet. However, you can change the recipient to a different wallet, such as a marketing or charity wallet. The fee is specified in basis points (bps). A fee of 3.5%, for example, would be set to 350 bps. The fee recipient is excluded from the fee when they send tokens. The tax/fee setting can be modified after token creation under the Manage Token function or set to 0 to disable it. Enabling this feature may make your token incompatible for listing it on Uniswap V3. Add the LP address to exclusion list for it to be traded normally on V3. Tax will not apply on transactions that take place on V3 DEXes.
Burn fee for deflationary tokens: You can enable a burn fee to have a portion of every token transfer burnt, which will gradually reduce the total supply of tokens. The burn fee is specified in basis points (bps). A burn fee of 1.8%, for example, would be set to 180 bps. The burn fee setting can be modified after token creation under the Manage Token function or set to 0 to disable it. Enabling this feature may make your token incompatible for listing it on Uniswap V3. Add the LP address to exclusion list for it to be traded on V3. Burn fee will not apply on transactions that take place on V3 DEXes.
Apply Holder Rewards (Reflection Token): You can enable this feature to reward holders with passive income by automatically distributing a portion of a transaction based on their holdings. This incentivizes investors to hold tokens and potentially stabilizes the token price. Example: to apply a reward fee of 3.5%, enter the number 350. The reward rate is specified in basis points (bps) and it can be updated after creation. This feature is incompatible with "Can Burn", "Can Mint", and "Deflationary Token" features. Enabling this feature may make your token incompatible for listing it on Uniswap V3. Add the LP address to exclusion list for it to be traded on V3. Holders rewards will not apply on transactions that take place on V3 DEXes.
Change owner: The default owner is the address of the connected wallet. However, it is important to note that if you change the owner to an address that you do not control, you will not be able to make any further changes to the token after its creation.
Has document (ERC-1643): You can add the URL of an offering documentation such as a prospectus or whitepaper here. If you don't know what to put in here, you can leave this inactive.
Max number of tokens per address is limited (ERC-1594): You can set a maximum token balance per individual address. Limit can be increased after initial token creation but not decreased. Note: when creating a liquidity pool, make sure to fund it with the amount based on the limit set, you can then add the LP address to the exclusion list once the pool is created. Excluding the LP address from this limit will allow you to fund the pool with a higher amount than the limit set.
The section below is to create security tokens enabling regulatory compliance.
The following options are mainly relevant for compliance and regulatory reasons and make use of different security token standards from the ERC-1400 family. Note that you may not be able to create a liquidity pool on a DEX for tokens where some of these features are activated.
Can burn: Enables token burning after initial token creation to decrease supply
Can mint: Enables additional token minting after initial token creation to increase supply
Can pause: Specifies whether your token and all associated operations can be halted and resumed whenever needed. This can be useful in case of a vulnerability or a malicious attack. Be aware that enabling pausing gives central authority to the token creator.
Can blacklist: Specifies whether individual accounts such as malicious actors can be blacklisted after initial token creation. Note that if this function is enabled together with whitelisting, you can still black list an address that is on the whitelist. This is useful when an investor has been added to a sanction list and you have to prevent them from transferring the token further.
Charge transaction tax / fee: If activated, the fee will go to the specified tax / fee wallet as a portion of every transfer of the token. The default recipient of the tax / fee is the connected token creator wallet. The recipient can be changed to a different fee, marketing or charity wallet. The fee is specified in basis points (bps). If you want to charge a fee of 3.5% for example, you need to enter 350 bps. By default the fee recipient is excluded from the fee when sending tokens. The tax / fee setting can be changed after token creation under the Manage Token function or set to 0 to deactivate it. Enabling this feature may make your token incompatible for listing it on Uniswap V3.
Burn fee for deflationary token: If activated, the specified burn fee as a portion of every transfer of the token will be burnt. The burn fee is specified in basis points (bps). If you want to have 1.8% deflation / burn for each transfer for example, you need to enter 180 bps. The burn fee setting can be changed after token creation under the Manage Token function or set to 0 to deactivate it.
Change owner: The default owner is the address of the connected wallet. Note: if you change the owner to an address that you don’t control, you will not be able to make any changes to the token after its creation.
Has document (ERC-1643): Add the URL of an offering documentation such as a prospectus or whitepaper here. If you don't know what to put in here, you can leave this inactive.
Max number of tokens per address is limited (ERC-1594): Sets maximum token balance per individual address. Limit can be increased after initial token creation but not decreased.
Can be force transferred (ERC-1410): Regulates the permissions of the token issuer to enforce token transfers without approval or signature of the token holder. This feature be deactivated after initial token creation. Please note: This unrestricted transfer introduces a centralization risk and may lead to a potential misuse of the privilege. If there is a legitimate need for this functionality, make sure it is properly communicated to all users and token holders.
Requires whitelisting (ERC-1594): Defines if token transfers are only possible to whitelisted addresses or if the token is freely transferable. If you activate this, you can add and remove addresses to the whitelist under the Manage Token functionality. This feature is useful for security tokens where you need to know who holds your tokens. Note that you also need to whitelist your own creator address to be able to transfer tokens.
It takes approximately 10 seconds to create the tokens after you confirm. The initial token balance will be automatically transferred to the address of the creator/owner after the creation is successful.
The token is automatically deployed to the network and verified. Should the token verification not be completed automatically, you can go to Manage Token and click the "Verify" button that is shown at the top of the screen in such cases.
Please note: The owner address can distribute tokens without obtaining the consensus of the community. It is recommended that the team be transparent regarding the initial token distribution process. The token distribution plan should be published in a public location that the community can access. The team can lock up a portion of tokens, release them with a vesting schedule for long-term success, and deanonymize the project team with a third-party KYC provider to create greater accountability.
