It would be very easy to latch onto that for watching for received payments. There is no reliable way to do it that way and make sure nothing can slip through the cracks. Until we have solid example code using getreceivedbyaddress and getreceivedbylabel to point to and say “use this! use this! don’t use listtransactions!”, I don’t think we should implement listtransactions.
Can you be more specific about “no reliable way”?
The existing facility getreceivedby* is provably unreliable. It combines transactions into summarized totals. When you go to the bank ATM and perform two deposits, the second immediately following the first, you do not see “ATM deposit $80” on your bank statement, you see two transactions with different transaction IDs for “ATM deposit $40”.
I am missing something here? listtransaction seems more reliable than getreceivedby* summaries.