-
Notifications
You must be signed in to change notification settings - Fork 35.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GUI unnecessarly encourages address reuse #2429
Comments
If the workflow for receiving coins is "1) create a new receiving address..." then maybe the message could be improved as well, it's currently: "These are your Bitcoin addresses for receiving payments. You may want to give a different one to each sender so you can keep track of who is paying you." When we're in this discussion anyway: the send UI also encourages address reuse, by offering an "address book" of past sending addresses. But TBH I don't think much can be done here until there is a standardized payment protocol of some kind. |
No, the "default address" will not be back. It encourages unlabeled addresses, it causes automatic empty labels to be created, and confuses users because there is a "changing address". No way we're going back there. I'd propose changing the "Receive" tab so that the primary function is not a list, but a form in which a payment request can be created. Similar to what is now the QR code dialog. A workflow of
It is then made clear to the user that he should give this address to the person that wants to send him coins. Listing the current receiving addresses is secondary; it could remain at the bottom of the tab, or behind a special menu item. |
How about showing "your last used" bitcoins address, and "your new bitcoin address" for one which has not been used? I've already encountered problems with "new address" giving me an address that's already been used for change. I think "new address" should only ever give unused addresses. |
Adding to this, apparently the address use triggers some OCD in some users and they really want to "delete" addresses which are "cluttering" the list. Any revisions here should be mindful of that and help those people out without creating a coinloss risk. |
@rebroad: dealing out change addresses as "new" sounds like something that warrants a seperate issue |
Ugh. More indications that low-level abstractions such as addresses and individual keypairs are dangerous to users. They should just regard a wallet as a wallet. https://bitcointalk.org/index.php?topic=185185.msg1927752#msg1927752 |
Providing a stack list of past receive addresses as a top level GUI element encourages reuse, it makes addresses seem like something scarce which should be conserved. It also can result in people accidentally sending coins to addresses created prior to wallet encryption.
The interface should probably be adjusted to make it clear that used addresses are used and shouldn't be reused, e.g. by only displaying the initial digits of all but the most recent address and requiring context click to get details.
The text was updated successfully, but these errors were encountered: