Manage Token

To manage an existing token you need to connect the wallet that owns the token contract in Token Tool. After that, enter the token contract address. Alternatively you can also click on the token that you want to manage from the drop down list of token symbols and contract addresses that opens once you click the input field. Make sure that your wallet is connected to the same network as the one on which the token was created.

Token verification with custom contract name

Token verification is available on all supported mainnet and testnet networks except peaq network. Contracts created with Token Tool can be verified on multiple block explorers, you can see supported explorers in the verification process.

All tokens created with Token Tool will have Bitbond branding by default as the name of the contract file. For tokens created under DeFi Token or Security Token section, users can change the default name to their own custom file name for an extra fee upon creating the token.

To do that, when creating the DeFi Token and/or Security Token, simply enable the possibility to customize the token contract name by turning on the "Custom Contract Name" toggle. Then type the name you desire in PascalCase (e.g. MyTokenProject):

The customer contract name cannot be changed once token is created and deployed to the network.

Example of a verified token contract on the block explorer without a custom name:

Example of a verified token contract on the block explorer with a custom name:

The custom contract name verification will be complete once you complete the steps in the Verify Source Code section.

Verify source code of contracts

Source code verification is supported for DeFi Token contracts, Security Token contracts, NFT contracts, and Token Locker contracts.

Here is an example process for how you can complete verification for a DeFi token contract. The process is similar across other contracts, you should simply follow the same steps from their designated sections within Token Tool.

To verify token contract source code for a DeFi Token or Security Token, go to Manage Token and select your token or paste its contract address. Then click the Verify Source Code button:

Then select the block explorer on which you wish to have the contract verified. You can choose from supported explorers, and you can perform verification on more than just one block explorer:

Then click next and choose the type of verification you wish to complete. Please note that contract source code verification is possible in three different options:

1. Source code verification with Bitbond Branding

2. Source code verification Bitbond Branding removed

3. Source code verification with your own custom branding

Select the verification option you desire, agree on the terms, and then click "Submit". Confirm transaction in your wallet to pay fees and complete the verification. Once the transaction is complete, you will be able to see the source contract verified and publicly displayed on the block explorer.

Click the "View verified contract" to see your token contract on the explorer. Here is an example:

Here is how your token contract source code looks like on the block explorer with the default Bitbond branding:

Here is how your token's contract source code without any branding:

Here is how your token's contract source code with your own branding:

Token configuration

You can control the following parameters of your token. Please note that some of these parameters can only be changed, if the respective function was activated at the initial token creation:

• Mint (only possible if activated at creation)

• Burn (only possible if activated at creation)

• Change owner (always possible)

• Renounce ownership (always possible)

• Blacklist address (only possible if activated at creation)

• Pause (only possible if activated at creation)

• Transaction tax / fee (only possible if activated at creation). You can exclude addresses from being taxed by adding them to the exclusion list. Add the LP address to exclusion list for it to be traded on V3. Tax will not apply on transactions that take place on V3 DEXes.

• Deflation settings (only possible if activated at creation). Add the LP address to exclusion list for it to be traded on V3. Deflation will not apply on transactions that take place on V3 DEXes.

• Holders Reward/ Reflection Token (only possible if activated at creation) . You can prevent addresses from receiving holders rewards by adding them to the exclusion list. 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.

• Add a liquidity pool to a decentralized exchange. This feature may not work for tokens that have “Security Token Configuration” features activated.
• Edit asset documentation (only possible if activated at creation)

• Add or remove whitelisted addresses (only visible and possible if activated at creation)

