-
Notifications
You must be signed in to change notification settings - Fork 570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Float-to-Integer conversion producing too many digits in Liquidity Pool exchange #3545
Comments
Yeah; doing so Math.round(parseFloat(minToReceive) * minToReceivePrecision) would solve this issue but not sure about other scenarios, will be implementing it now at dex.iobanker.com and please check the results. |
I don't exactly know where it went wrong, but it seems the input (E.G. the float
The result is clearly unexpected.
Created issue bitshares/bitsharesjs#99 and pull request bitshares/bitsharesjs#100. Wish it helps. |
FWIW rounding the input should work.
|
Describe the bug
Some decimal values with imprecise floating point representation are not converting correctly to integer values. Extra digits are produced, with result that a user might sell MORE of their asset than they intend to.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
BTWTY has a precision of 5, so the user would expect to be selling 13 units.
Encountered behavior
User is in fact selling 129999999998 units.
Screenshots
Desktop (please complete the following information):
Additional context
Problem may stem from not rounding the result from parseFloat in PoolExchangeModal.jsx, e.g. here:
bitshares-ui/app/components/Modal/PoolExchangeModal.jsx
Line 81 in 24c9e71
Case in point, in the Node.js REPL, the following can be observed:
Better may be to simply round the result:
An additional concern:
Although the result of parseFloat in the above example gives digits following the decimal point, it DOES place the decimal point in the correct location. The value passed in to ApplicationApi.liquidityPoolExchange() as the amountToSell parameter, gets passed along from there to TransactionBuilder as, presumably, a floating point value. Somehow or other TransactionBuilder is not detecting this and throwing an error as it should, nor truncating at the decimal point. Worse, it seems to be silently removing the decimal point and using all digits, including the sub-integral digits, to make the integer amount_to_sell value. This suggests a deeper problem in the TransactionBuilder functionality.
The text was updated successfully, but these errors were encountered: