It’s been close to two years now since Tron (TRX) launched its mainnet, moving away from the Ethereum blockchain, where it first started as an open-source protocol for the global digital entertainment industry in September 2017.
Fast forward to eighteen months later, a Reddit user who has allegedly not been following developments with the TRON ecosystem is now stuck with TRX tokens held in an Ether wallet from Tron’s pre-mainnet days.
While the tokens are still available in the Ether wallet, it reportedly shows that the tokens are worth nothing despite how many units the user holds. Additionally, an attempt to load the tokens in popular Ether wallet service, MyEtherWallet as a custom token (using wallet address, TRX code, and decimal) shows the balance as zero.
Can the Lost TRX Be Recovered?
For the Reddit user and every other person still holding TRX from pre-mainnet days, there should always be a way to convert the tokens back to a valuable cryptocurrency.
For one thing, the Tron Foundation mentioned in its FAQs page before launching its mainnet that “there will be an exchange that supports TRX migration forever, so users who do not transfer TRX before the migration in June can wait for the regular migration after the completion of the forever-supportive exchange, without incurring losses.”
At this time, it appears that Binance is still one of those exchanges. At the time of listing the new token on the exchange, Binance confirmed that even after the TRX Mainnet comes online, the exchange will continue to support the ERC20 TRX token swap.
Users only have to deposit ERC20 TRX to their Ethereum address on Binance, and automatically, the tokens would be converted to TRON (TRX).
Meanwhile, the latest situation highlights the fact that the crypto industry is still at its infant stage, with many users still getting to the grip with the concept of managing their funds without the assistance of a third-party.
In a similar development, Coinfomania reported last month that a LocalBitcoins user lost $3400 on the platform despite enabling 2FA on his account.