Show originating address in transaction details #3142

issue kroese opened this issue on October 24, 2013
  1. kroese commented at 9:02 AM on October 24, 2013: none

    I imported a large number of private keys, and incoming transactions have the correct label, but all previous outgoing transactions are 'blind'. There is no way to see from which label/address they were originally send. Is there some technical reason for this, or can this feature be added?

  2. laanwj commented at 9:55 AM on October 24, 2013: member

    Any label data is stored in the wallet (as extra data), and thus lost when you import bare keys.

    Edit: I suppose you mean "recipient address" and "sent to" for outgoing transactions, otherwise your message makes little sense, there is no originating address.

  3. kroese commented at 10:09 AM on October 24, 2013: none

    @laanwj With 'originating address' I ment the address(es) used as input. I can see that I send 500 BTC. I can also see the address it went to. But I cannot see the address it was taken from. I understand why this is (because the idea behind the wallet is that you have a single balance), but it makes the history-tab almost useless for me now. I merged many wallets into a single big one, giving every address a label based on the wallet-name it originally belonged to. I can track the history of incoming transactions just fine that way, and showing the inputs in the details dialogue would make that possible for the outgoing ones too.

  4. laanwj commented at 10:32 AM on October 24, 2013: member

    If you run the client in -debug mode, you can see all the inputs for transactions in the "transaction details" window. This is not normally shown because it is only confusing and indeed breaks the wallet abstraction that we use in bitcoin-qt.

  5. sipa commented at 2:28 PM on October 27, 2013: member

    You shouldn't rely on the "input addresses" for anything - they are not a reliable way of finding out who sent something, or where to send something back to. The only thing it is useful for, is debugging (what -debug is for) or micromanagement. Regarding the latter, I think txout-level details about transactions could be made available when coin control is merged, as that is explicitly about breaking the wallet abstraction.

  6. laanwj commented at 2:46 PM on October 27, 2013: member

    @Poes it tries to show label information for the "input addresses" (see https://github.com/bitcoin/bitcoin/blob/master/src/qt/transactiondesc.cpp#L277). Are you sure these are not change addresses ?

  7. laanwj commented at 2:09 PM on November 4, 2013: member

    Closing this as (AFAIK) it works as intended

  8. laanwj closed this on Nov 4, 2013

  9. MarcoFalke locked this on Sep 8, 2021
Contributors

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-15 18:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me