Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM@<div class="post">I'm proposing one small change to Bitcoin's JSON-RPC api:&nbsp; return a transaction ID when Bitcoins are successfully sent.<br/><br/>Why?&nbsp; Because I want to keep a complete audit trail for any coins going into or coming out of my application's wallet; I want to keep track of the particular transactions in the bitcoin network that correspond to actions my application takes.&nbsp; The alternative is to call sendtoaddress and then call listtransactions, but that won't work properly if two similar transactions (same amount to same address) occur at about the same time.<br/><br/>So I propose doing the simplest thing possible: modify the JSON-RPC sendtoaddress call so it returns the string 'sent:' followed by the 256-bit-hexadecimal transactions id.<br/><br/>This could break any applications that look for exactly the string 'sent' (which is what sendtoaddress does now).&nbsp; The fix would be to modify the apps to see if the string began with 'sent'.<br/><br/>Alternatives I thought about but think I don't like:<br/>&nbsp;+ make it a new api call so old apps do not break (sendtoaddress2 ? yuck)<br/>&nbsp;+ return just the transaction id on successful send instead of 'sent:...'<br/>&nbsp;+ return an array with more information (maybe [ "tx_id": "...", "fee" : 0.0 ] )<br/><br/>Comments/criticisms?<br/></div> text/html