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 we are not applying any limit on the minimum transferable AIN value.
When we transfer 1e-39 AIN for example, the balance changes 50.0948888888891 -> 149.90438888888912 for example, which means except the tx fee 0.1905 AIN, 0.00000000000002 (2e-14) AIN is subtracted from the sender's balance, and it's not the same as the transferred value 1e-39 AIN.
Updates:
As the total supply is 0.7 billion (700,000,000) AIN, the integer parts consumes 9 digits. So only 6 (= 15 - 9) digits are available for non-integer values. So 10^{-6} would be safe.
Currently we are not applying any limit on the minimum transferable AIN value.
When we transfer 1e-39 AIN for example, the balance changes 50.0948888888891 -> 149.90438888888912 for example, which means except the tx fee 0.1905 AIN, 0.00000000000002 (2e-14) AIN is subtracted from the sender's balance, and it's not the same as the transferred value 1e-39 AIN.
This happens because of the 52 bits limit of the mantissa:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number
So, we need to apply a limit to the minimum transferable AIN value.
As 2^52 ~= 4.5 x 10^{15}, some value around 10^{-14} would be safe.
The text was updated successfully, but these errors were encountered: