-
Notifications
You must be signed in to change notification settings - Fork 58
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
RPC interface seems to silently ignore too-large numbers #219
Comments
In the
It appears this bug will display odd/overflow behavior with any RPC command executed with the standard I would assume fixing the call to |
Ref: bitcoin/bitcoin#6765 |
This is fixed in the update from json_spirit to UniValue. Is the pull request but has not been fully tested yet. createrawtransaction and signrawtransaction especially need to be tested still. |
This looks fixed so I'm going to close it. The test numbers you see here are 31 signed bits filled and +1.
|
I'll try and test createrawtransaction and signrawtransaction soon |
I recently tried to list the unspent inputs in my wallet. Since there's no way I know of to ask for "all of them, mature or not", I typically ask for those with between 0 and 9999999999 confirmations, from any address, mature-or-not, like this:
... and that works. But this time I put too many 9's, and it returned an empty list:
It seems the extra 9 must have made the integer overflow, probably making it go negative, and so no outputs were found to match.
That's eleven 9's works, and twelve 9's doesn't.
Indeed, it's at 2^31 that the issue first happens:
The text was updated successfully, but these errors were encountered: