Right now we get: account, category, time, amount, otheraccount, comment.
Why don't we get a txid?
RPC listtransactions should include transaction IDs in output #242
issue mikegogulski opened this issue on May 19, 2011-
mikegogulski commented at 2:32 AM on May 19, 2011: none
-
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?
-
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 :)
- mikegogulski closed this on May 19, 2011
-
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
-
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
- ptschip referenced this in commit 3aeb2a8da6 on Jan 14, 2017
- attilaaf referenced this in commit 72cf5fe89b on Jan 13, 2020
- cryptapus referenced this in commit 9c191e33ab on May 3, 2021
- DrahtBot locked this on Sep 8, 2021
