getaddressbalances & getmultibalances ignore minconf parameter

+1 vote

It looks like both these api calls ignore the minconf parameter for setting the minimum confirmations for transactions to be included in the balance calculation.

This is causing a disconnect between in the responses for these and listunspent which does honour the minconf parameter.

 Can this be fixed?

asked Sep 6, 2017 by marty

3 Answers

0 votes
Best answer

Thanks for reporting this – it seems we can also reproduce the problem. The minconf parameter appears to work fine to distinguish between zero and more-than-zero confirmations, but all values larger than 1 appear to be treated as 1. We'll look into it and revert shortly with more information.

answered Sep 7, 2017 by MultiChain
selected Sep 8, 2017 by marty
Just to follow up, minconf is currently treated as boolean in the following APIs:


We'll fix this to treat it properly as a block count in MultiChain 1.0.1.
0 votes

Another thing to be aware of – if an address sends funds to itself, either directly or via a change output, then for the 'balance' APIs the received funds are considered as available immediately, independent of the minconf parameter. This is because, if for some reason the transaction is never confirmed, the funds will still be available to that same address. However this does not apply to the (lower level) listunspent API which shows individual UTXOs.

answered Sep 7, 2017 by MultiChain
0 votes
This should be fixed in MultiChain 1.0.1 released today.
answered Sep 13, 2017 by MultiChain
Thanks....that's great!