Open mmbbee opened 1 year ago
Just a guess, it might have something to do with the wallet db not being vacuumed after rescan ?
I’ll look into this. Do you have any steps to reproduce? How many addresses are you watching? What are you using the watch endpoints for?
We are watching about 50k addresses.
The steps where we hit this were
unused
= false ( kick off rescan)/wallet/unspent
which throws the above error. Wallet reports the correct balance, siad is up, and other endpoints are happy, just not get unspentSimilarly, i have seen this a few times in local testnet during integration tests. In our integration tests, the beforeAll()
is to
remove=true
- remove all watched addressesremove=false, unused=true
- re-add all watched addresses but dont rescanIn the local testnet case, it is happening with < 100 addresses
Should also clarify these wallets only watch addresses. We don't use the wallet for any funds management, just tx tracking
After performing a wallet rescan on watched addresses, we can no longer call /wallet/unspent, getting the error
This is on version v1.5.9