Coins on Polygon (MATIC) not automatically matched
closed
Eivind
Coin transactions on Polygon (MATIC) are not being automatically matched against their main-chain counterparts. This happens only on public wallet addresses. We map automatically on exchanges and when transactions are imported via the generic CoinTracker CSV format.
When tokens are not automatically mapped, users will see a question mark or a the first letter of the coin's symbol inside of a blue circle instead of the correct symbol for the coin.
One workaround for this is to edit the affected transactions in the public wallet and manually select the correct coin. Please see the following article on our help center for further details: https://help.cointracker.io/en/articles/5158413-why-are-my-transactions-showing-the-wrong-coin
If you have a very large number of transactions, you may want to use the CoinTracker generic CSV format to add the wallet instead of using the public address. The CSV import will allow the coins to be mapped automatically so you won't need to select them by manually. Once you obtain the CSV of your transactions, follow these instructions to create the import: https://support.cointracker.io/hc/en-us/articles/4413071299729
Log In
Sarah T. - CoinTracker
closed
Tokens should now be better matched against their main-chain counterparts, you can read more about supported and unsupported tokens here. CoinTracker now matches tokens based on the token contract address and not the symbol, you can read more about that here.
Users can remove and re-add their public address. CAUTION: This will delete any manual edits made on that wallet, we recommend filtering by your manual edit transactions using the Sync method: Manual filter in the transactions page and exporting those transactions via CSV for your records. Here is a guide on on how to export a filtered CSV. Users may need to re-apply those edits. When you re-add your wallet CoinTracker will either identify the token as the supported token or as an unsupported token should the token contract address not match the intended token.
If users have a handful of transactions with the wrong tokens mapped, they can edit the individual transactions using this guide. This only applies if the token is supported by CoinTracker.
If the reported behavior for this post still persists please reach out to the CoinTracker support team directly or re-submit this post with with updated details.
Sarah T. - CoinTracker
closed
Tokens should now be better matched against their main-chain counterparts, you can read more about supported and unsupported tokens here. CoinTracker now matches tokens based on the token contract address and not the symbol, you can read more about that here.
Users can remove and re-add their public address. CAUTION: This will delete any manual edits made on that wallet, we recommend filtering by your manual edit transactions using the Sync method: Manual filter in the transactions page and exporting those transactions via CSV for your records. Here is a guide on on how to export a filtered CSV. Users may need to re-apply those edits. When you re-add your wallet CoinTracker will either identify the token as the supported token or as an unsupported token should the token contract address not match the intended token.
If users have a handful of transactions with the wrong tokens mapped, they can edit the individual transactions using this guide. This only applies if the token is supported by CoinTracker.
If the reported behavior for this post still persists please reach out to the CoinTracker support team directly or re-submit this post with with updated details.
C
CT-7XRGWBNO
Kinda waiting on this fix to happen, my issue is it showing double the tokens that i have. its the only thing really holding me up from getting my taxes done. I've already went through and tried to fix it myself and screwed everything up worse. What happened to that 100m to better our experience.? Time is running out.!
C
CT-wXl8zMKX
Any update on when the integration will be finished?
C
CT-MQzMzg9q
Is there any progress being made on this? This makes this platform pretty much unusable for me
C
CT-MQzMzg9q
Also having the same issue. Here is a photo demo: https://coin-tracker-support-files.s3.amazonaws.com/dfb5ac05-8622-4cfa-95e4-ff65205312d7?AWSAccessKeyId=AKIAITYIG5VELYR73LHQ&Signature=zu88ezaA%2BT2XHawQWzlJ9yL2axg%3D&Expires=1669357114
C
CT-0qo1GwyX
I'm having this issue as well. The workaround of manually editing the tokens on the transactions does not solve the issue. After the next wallet sync, my USDC, USDT, and LINK tokens all revert back to an unknown token with no fiat value.
Additionally, the tokens that I was able to edit and retain their mappings show the correct fiat value on the transaction level. But on the wallet and portfolio level they are still counted as unknown tokens with no fiat value.
Would appreciate a fix for this, as I really can't justify paying for this product for the 2021 tax year without this functionality working.
Taylor-CoinTracker
Merged in a post:
WETH cost basis is 0 on Polygon/Matic Network
C
CT-kQE05Deq
First of all, huge thanks for implementing Polygon/Matic network. This is a huge quality of live improvement for me!
I did notice an issue with my WETH (0x7ceb23fd6bc0add59e62ac25578270cff1b9f619) mining payments from ethermine (0xc0899474fa0a2f650231befcd5c775c2d9ff04f1 ) on the Polygon/Matic network. The cost basis for these transactions shows as 0.
Eivind
Merged in a post:
Support Qi Dao Tokens
C
CT-7XRj66wX
Please support all tokens used on https://www.mai.finance on Polygon Network, such as QI, amWMATIC, camWMATIC, miMATIC, etc. I have noticed that as of today QI is not recognized.
Eivind
Merged in a post:
USDC not registering on Matic
C
CT-wXl8zMKX
On Matic/Polygon wallets, USDC reads as an unknown token rather than actual USDC
Henry - CoinTracker
Merged in a post:
Polygon/MATIC WETH Cost Basis
C
CT-ZX6YGK9Q
Deposits for WETH have a cost basis of 0.00 and as a result no income shows up for taxes. There is a mapping issue because the WETH icon shows up as a question mark. Manually editing transactions and selecting WETH fixes the issue and shows the correct cost basis and logo but this isn’t a solution for hundreds or thousands of transactions.
Load More
→