• Change tokens per address limit (only possible if activated at creation) – note that you can only increase the limit but not decrease it in order to avoid creating a conflict with the amount of tokens that could be held per address prior to the change. This feature is also called "whale protection". You can exclude specific wallet addresses by adding them to the exclusion list. Once added to the exclusion list, the limit would not apply to these wallets. This can be useful when adding a liquidity pool to DEX. Note when creating a liquidity pool: make sure to fund it with an amount within the limit, you can then add the liquidity pool (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.

• Force transaction to move tokens from any wallet address to another address (only possible if activated at creation)

Manage Token is particularly useful if you want to execute corporate actions that have an impact on existing or to be newly minted tokens / shares.

View of Manage DeFi Token

View of Manage Security Token

Add liquidity pool to DEX

This feature enables you to easily submit and add a liquidity pool for your token on a decentralized exchange (DEX). Feel free to try it on testnets prior to proceeding with mainnet transactions.

Start by clicking the "Add liquidity pool to DEX" button under the Manage Token page. Then select the DEX of choice from the presented options by creating a new pool. If you already have an existing pool, you can choose top "Top Up" that LP after clicking the add liquidity button.

Note: If your token has holder rewards, burn fee or tax, it needs to be set to 0. After adding/topping up the liquidity pool (LP), modify it back to the desired rate. If your token has a max limit per holder / whale protection set up, ensure to add the initial LP within the limits, you can then add the LP contract address to the exclusion list under Manage Token and increase the liquidity as needed.

Next, insert the pair amount you wish to submit to the LP. After that, click "Approve" to allow the sending of the tokens and confirm the transaction in your wallet. Once completed, proceed with clicking "Submit", confirm the transaction in your wallet.

After the transaction is processed, your liquidity pool will be submitted to the selected DEX.

You can then return to this page to modify existing pool ratios for your LP by topping it up.

Add and Manage Liquidity for Tokens with Fees and Holder Limits

The Add Liquidity function on Token Tool is designed to simplify the process of submitting liquidity to decentralized exchanges (DEXs) like Uniswap or PancakeSwap. It acts as an intermediary, allowing you to add liquidity in a user-friendly way without needing to interact directly with the DEX platform.

Token Tool is not a DEX protocol. We do not have control over platforms like Uniswap or PancakeSwap. Our feature is solely meant to help you submit liquidity to these protocols more easily. This guide explains how to add and manage liquidity for tokens with fees (tax, deflation, holders reward) and/or a maximum limit per address.

1. Adding Liquidity for Tokens with Fees

• You can add liquidity even if token fees are enabled.

• If fees are not set to 0, they will be deducted when adding liquidity.

• Recommendation: Temporarily set fees to 0 when adding liquidity. This ensures the pool ratios remain correct.

2. Adding Initial Liquidity for Tokens with Max Limit per Address enabled

• Add liquidity using a token amount that is smaller or equal to the maximum limit per address.

• As long as the LP (Liquidity Pool) address is not excluded, tax will apply to any swaps involving that LP.

• Swapping in both directions (buy/sell) should work fine at this stage.

3. Excluding the LP Address

After liquidity is added, you can exclude the LP contract address to achieve the following:

1. Disable tax on transactions involving the LP (i.e. swaps).

2. Remove the max limit per address, allowing you to fund the LP with an amount greater than the limit.

When the LP address is excluded:

• Swapping: Swaps will continue to work.

• Tax: No fees will be charged on swap transactions involving the LP address.

• Max Limit: You can now add liquidity beyond the original max limit per address.

⚠️ Important: Once you finish funding the LP remove the LP address from the exclusion list to re-enable tax and max limit restrictions.

4. Fixing Pool Ratio Issues

If tax is applied or swaps occur during the initial LP setup, the pool ratios may get disrupted. This can cause issues, especially if slippage tolerance is low or set to 0.

To try and fix this issue:

1. Go directly to the DEX platform where the liquidity is added (Uniswap, PancakeSwap etc.).

2. Remove 100% of the liquidity from the pool.

3. Re-fund the LP with the correct amount of tokens.

4. While re-funding, exclude the LP address to temporarily disable tax and remove the max limit.

⚠️ Reminder: Once the LP is successfully funded, remove the LP address from the exclusion list to restore tax and max holder limit functionality.

Crucial Note on Pool Ratios:

• Correct Ratio at the Start: It is critical to submit the correct ratio of tokens when adding initial liquidity. If the wrong ratio is submitted initially, it cannot be fully fixed later.

• DEX Protocol Behavior: Even when you remove 100% of the liquidity, the DEX protocol retains a very small ratio of the token pair. This ensures that the ratio is maintained in case liquidity is added to the same token contract address in the future.

5. Finalizing the LP Setup

After re-funding the LP or adding tokens beyond the limit:

1. Remove the LP address from the exclusion list.

2. Swaps will now work, and taxes will apply as intended.

If a swap fails: Increase your slippage tolerance to account for adjusted pool ratios.

6. Adding Liquidity Beyond the Address Limit

To fund the LP with an amount greater than the max limit per address:

1. Exclude the LP address temporarily.

2. Add the desired amount of liquidity.

3. Once done, remove the LP address from the exclusion list.

⚠️ Note: While the LP address is excluded, tax will not apply, and the max limit restriction is bypassed.

By following these steps, you can seamlessly add and manage liquidity for tokens with fees and address limits while ensuring smooth swap functionality and proper tax enforcement.

Supported decentralied exchanges (DEXes):

• Ethereum: Uniswap V2, SushiSwap V2

• Avalanche: Trader Joe V1, Uniswap V2, SushiSwap V2

• Polygon PoS: Quickswap V2, Uniswap V2, ApeSwap, SushiSwap V2

• BNB Chain: PancakeSwap V2, Uniswap V2, ApeSwap, SushiSwap V2

• Fantom: SpookySwap V2, WigoSwap, SushiSwap V2

• Arbitrum: Camelot V2, Uniswap V2, Trader Joe V1, SushiSwap V2

• Optimism: Uniswap V2, SushiSwap V2

• Base: Uniswap V2, BaseSwap V2, SwapBased V2, SushiSwap V2

• Blast: BlasterSwap V2, Uniswap V2, SushiSwap V2