Well, here is a good example:
While noTxList=1, if you check the code,
(sorry for some reason this forum is blocking links to github??)
It is calling
this.node.getAddressSummary(address, options, function(err, summary)
It doesn’t look like any of the functions in that async waterfall really actually have any type of pagination capabilities.
I’m not too familiar how the DB streaming works, so I gave up to be honest. What we are doing is just adding a layer to blacklist most of these addresses to avoid the API from getting taken down too easily:
I can push that patch up to our fork if you are interested, but its an ugly, shameful work-around.