RPC listtransactions should include transaction IDs in output #242

1. 
   mikegogulski commented at 2:32 am on May 19, 2011: none

   Right now we get: account, category, time, amount, otheraccount, comment.

   Why don’t we get a txid?

2. 
   gavinandresen commented at 3:21 am on May 19, 2011: contributor

   send/receive/generated do have txids; you mean for “move” transactions? Because there is no txid for move transactions, they’re internal to the wallet. I suppose bitcoin could generate one for moves, but it is not immediately obvious how. What do you need it for? moves always come in pairs; I assume both entries in the pair should have the same txid. And I assume you’d want gettransaction <txid_for_move> to work?
3. 
   mikegogulski commented at 1:28 pm on May 19, 2011: none

   You’re right, I was looking at a move, so a txid wouldn’t apply. Non-issue, closed :)
4. mikegogulski closed this on May 19, 2011

   ---

5. 
   AEtherSurfer commented at 6:38 pm on October 24, 2011: none

   I need this to reconcile “listtransactions” with an external db, also would be helfpul to detect if i need to go back farther than the last ten txes for synchronization

   I would be content if the txid was merely the direction(eg receive, send) combined with the timestamp

6. 
   freewil commented at 6:53 pm on October 24, 2011: contributor

   @DataSurfer: try upgrading your client and you shall find what you’re looking for :)

   https://en.bitcoin.it/w/index.php?title=Original_Bitcoin_client/API_calls_list

7. ptschip referenced this in commit 3aeb2a8da6 on Jan 14, 2017
8. attilaaf referenced this in commit 72cf5fe89b on Jan 13, 2020
9. cryptapus referenced this in commit 9c191e33ab on May 3, 2021
10. DrahtBot locked this on Sep 8, 2021

Contributors
mikegogulski gavinandresen AEtherSurfer freewil