Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Restore ability to display addresses in GUI #5861
Conversation
|
NACK. See #4580 for rationale on removing this feature. Apart from you, I've heard no one complain about this. |
|
#4580 does not make sense. It states that "addresses are always displayed", but they aren't... right now there is no way to get them displayed. |
|
ACK |
|
@luke-jr On recent master, I see addresses in the transaction list. Have you tried a fresh wallet.dat? |
|
@dgenr8 No, I've read the code, and it does not show addresses in normal circumstances (ie, labels set). |
|
@dgenr8 |
laanwj
added
the
GUI
label
Mar 9, 2015
|
So from a UI perspective why would you want to see addresses in this list? Do they convey any meaning to you? It's like having a 'SHA256 hash' column in your mail client. |
|
@laanwj It occurs to me I have no good use case for it (I was trying to get a list of used addresses matching a given label term, which is something better done via RPC anyway and has no GUI value except when addresses have been reused). Leaving this open for now in case @fsb4000 has some better reason for it. |
|
Of course addresses convey meaning. They are the actual ID that is exchanged OOB between parties. I'm not going to read my private label to somebody when he claims he didn't receive payment. |
|
Another reason: If you have multiple addresses under one label. For example: donations. Different addresses for different projects, but one label. Of course, you can make a longer labels include a fuller description, but I do not really like long labels... |
|
A while ago there was extensive discussion on the mailing list, that it was bad idea to expose addresses to the end user. This is in line with increasing usage of payment requests, and other innovation. Of course there are some edge cases where you do want the address, but in that case you can click on the transaction to get full information (or even hover?). It seems pointless to show the address for every single transaction. So I'm closing this. |
laanwj
closed this
Mar 10, 2015
|
utACK |

luke-jr commentedMar 6, 2015
This reverts commit bdba2dd (PR #4610). I don't understand why it was removed in the first place, and didn't get an answer on IRC when I inquired a week ago. But since the commit message states "no-one cares about" the option, it seems reasonable to restore it so long as it is cared about.
Note: This needs adapting if #5833 gets merged first. git will NOT detect the conflict.