Bug: TokenAddress vs CSV upload race #113
Description
A user inserts a token with decimals 18 and then uploads a CSV. You know the parsing of the amount in the CSV depends on that decimal.
Imagine a user after uploading now changes the token address to a token with a smaller or decimal say 6 or 8, what happens to the CSV parsed or how can we go about this?
A possible solution:
When the user changes the token address, check if the previous and new decimal values are the same. If different, require that the user reupload the CSV before they can move to the next step