It happens occasionally, that specific ERC20 token at certain point in time migrates from Ethereum Blockchain, where it exists as an ERC20 token to own blockchain. This happened for example with TRON, BNB, ICON, VECHAIN and EOS in the past.
In such case you have to follow the transition advice of the specific token issuer.
TRON - https://tron.network/trx
BNB - https://community.binance.org/topic/44/binance-chain-mainnet-swap
ICON - https://medium.com/helloiconworld/the-token-swap-has-ended-33da57b302d0
VECHAIN - https://vechaininsider.com/guides/a-complete-guide-to-the-vechain-ven-to-vet-token-swap/
You have to be careful though not to mix up legacy ERC20 Tokens and own blockchain coins under same name!
You can not store native blockchain coin in ERC20 wallet and vice versa!
For example with TRON (TRX) you can distinguish the two by the format of the wallet address:
Legacy ERC20 TRON Address - 0x939a715B25308f56Ed17Fa60fC88556E77B83602 (Ethereum address format, as all ERC20 tokens reside on Ethereum blockchain/wallet)
TRON Blockchain Address - TF5ko6qZ7dQPaPNhNyurgL8RcYeB8MQXeh
Tokens that will be migrated to own blockchain will be removed from BC Vault GUI in some time (you can always add them back as a custom ERC20 token, should you wish so).
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article