listaddresstransactions API issue with count and skip

Question

hi team,

Absolutely loving your product!! great job.

I think I might've found a bug (or I am not doing something correctly).

Situation: My node has 925,620 transactions for a particular address.

API: listaddresstransactions API with count and skip. All works well if I go chunk by chunk until I reach to the end. If I query listaddresstransactions 10 925615, instead of getting the very first 5 transactions (since the address is created), I am getting the first 10.

Seems like, to satisfy the count condition, the API is filling the gaps by going back in the loop.

If I increment in 100k chunks, I am getting 1mil transactions instead of 920k, because the last chunk is coming as 820-920k rather than as 900-920k.

Is there a way to know the total count, so that I can adjust the count in the last chunk?

Thanks in advance.

Regards,

Naveen.

Comments

Thanks for reporting this - we'll check this out and get back to you shortly.

Answer 1

We've confirmed this is a bug and will be fixed in the next release. In the meantime, we would recommend a workaround where you detect the duplicate transaction IDs at the application level.

Comments

Noted, thanks for the update. Appreciated.

Answer 2

Alpha 29, just released, should fix this issue.