What is "utxocount" in "getwalletinfo" API?

+1 vote

Hi Team,
We have analysed the utxocount and have seen if utxocount is less, then TPS is higher.
Accordingly we have changed our use case where we are sending +1 qty Asset from Address 1 to Address 2 and then Address 2 to Address 3 and so on & we are again returning the same Asset to Address 1 after few iterations. So ideally in this scenario we should have 1 Unspent Tx for this entire loop as we are sending the same asset to every other Addresses.So our derivation is "utxocount" should be 1 for this entire transactions.
But we are observing utxocount is increasing just like txcount. After end of test with a span of 15-20 minutes sometimes utxocount is automatically decreased to a lower value or else we need to execute "combineunspent" API to reduce the same. So we are not getting this pattern

asked Dec 11, 2018 by adgupta

2 Answers

0 votes
Best answer

Every time you send an asset to a different address, some of it comes back to the original address in a "change output". So this is why the utxocount is increasing. If you just want to test maximum transaction throughput, try sending assets to the chain's burn address (burnaddress in getinfo response) instead.

answered Dec 12, 2018 by MultiChain
selected Dec 13, 2018 by adgupta
0 votes
The delay in combining the UTXOs might be due to the runtime parameters you've set, aka autocombinemininputs, autocombinedelay and autocombinesuspend
answered Dec 12, 2018 by SDVII
How to change this runtime parameter's default value as "setruntime" API does not work for them.Can I mention them during start of chain?
You can set them by stopping and running your chain like this example:
`multichaind chain1 -hideknownopdrops=1`

there are other says like adding them to multichain.conf file inside your node's folder.

you can see a full description here: https://www.multichain.com/developers/runtime-parameters/