API sync error for ETH on layer 2s
complete
P
Petur
complete
Hi,
This can happen if you created your wallet right after it was released. This was fixed very soon so all ETH (and most tokens) will now be recognized correctly.
I would actually recommend deleting and recreating any Optimism/Arbitrum wallet that has this issue since we have made a lot of improvements in the last few months. You could also fix this by only deleting the incorrect transactions and then resyncing the wallet, as described here:
https://help.koinly.io/en/articles/5951168-how-to-re-import-tokens-after-an-update
T
Tropical Sheep
Petur: Thanks for the reply. Ok yes, know I can resync. But I have to say this solution is unsustainable imho. The crypto space changes too fast, and there are always issues like this. I have found the same issue for WETH when syncing Optimism. I spent countless hours mapping and locking transaction between chains, in wallets, manually editing etc... Just erasing all this works that will necessarily need to be done again and that goes back up to one year in the past is not an option. I don't have the time and means to do this.
I have checked with Cointracker to see how they manage similar issue. They actually allow editing for API synced transaction.
So I am wondering what actually prevents you from implementing this solution. It is, fir the end user, the simplest and more effective way of fixing token errors and issues.
I would really like to have an answer to this question, as it may impact my decision to keep on going with Koinly in the future.
I love using your software, the support is pretty good, and I gor to really know how it works.
But if I have to resync a chain everytime there is an error like this - because I can't change tokens in API synced transactions - it seems to me like it might be a deal breaker.
It would be really great if you implemented this change.
Looking forward to your reply.
Thank you.
P
Petur
Tropical Sheep:
Hi,
Thank you for the feedback!
We will probably be making all transactions either fully or partially editable but this takes some planning.
If you have already fixed your transactions then there is no need to do any resyncing. The tokens will be synced correctly from now on so you shouldn't need to do this fixing any more.
Note that you can do the resync only for the affected transactions. You would do this by deleting all of the incorrectly imported transactions and then clicking on the 'REsync from the beginning' button. This would resync any missing transactions which in this case would just be the transactions that you deleted. The transactions would then be synced correctly which means that transfers and trades would be automatically handled and you wouldn't need to fix them manually :)
T
Tropical Sheep
Petur: I haven't corrected the transactions containing token errors yet. Being able to delete TXs and having those TXs resynced is already a better option than resyncing the whole blockchain / wallet. But it is still a tedious process, which asks for a close monitoring, whereas editing TXs allows the user to be in complete control of the process, which is much better and less time consuming.
I might try deleting and resyncing, while waiting for the better solution.