j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM¶<div class="post">I'll and add another reason not to have a "list transactions that happened after <txid>" :<br/><br/>move "transactions" don't have a transaction id, but they do affect account balances (and are listed in listtransactions).<br/><br/>Your code is going to get really messy if you expect to call listtransactions and then squirrel away the txid of the last item returned. If it was "category":"move", there WILL be no txid...<br/><br/>RE: eliminating polling: at some point fairly soon, I plan on cleaning up my "monitorreceived" patch, to POST to a URL when transactions come in or blocks are accepted... but I need to do some Deep Thinking to redesign based on lessons learned from 'accounts'. It might turn into a very minimal API, where the notification is "Hey, txid <123ae4221...> just got to N confirmations, you might want to call gettransaction and getbalance to get up-to-date."<br/></div> text/html
https://whatsonchain.com/tx/876db229152aef5000c30d9cf3fcf1c4703eb66fbc90ca2fff4dcb4526c3deb3