Max count of Assets in a node

Question

hello, is there any limitation in the max amount of assets in a node.I have tried to issue 20 thousand asset to an address, and when i look up the debug.log, there exists some problem.

belows are the records in debug.log:

2018-06-25 08:03:19 ERROR: CScriptCheck(): 06b2499a3129b5a62a5be9c644128464ad55998a2991cbad4d27522d08e9930b:
89 VerifySignature failed: Script is too big
2018-06-25 08:03:19 ERROR: CScriptCheck(): 06b2499a3129b5a62a5be9c644128464ad55998a2991cbad4d27522d08e9930b:
89 VerifySignature failed: Script is too big
2018-06-25 08:03:19 ERROR: AcceptToMemoryPool: : ConnectInputs failed 06b2499a3129b5a62a5be9c644128464ad55998a2991cbad4d27522d08e9930b

and now,it cost 1~5s to issue an asset, is there any method to improve 
multichain's performance?
thanks!

 

Answer 1

If you are issuing a large amount of assets to an address, or indeed sending a large number of transactions to that address, then your problem will be the large number of UTXOs (unspent transaction outputs) which belong to that address. This can lead to slow transaction building like you see.

You can confirm if this is a problem by examining the utxocount field of the output from getwalletinfo.

The solution is to combine UTXOs, either explicitly using the combineunspent API, or else using the autocombine* runtime parameters (which are configured for sensible behavior by default). But this is only possible if the address has send as well as receive permissions.

As for these errors you are seeing in the debug log, it would be helpful for us to know what API calls were being made (if any) at the timestamps shown for those errors. And please also confirm which version of MultiChain you are using.

Comments

thanks again
my multichain version is 1.0.2, and these errors occur when I use the issue call.I use this api by writing a program to keep issuing assets to an address.

---

OK, please update to MultiChain 1.0.5. If the problem persists with the latest version we will then get into the details of debugging it.