Watch Only Address Limit

+1 vote
Is there a limit to the number of watch-only address you can import into a wallet before you start to see a degradation in performance?

My projected user base is between 2 -> 5 thousand and I need to decide if it's worth the overhead of building out a DB cache of wallet transactions for the user application or just load all the addresses into a multichain wallet and use that for transaction history and asset balances.

If scalability on the wallet is not a concern then that is the most straight forward approach.
asked Jun 21, 2016 by marty

1 Answer

0 votes
We're currently in the process of rewriting the wallet for much greater scalability in terms of historical transaction volume, but not yet in a way specifically designed to handle a large number of addresses. The first alpha with that should be out in a month or so.

At that point the main scalability problem will be the number of UTXOs in the wallet, and it will start slowing down when there are tens of thousands. This is a possible scenario if you have many thousands of watch-only addresses - it depends on the way in which you are building transactions.

So my recommendation would be to wait for this new version, test how it performs in your usage scenario, and then decide how to proceed. None of the actual APIs will be affected so you can start working with the current version.
answered Jun 22, 2016 by MultiChain