Question about LCX 2.0 token migration in Koinly
complete
S
Square Gazelle
I have a question regarding the LCX token migration to LCX 2.0.
As you may know, the original Ethereum LCX token has been migrated to a new LCX 2.0 token contract on a 1:1 basis, with major exchanges such as Kraken and Coinbase supporting the migration. My Trezor wallet and my LCX exchange wallet both hold the migrated LCX 2.0 token, and after using Change Currency, Koinly displays the correct market value for my holdings.
However, when I click on the LCX asset in Koinly, it still shows the legacy LCX contract address rather than the new LCX 2.0 contract.
Could you please let me know whether this is intentional, in order to preserve the historical transaction and price history for LCX, or whether Koinly plans to update the asset metadata to reference the new LCX 2.0 contract in the future?
I was simply curious how Koinly handles token migrations such as this.
Thank you very much for your assistance.
Jack
updated the status to
complete
Thanks for reporting this - we updated the metadata (contract address) for LCX token to the new one.
Do mind that with a seamless migration like this, we just update the token instead of creating a new one - so old transactions with the token will show as if it had the new contract already.
Right now, transactions with both old and new contract will be importing as the same token (and contract being the new one).
I'm not sure how the on-chain migration happened (if it was an airdrop or you had to burn old tokens to claim new ones) - depending on what happened, you may need to make some adjustments to your transactions - see Token rebases and symbol swaps (AMPL, DOT, BTT) | Koinly Help Center
S
Square Gazelle
Jack Thank you very much for updating the LCX token metadata and contract address. I really appreciate you taking the time to investigate this and implement the update.
I’m sure this will also help other LCX holders following the migration to the new LCX 2.0 token.
Thank you also for explaining how Koinly handles token migrations. That was very helpful.