-
Notifications
You must be signed in to change notification settings - Fork 259
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
Issues with floating point precision #70
Comments
Reading https://en.bitcoin.it/wiki/Proper_Money_Handling_(JSON-RPC) I wonder if I could fix this from the client library. but given the ouput difference from multichain above, I doubt it. |
In my experience, Multichain can't reliably handle more than 21 million coins, nor do you want to change the decimal place from Bitcoin's default. |
There's an issue with accuracy in JSON (and general double floating point) representations past 16 significant digits. Please try using a method which enables MultiChain to calculate the change itself – either using |
When sending high amounts of assets, multichain may reject transactions due to rounding errors in floating point calculation. I was trying to work around this by adding additional outputs that would correct the error, but internal calculations seem to add additional errors.
Steps to reproduce:
alpcointest
with assetalpcointest
(
issue <adminaddress> '{"name":"alpcointest","open":true}' 1 0.00000001
)132463363.16643485
coins to an address30000000
to another address using the above amount as input (I am using raw transactions)sendrawtransaction
fails withThe raw transaction is:
output of
decoderawtransaction
:The problem seems to be related to the conversion from raw and qty here:
The text was updated successfully, but these errors were encountered: