What is the issue?
When importing a native Robinhood CSV two tokens are created when there should only be one.
For example, for BTC - BTC and BITCOIN are both created.
For ETH - ETH and ETHEREUM are both created.
Image
Who is affected?
Users importing Robinhood CSVs that use the blockchain name in the network column.
What is the workaround?
Users can manually edit the CSV to replace the network column before importing.
For BITCOIN replace with BTC.
For ETHEREUM replace with ETH.
Keywords: Robinhood CSV import, BTC mislabeled, wrong token mapping, network column, balance discrepancy