-
Notifications
You must be signed in to change notification settings - Fork 35.6k
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
getbalance and listaccounts returning incorrect balance (testnet) #6042
Comments
If there is a bug here, it's listunspent suggesting that UTXOs are associated with addresses or accounts: They are not. |
I think the bug here is reporting an account name for the listunspent Accounts are just bean counters. Their value is increased when a |
Thanks, I agree. So it's confirmed that the account system will be deprecated for 0.11 as discussed in #3816 ? Will JSON-RPC responses such as listunspent continue to return an account field during the deprecation phase or will they be removed immediately? |
@bitcartel Accounts will be replaced by labels, which are just a handle for an output script/address. At most the return field will be renamed at some point (not for 0.11 though). |
any suggestion for me, what balance i have ? ~/bitcoin-0.16.3/bin$ ./bitcoin-cli getwalletinfo
|
Problem: Testnet wallet account "elmo" is showing a balance of 1.02 but should instead show 0.01.
However when using
listunspent
to examine the UTXO in the wallet, there is only one UTXO assigned to the account "elmo" and this UTXO shows a balance of 0.01.Here are the two addresses associated with account "elmo"
Two separate block explorers report the balance of each address as:
http://tbtc.blockr.io/address/info/myZ2mEYZt1CyRPgdE6oXRbAJWbaaTtTwRi
https://www.blocktrail.com/tBTC/address/myZ2mEYZt1CyRPgdE6oXRbAJWbaaTtTwRi
0.01
http://tbtc.blockr.io/address/info/mkwLg4ARNWimVW1Bh9uxv9SKdfNnPHRHWr
https://www.blocktrail.com/tBTC/address/mkwLg4ARNWimVW1Bh9uxv9SKdfNnPHRHWr
0
So it appears that bitcoind is returning an incorrect balance of 1.02 instead of 0.01.
The text was updated successfully, but these errors were encountered: