You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if we have a Token with i.e. 2 decimals and we provide 4 decimals: 0.1234 we will cut off after the second decimal and ignore the other ones.
This can lead to unexpected behaviour. Currently the UI displays all decimals (in the table for instance) and does not show the cut-off decimals.
I think this should generate a warning in the code editor and display only the decimals which are going to be submitted in the table.
The text was updated successfully, but these errors were encountered:
Currently if we have a Token with i.e. 2 decimals and we provide 4 decimals: 0.1234 we will cut off after the second decimal and ignore the other ones.
This can lead to unexpected behaviour. Currently the UI displays all decimals (in the table for instance) and does not show the cut-off decimals.
I think this should generate a warning in the code editor and display only the decimals which are going to be submitted in the table.
The text was updated successfully, but these errors were encountered: