Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM¶<div class="post">I'll and add another reason not to have a "list transactions that happened after &lt;txid&gt;" :<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.&nbsp; If it was "category":"move",&nbsp; there WILL be no txid...<br/><br/>RE: eliminating polling:&nbsp; 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'.&nbsp; It might turn into a very minimal API, where the notification is "Hey, txid &lt;123ae4221...&gt; just got to N confirmations, you might want to call gettransaction and getbalance to get up-to-date."<br/></div> text/html