The current multiwallet design will attempt to sync the latest state of each active address. If any address is invalid, the entire update is aborted. Instead, we should log the failure and continue so the valid addresses may still be updated.
within BlockbookClient.GetTransactions which receives the slice of btcutil.Addresses:
[x] Instead of returning a nil response on error, it should log and continue when a failure occurs
[x] a partially satisfied response should always be returned in the case of an error or not
[x] Godoc should be updated to mention the new behavior indicating that an error condition does not mean a complete failure
The current multiwallet design will attempt to sync the latest state of each active address. If any address is invalid, the entire update is aborted. Instead, we should log the failure and continue so the valid addresses may still be updated.
within
BlockbookClient.GetTransactionswhich receives the slice ofbtcutil.Addresses: