get_bulk_payments(json_encode(array('min_block_height'=>399206)));
When can we expect this function to work with only min_block_height parameter in the pre-built libraries?
That's not really on our radar; get_bulk_payments is for scanning payment IDs you already know. A general scan of the wallet would be using the incoming_transfers call.
I would like to make the application scalable, what is the best practice currently?
Getting transactions with incoming_transfers is fine, except the returned result will grow too large at some point? I guess with the parameter transfer_type "available" it won't be all that bad since most funds will be transferred elsewhere, but doesn't feel right to me. Also, is there any function to retrieve a payment_id with tx hash? without that this won't work anyways.
Polling get_bulk_payments with payment id's is fine too, except it will also grow too large at some point? As in, one may end up having to poll millions of payment ids. You could add the height parameter, but still, it just doesn't feel right having to run this through all payment_ids just to check for new transactions.
I'm thinking a simple
get tx's/payment id's > height = new transactions for script to process. Currently is seems to me I'll have to:
1. Record last checked height next to all payment ids in database.
2. Cron job traverse through all payment ids in database continuously checking for new tx's while also updating height
I must be missing something
