POOF Incorrectly Categorized as LOCK After Migration
complete
Sarah T. - CoinTracker
Users may experience:
- Incorrect categorization of assets due to the migration from POOF to LOCK. POOF is being categorized as LOCK.
Expected behavior:
- POOF should not be categorized as LOCK for transactions prior to the migration.
As a user, what should I do?
- Impacted users can edit the asset to reflect the correct one.
Additional Information
Please upvote this post to indicate that you are experiencing this behavior.
We have information on
bug reports
and what the status means in our help center
. For further assistance or inquiries regarding this bug you can contact the support team
.Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience!
Keywords: POOF, LOCK
Log In
Sarah T. - CoinTracker
complete
This has been corrected and POOF should no longer be recognized as LOCK.
Please
reach out to the CoinTracker support team directly
if you are still noticing the reported behavior.This post was marked as
being verified
This post was marked as
in progress
This post was marked as
confirmed
Sarah T. - CoinTracker
submitted