Skip to main content

Custom Tokens in TronLink: What You Need to Know

TRONSCAN Support
  • Updated

With the feature of custom tokens, users can manually add contracts not recorded as tokens on TRONSCAN as custom tokens in TronLink wallet, and this is to help users search and manage their token assets.

Some contracts might not be recorded directly on TRONSCAN because certain ABI functions and parameters in the contract code are not identified. When these token contracts are added as custom tokens on TronLink, you may not be able to access certain features. For more details:

 

I. Only contracts including the following parameters can be added as custom tokens on TronLink:

For TRC-20 tokens: The contract must include the balanceOf function and the Transfer event.

For TRC-721 tokens: The contract must include the ownerOf function and the Transfer event.

Contract addresses without the variables above can not be added as custom tokens.

 

II. If these variables are not detected in the contract address, certain token features will be missing

If the following variables in the contract address are not identified, certain features will be missing after the contract is added as a custom token.

  1. total supply function
  • If it is not detected, the token's total supply won't be shown on the project overview page.
  1. allowance function
  • If it is not detected, the approved spending cap for this token may not be accessible.
  1. transfer function
  • If it is not detected, you may not be able to transfer the token directly.
  1. approve function
    • If it is not detected, the following issues may exist: 
    1. The approval operation for this token may not be available.
    2. The token cannot be traded within other smart contracts (including, but not limited to, swap contracts).
  1. transferFrom function
  • If it is not detected, you may not be able to directly transfer collectibles under the token contract.
  1. Approval event
  • If it is not detected, the remaining spending allowance of the token may not be accessible.
  1. name variable
  • If it is not detected, please enter the token name manually; otherwise it may not be displayed.
  1. symbol variable
  • If it is not detected, please enter the symbol manually when adding the token.
  1. decimals variable
  • If it is not detected, the token precision will be set to 0 by default.

 

III. FAQs

  1. After I add a custom token, how can I tell which features are missing?
  • If there are missing features due to variables above not detected, a warning tab of the missing features will be displayed on the token details page (TronLink Extension) or the project overview page (TronLink App). You may visit these pages for details.
  1. Is adding a custom token on TronLink the same as recording a token on TRONSCAN?
  • No. A custom token added on TronLink is only valid at the current address, and the contract on TRONSCAN is not a token at this time. Other addresses that haven't added the contract as a custom token cannot identify the contract as a token. Therefore, after this contract is improved and recorded as a token on TRONSCAN, it can then be circulated and traded.
  1. After adding the contract address as a custom token on TronLink, can I still record the contract as a token on TRONSCAN?
  • Yes. In this case, the token details page on TronLink will remind the user whether to update the information of the token. If the user confirms such an update, information of the token recorded on TRONSCAN will replace that of the current custom token.

Related articles