Bittensor (TAO) mapped to Fusatao Protocol (TAO) on Uphold
complete
C
CT-RqvA7W4O
Users may experience:
- Bittensor (TAO) mapped to Fusatao Protocol (TAO) on Uphold
- Users reported incorrect portfolio and wallet values due the incorrect token being tracked.
Expected behavior:
- Users should see the correct Bittensor (TAO) token upon import.
As a user, what should I do?
- Users can edit individual (TAO) transactions and replace the incorrect token with the correct asset. Instructions can be found in this support guide for correcting wrong coins. (Image 1)
How can users provide feedback?
You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to
Complete
once a fix is rolled out to all users. Up-voters will be notified of the status change.I need additional assistance, who can I contact?
For further assistance, please contact our support team directly.
Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience!
Keyword: Bittensor, TAO, Fusotao Protocol, coin-mapping, wrong token, Uphold
Log In
Sarah T. - CoinTracker
complete
This is now resolved, TAO is now being recognized on Uphold exchange. All transactions moving forward for TAO on Uphold will display as the correct token.
This fix was not applied retroactively, to see this applied to tokens prior to this update users can edit individual transactions and replace the incorrect token with the correct asset. Instructions can be found in
this support guide
for correcting wrong coins. If users have a large amount of incorrect transactions they can remove and re-add their exchange. ⚠️CAUTION
: This will delete any manual edits made on that exchange, 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 exchange, CoinTracker will identify the token as the correct token. If the reported behavior for this post still persists please
reach out to the CoinTracker support team directly
.This post was marked as
being verified
This post was marked as
in progress
Sam - CoinTracker
submitted